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: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Xen-users] Problemi using vif-route script
Date: Mon, 28 Jan 2013 14:45:10 +0100	[thread overview]
Message-ID: <510680E6.6050406@hosteurope.de> (raw)
In-Reply-To: <51028DDE.9070907@citrix.com>


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

Roger -

>>> 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)
>

I think I could track down the issue:
The mac address is not parsed correctly if not padded with leading zeros
(and no error reported, though):
Using the example above which worked perfectly with the old xm,
xl create -n test.domU
====
...shortened output...
"nics": [
            {
                ...
                "mac": "de:ad:0a:0e:02:00",
                "ip": null,
                "bridge": null,
                "ifname": null,
                ...
            },
            {
                ...
                "mac": "ba:cc:7f:00:00:0b",
                "ip": null,
                "bridge": null,
                "ifname": null,
                ...
            }
        ]
=====
If I use padded bytes,
vif = [ 'mac=de:ad:0a:1e:42:03, ip=10.3.2.3',
        'mac=ba:cc:7f:00:04:01,bridge=backupbr0,script=vif-bridge']
it creates correctly
=====
"nics": [
            {
                ...
                "mac": "de:ad:0a:1e:42:03",
                "ip": "10.3.2.3",
                "bridge": null,
                "ifname": null,
                ...
            },
            {
                ...
                "mac": "ba:cc:7f:00:04:01",
                "ip": null,
                "bridge": "backupbr0",
                "ifname": null,
                ...
            }
        ]
=====
which is totally ok for me. Routes are set and the IP of the routed vif
shows up in xenstore.

Many thanks and 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

  parent reply	other threads:[~2013-01-28 13:45 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é
2013-01-25 14:04                 ` Ulf Kreutzberg
2013-01-25 14:15                   ` Ian Campbell
2013-01-28 13:45                 ` Ulf Kreutzberg [this message]
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=510680E6.6050406@hosteurope.de \
    --to=ulf.kreutzberg@hosteurope.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=roger.pau@citrix.com \
    --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 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.