Re: [Xen-users] bridge name not passed to network backend

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Sat, 2015-03-14 at 21:15 +0100, Henrik Riomar wrote:
> Hi,
> 
> I have a problem getting backend driver domains to work with xl and
> with multiple bridges
> in the driver domain. (e.g. in a one brigde per domU setup).
> 
> example guest config:
> 
> vif         = [
> 'ip=192.168.1.31,mac=00:16:3E:ab:cd:ef,bridge=br_b,backend=net-back' ]
> 
> If the dom0 and the driver domain is running xm/xend with xen-4.1
> (under Debian wheezy) it works fine,
> 
> From the syslog in the driver domain:
> 
> Mar 14 20:59:52 net-back logger: /etc/xen/scripts/vif-bridge: online
> type_if=vif XENBUS_PATH=backend/vif/8/0
> Mar 14 20:59:52 net-back kernel: [ 1252.739351] device vif8.0 entered
> promiscuous mode
> Mar 14 20:59:52 net-back kernel: [ 1252.744057] ADDRCONF(NETDEV_UP):
> vif8.0: link is not ready
> Mar 14 20:59:52 net-back kernel: [ 1252.873690] ip_tables: (C)
> 2000-2006 Netfilter Core Team
> Mar 14 20:59:53 net-back logger: /etc/xen/scripts/vif-bridge:
> Successful vif-bridge online for vif8.0, bridge br_b.
> Mar 14 20:59:53 net-back logger: /etc/xen/scripts/vif-bridge: Writing
> backend/vif/8/0/hotplug-status connected to xenstore.
> Mar 14 20:59:55 net-back kernel: [ 1255.138904]
> ADDRCONF(NETDEV_CHANGE): vif8.0:link becomes ready
> Mar 14 21:00:05 net-back kernel: [ 1265.504218] vif8.0: no IPv6 routers 
> present
> 
> root@net-back:~# brctl show
> bridge name     bridge id               STP enabled     interfaces
> br_a            8000.000000000000       no
> br_b            8000.feffffffffff       no              vif8.0
> br_c            8000.000000000000       no
> 
> But the same thing with xl under Debian Jessie and the bridge is not
> passed at all to the backend, making it fallback to the first bridge.
> 
> Is this a known limitation with xl?

I'm pretty certain that people have run network driver domains with xl
in the not too distant past.

[...]
> Environment passed to /etc/xen/scripts/vif-bridge:

AFAIK the bridge should be passed via xenstore not the environment, see
the top of vif-bridge which has:

bridge=${bridge:-}
bridge=$(xenstore_read_default "$XENBUS_PATH/bridge" "$bridge")

I can see the code which writes that in libxl__device_nic_add.

"xenstore-ls -fp" might give a clue as to what is going on.

Ian.


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