WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Bridging failing (timing out)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Bridging failing (timing out)
From: Kris Buytaert <mlkb@xxxxxxxxx>
Date: Thu, 20 Oct 2005 11:50:52 +0200
Delivery-date: Thu, 20 Oct 2005 09:47:52 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Folks,


We have a machine which is running Xen 2.0.7  with a 2.4.30 kernel.
(tested on different hardware)

The machine is connected to 2 separate networks on eth0 and eth1.
A virtual machine is running on this Xen box and we bridge eth0 and eth1 to the
virtual machine's eth0 and eth1.
After pulling out the eth1 cable on the physical machine and waiting for a
random timeout we loose ip connection to the virtual machines.

When connecting to the consoles we also see no interrupts being generated on
outgoing/incoming pings.

Upon plugging the cable back in traffic continues.

I assume that this is somehow related to some bridging code.

We use a separate A/B network for High Availability, when network A fails
traffic should continue over network B.  With this issue however , when network
B fails traffic on network A is also interrupted.


eth0      Link encap:Ethernet  HWaddr 00:0B:DB:90:C5:17
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:84194660 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30267426 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:380422169 (362.7 Mb)  TX bytes:3663013401 (3493.3 Mb)
          Base address:0xdce0 Memory:feb60000-feb80000

eth1      Link encap:Ethernet  HWaddr 00:0B:DB:90:C5:18
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:56154900 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2110365 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2117107178 (2019.0 Mb)  TX bytes:346518807 (330.4 Mb)
          Base address:0xdcc0 Memory:feb20000-feb40000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:9969848 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9969848 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:926726936 (883.7 Mb)  TX bytes:926726936 (883.7 Mb)

lo:1      Link encap:Local Loopback
          inet addr:172.17.0.102  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

lo:2      Link encap:Local Loopback
          inet addr:172.17.0.166  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14471578 errors:0 dropped:0 overruns:0 frame:0
          TX packets:69134919 errors:0 dropped:6702 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1998090252 (1905.5 Mb)  TX bytes:2608370312 (2487.5 Mb)

vif1.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1526585 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56408674 errors:0 dropped:2393 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:287873207 (274.5 Mb)  TX bytes:1919976931 (1831.0 Mb)

xen-br0   Link encap:Ethernet  HWaddr 00:0B:DB:90:C5:17
          inet addr:172.16.32.9  Bcast:172.16.255.255  Mask:255.255.248.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:73558990 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16044506 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1950570231 (1860.2 Mb)  TX bytes:1556556940 (1484.4 Mb)

xen-br1   Link encap:Ethernet  HWaddr 00:0B:DB:90:C5:18
          inet addr:172.16.40.9  Bcast:172.16.255.255  Mask:255.255.248.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:56517883 errors:0 dropped:0 overruns:0 frame:0
          TX packets:583787 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:632977188 (603.6 Mb)  TX bytes:50075742 (47.7 Mb)


bridge name     bridge id               STP enabled     interfaces
xen-br1         8000.000bdb90c518       no              eth1
                                                        vif1.1
xen-br0         8000.000bdb90c517       no              eth0
                                                        vif1.0



I would be happy to help out debugging this problem.


-- 
Kris Buytaert <mlkb@xxxxxxxxx>

PS. Also filed as Bug 344 


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Bridging failing (timing out), Kris Buytaert <=