All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ulf Kreutzberg <ulf.kreutzberg@hosteurope.de>
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: Mon, 18 Feb 2013 08:38:32 +0100	[thread overview]
Message-ID: <5121DA78.2000708@citrix.com> (raw)
In-Reply-To: <511E40D8.5070603@hosteurope.de>

On 15/02/13 15:06, Ulf Kreutzberg wrote:
> Hello Roger,
> hello everybody,
> 
> sorry for the late reply.
> 
> On 14.02.2013 16:17, Roger Pau Monné wrote:
>> Could you take a look at tools/libxl/libxl_types.idl?
>>
>> You should have something like the following chunk:
>>
>> libxl_device_nic = Struct("device_nic", [
>>     ("backend_domid", libxl_domid),
>>     ("devid", libxl_devid),
>>     ("mtu", integer),
>>     ("model", string),
>>     ("mac", libxl_mac),
>>     ("ip", string),
>>     ("bridge", string),
>>     ("ifname", string),
>>     ("script", string),
>>     ("nictype", libxl_nic_type),
>>     ("rate_bytes_per_interval", uint64),
>>     ("rate_interval_usecs", uint32),
>>     ("gatewaydev", string),
>>     ])
>>
>> (With only one "gatewaydev").
>>
> That was my copy'n'paste mistake - fixed.
> 
> I could see that after applying patches V1 the parameter "netdev" is
> parsed correctly and the main ip is passed to xen scripts.
> However, I could not get xen 4.3 running so I had to test 4.3 tools on
> 4.2.1 hypervisor, which could not start the domU, but debug output of
> the scripts showed me everything is parsed as expected.
> 
> 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

More information about how to build Xen from source can be found at
http://wiki.xen.org/wiki/Compiling_Xen_From_Source#Building_from_Source.

Hope this helps, Roger.

> Only patching with V2 resulted in missing "netdev" member in
> libxl_device_nic (libxl_types.idl). After editing the file and adding
> the definition, it compiled so far.
> 
> xl with only patches V2 applied does parse neither netdev nor gatewaydev
> as it seems.
> 
> 
> Best regards,
> Ulf
> 
> 


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

  reply	other threads:[~2013-02-18  7:38 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é [this message]
2013-02-19 16:04           ` Ulf Kreutzberg
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=5121DA78.2000708@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=ulf.kreutzberg@hosteurope.de \
    --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.