[Xen-users] xl and vifname

[mark@xxxxxxxxxxxxxx]

Hello,

While using xen 4.1-testing.hg (r23202) I noticed that the 'vifname'
config value is not handled by xl, but is handled by xm. Is there a
workaround or patch for this? My firewall and scripts depend on static
vifnames.

XM works good - it adds multiple interfaces to multiple bridges and
configures them appropriately. But with xl it differs -- here only tap
devices are added to a bridge instead of the interface pairs. The tap
devices /can/ be added to multiple bridges, so that's a good start.

Example of a use case:
*  dom0 has bridge br0, br1, br2, br3.
*  the (HVM) configuration contains this vif configuration:

vif = [ 'script=vif-bridge, vifname=foo0, mac=00:16:3e:00:00:00, bridge=br0, 
model=e1000, type=ioemu',
        'script=vif-bridge, vifname=foo1, mac=00:16:3e:00:00:01, bridge=br1, 
model=e1000, type=ioemu',
        'script=vif-bridge, vifname=foo2, mac=00:16:3e:00:00:02, bridge=br2, 
model=e1000, type=ioemu',
        'script=vif-bridge, vifname=foo3, mac=00:16:3e:00:00:03, bridge=br3, 
model=e1000, type=ioemu', ]

(^note: in the past vifnames did work when an entry contained something
like 'script=vif-bridge vifname=foo0' i.e. without the comma. But this
works no longer)

* xl start creates these interfaces, ignoring vifname:
* * vif53.0, vif53.1, vif53.2, vif53.3
* * tap53.0, tap53.1, tap53.2, tap53.3

* tap53.0 - tap53.3 are added to br0 - br3 and are upped;
* vif53.0 - vif53.3 are not added to the bridge and are /not/ upped;
* the domU host does show me the correct mac addresses.

A paravirtualised linux domU shows me the same scenario.

And to reiterate: this behaviour /only/ happens when I use xl. With xm
everything works as I want it to.

Excuse me for the above line length of 105 chars, it improved
readability unless mailman or something else rewraps the lines.

Thanks for helping,
- Mark.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users