[Bug 341846] [NEW] No network connectivity for new domU's (vif vif-247-0: 28 mapping shared-frames)

[Wido den Hollander]

Public bug reported:

I have a Ubuntu 8.04 server running with Xen 3.2

Linux vps-pool-01.xen.pcextreme.nl 2.6.24-22-xen #1 SMP Mon Nov 24
21:35:54 UTC 2008 x86_64 GNU/Linux

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu 8.04.2"

The machine is pretty powerfull:
* Dual CPU Quad Core Xeon
* 64GB FB-Dimm DDR2
* Dual Intel Corporation 80003ES2LAN Gbit Ethernet

On the machine are 78 domU's running and they run fine, but when
starting domU number 79 it boots fine, but the network does not come up.

The network looks like:
* eth0: untagged VLAN connected to private LAN
* eth0.711: tagged VLAN for management
* eth0.710 <> vlanbr710, connectivity for domU's

A snippet of "brctl show"

bridge name     bridge id               STP enabled     interfaces
vlanbr710               8000.feffffffffff       no              eth0.710
                                                        vps01
                                                        vps02
                                                        vps33
                                                        vps04
                                                        vps05

What caught my attention is that the bridge of the newest domU drops all
the traffic:

vps78     Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff  
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:31755 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

When i do a tcpdump in the domU i see no traffic coming into the domU
and as you can see, the RX/TX bytes stays at 0.0B

All the new domU's i create don't have network access, but the running
domU's are working fine.

I found a post on the Xen mailinglist: http://www.nabble.com/XEN-3.1
:-critical-bug:-vif-init-failure-after-creating-15-17-VMs-(XENBUS
:-Timeout-connecting-to-device:-device-vif)-td11571794.html

On that post the bug seemed fixed in the upstream code.

Since this machine is in production at the moment i can't reboot it or
build some new kernels.

Does anyone know how to fix this?

** Affects: xen-meta (Ubuntu)
     Importance: Undecided
         Status: New

-- 
No network connectivity for new domU's (vif vif-247-0: 28 mapping shared-frames)
https://bugs.launchpad.net/bugs/341846
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs