From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ulf Kreutzberg <ulf.kreutzberg@hosteurope.de>,
xen-devel <xen-devel@lists.xen.org>,
"xen-users@lists.xen.org" <xen-users@lists.xen.org>
Subject: Re: [Xen-users] Problemi using vif-route script
Date: Fri, 25 Jan 2013 14:51:26 +0100 [thread overview]
Message-ID: <51028DDE.9070907@citrix.com> (raw)
In-Reply-To: <1359105618.32057.58.camel@zakaz.uk.xensource.com>
On 25/01/13 10:20, Ian Campbell wrote:
> I'm ccing xen-devel and Roger since he's been looking at the hotplug
> stuff.
Thanks for Ccing me
>
> On Thu, 2013-01-24 at 16:13 +0000, Ulf Kreutzberg wrote:
>> It seems that
>> 1) in xl.conf you cannot pass a parameter to vif-route like
>> vifscript="vif-route netdev=bond0" any more,
>> as /etc/xen/scripts/vif-route netdev=bond0 cannot be executed (error in
>> xl log). I could workaround that...
>
> I didn't realise this was a feature of the old stuff, but yes I can now
> see that tools/hotplug/Linux/vif-common.sh:dom0_ip() expects
> netdev=<foo> to have been passed as a parameter to the script.
>
> This something we should fix in the libxl layer I think. In the meantime
> the obvious workaround would be to create vif-route-bond0 as a simple
> wrapper around vif-route.
I will look at adding an option to specify a default netdev in the
global xl config file and to allow passing a "netdev" option in the vif
specification.
Also, the vif-route script is not working with HVM domains, it is
lacking the "add" and "remove" actions used by HVM interfaces, it only
supports "online" and "offline".
>
>> 2) from domU config:
>> vif = [ 'mac=de:ad:a:1e:42:3,ip=10.3.2.3',
>> 'mac=ba:cc:7f:0:4:1,bridge=backupbr0,script=vif-bridge']
>>
>> The IP is not parsed so the ${ip} variable in the xen scripts is empty.
>
> ip should be parsed and written to xenstore -- do you see it there (in
> the backend dir)? I can see the code which reads it in the hotplug
> script.
I've tried this config and ip is written to xenstore:
/local/domain/0/backend/vif/6/0/ip = "192.168.1.230" (n0,r6)
>> If this is not a (known) bug or a general issue, I will provide some
>> logs (xen-hotplug.log or verbose vif-route etc).
>
> If the IP address is in xenstore then more verbose vif-route output
> would be useful. I usually do
>
> exec 1>>/tmp/vif-hotplug.log
> exec 2>&1
> set -x
>
> at the top of the script..
>
> Thanks,
> Ian.
>
>> Please let me know if you need more information.
>>
>> Many thanks and best Regards,
>> Ulf
>>
>>
>
>
next prev parent reply other threads:[~2013-01-25 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121026072821.GA9853@intersect>
[not found] ` <1351237241.8558.9.camel@dagon.hellion.org.uk>
[not found] ` <20121026121544.GA14662@intersect>
[not found] ` <1351255054.15162.66.camel@zakaz.uk.xensource.com>
[not found] ` <20121026170920.GA4835@intersect>
[not found] ` <1351276218.11876.0.camel@dagon.hellion.org.uk>
[not found] ` <51015DB8.40107@hosteurope.de>
2013-01-25 9:20 ` [Xen-users] Problemi using vif-route script Ian Campbell
2013-01-25 13:51 ` Roger Pau Monné [this message]
2013-01-25 14:04 ` Ulf Kreutzberg
2013-01-25 14:15 ` Ian Campbell
2013-01-28 13:45 ` Ulf Kreutzberg
2013-01-28 13:59 ` Ian Campbell
2013-02-01 14:46 ` Ulf Kreutzberg
2013-02-02 15:51 ` Roger Pau Monné
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=51028DDE.9070907@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=ulf.kreutzberg@hosteurope.de \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).