All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Kreutzberg <ulf.kreutzberg@hosteurope.de>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 2/4] xl: allow specifying a default gatewaydev in xl.conf
Date: Tue, 19 Feb 2013 17:04:38 +0100	[thread overview]
Message-ID: <5123A296.2040607@hosteurope.de> (raw)
In-Reply-To: <5121DA78.2000708@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1244 bytes --]

Hello Roger,
hi all,

On 18.02.2013 08:38, Roger Pau Monné wrote:
>> The mac address still is not parsed if digits are not padded with
>> leading zero, like "mac=de:ad:a:1e:42:3" - the rest of the line is
>> ignored without any error.
>>
>> However, I was not able to apply patches V2 after that, they do not seem
>> to work together with the first patch series.
> 
> Hello Ulf,
> 
> Version v2 should be applied without v1, they are not additional
> patches, it's a revision of the same patches (trying to apply both will
> lead to errors). To simplify it I've pushed the patches to my git repo,
> so you can fetch them easily:
> 
> $ git clone -b vif_route_v2 git://xenbits.xen.org/people/royger/xen.git
> 

Many thanks, building that tree definitely works. (Still could not get
xen 4.3 running, but that is not the issue here). I have tested the
utils with Xen 4.2.1 and parsing of domu configs with netdev= and
gatewaydev= parameter works perfectly. Domu does start up and is reacheable.
I wonder if you could backport these changes to 4.2?

One caveat: the mac address and therfore the rest of the domu config
still is not parsed if not padded with leading zeros, as mentioned before.

Best regards,
Ulf


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-02-19 16:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 18:04 [PATCH v2 0/4] add vif-route support to libxl/xl Roger Pau Monne
2013-02-06 18:04 ` [PATCH v2 1/4] xl/libxl: add gatewaydev/netdev to vif specification Roger Pau Monne
2013-03-12 16:20   ` Ian Campbell
2013-02-06 18:04 ` [PATCH v2 2/4] xl: allow specifying a default gatewaydev in xl.conf Roger Pau Monne
2013-02-14 15:09   ` Ulf Kreutzberg
2013-02-14 15:17     ` Roger Pau Monné
2013-02-15 14:06       ` Ulf Kreutzberg
2013-02-18  7:38         ` Roger Pau Monné
2013-02-19 16:04           ` Ulf Kreutzberg [this message]
2013-03-04 11:02             ` Roger Pau Monné
2013-03-12 16:39               ` Ulf Kreutzberg
2013-03-12 16:22   ` Ian Campbell
2013-03-12 16:27     ` Ian Campbell
2013-03-13 16:29       ` Roger Pau Monné
2013-02-06 18:04 ` [PATCH v2 3/4] xl: add vif.default.bridge Roger Pau Monne
2013-03-12 16:25   ` Ian Campbell
2013-03-13 16:40     ` Roger Pau Monné
2013-02-06 18:04 ` [PATCH v2 4/4] xl: add vif.default.script Roger Pau Monne
2013-02-07 11:31   ` George Dunlap
2013-03-12 16:25   ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5123A296.2040607@hosteurope.de \
    --to=ulf.kreutzberg@hosteurope.de \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.