[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] domU with two eth but only one is active

  • To: xen-users@xxxxxxxxxxxxx
  • From: SZABO Zsolt <szazs@xxxxxxxxx>
  • Date: Sat, 18 Jul 2015 00:56:37 +0200 (CEST)
  • Delivery-date: Fri, 17 Jul 2015 22:57:53 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

I have recently upgraded the xen system with the debian distro on
my xen machine.

So, in wheezy it has xen-4.1, and xm, and linux-3.2,
now the versions are xen-4.4 with xl toolstack, and the linux kernel is 3.16.

On wheezy I used a modified version of the network-bridge script, but after the upgrade I omit this procedure and modified

auto xenbr0
iface xenbr0 inet static
    bridge_ports eth0

auto xenbr1
iface xenbr1 inet static
    bridge_ports eth1

Thus, when I boot the xen machine, everything seems fine:

# brctl show
xenbr0          8000.0025908190d8       no              eth0
xenbr1          8000.0025908190d9       no              eth1

I can ping other hosts on both interfaces (bridges).

however, when I create (start) the new domU with lines in xl_domU.cfg
vif  = [ 'mac=00:40:f6:54:79:0f, bridge=xenbr0',
         'mac=00:16:3e:00:02:01, bridge=xenbr1' ]

and "brctl show"s
xenbr0          8000.0025908190d8       no              eth0
xenbr1          8000.0025908190d9       no              eth1

then eth0 @domU (aka vif5.0 @dom0) works
but  eth1 @domU (aka vif5.1 @dom0) does not... :-(

I have also noticed in kern.log some lines like

vif vif-5-0 vif5.0: Guest Rx ready
IPv6: ADDRCONF(NETDEV_CHANGE): vif5.0: link becomes ready
xenbr0: port 2(vif5.0) entered forwarding state

but any similar for vif-5-1 ...

What can be the problem?

PS: maybe I will try the old method with network-bridge script..

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.