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] Strange dom0 networking error with Debian "Etch" amd64

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Strange dom0 networking error with Debian "Etch" amd64
From: Mark <m_c_001@xxxxxxxxxxx>
Date: Wed, 28 May 2008 17:01:18 +0100
Delivery-date: Wed, 28 May 2008 09:02:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: Normal
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
Hi,

We're trying to run Xen on a Debian "Etch" base system (kernel 2.6.18-6-xen-amd64), but have come across a strange networking error whenever bridging (vif-bridge/network-bridge) is in operation. The
symptom is that the dom0 base system loses all network connectivity to the outside world while the two guest instances function perfectly well. As far as we can tell, we haven't done anything which isn't entirely standard.

Rebooting the base system and preventing xend from setting up the bridged environment (by uninstalling 'bridge-utils') fixes the problem, but means that the domUs obviously fail to start. So it looks like this is something to do with the way the networking is set up.

A further symptom is that "arping" from another machine gets a reply, with the correct MAC address, from the broadcast ping but not the unicast one, like this:

$ sudo arping 172.24.189.23
ARPING 172.24.189.23 from 172.24.189.20 eth0
Unicast reply from 172.24.189.23 [00:18:8B:46:4A:CD] 0.688ms
Sent 3 probes (1 broadcast(s))
Received 1 response(s)

$ sudo arping -b 172.24.189.23
ARPING 172.24.189.23 from 172.24.189.20 eth0
Unicast reply from 172.24.189.23 [00:18:8B:46:4A:CD] 0.688ms
Unicast reply from 172.24.189.23 [00:18:8B:46:4A:CD] 0.678ms
Unicast reply from 172.24.189.23 [00:18:8B:46:4A:CD] 0.682ms
Sent 3 probes (3 broadcast(s))
Received 3 response(s)

In /etc/xen/xend-config.sxp we're using the following options:

(vif-script vif-bridge)
(network-script network-bridge)

The output of ifconfig when bridging's in operation is below. From all our research so far, this looks correct to us.

Has anyone experienced a similar problem? Can anyone suggest a possible solution, or maybe something specific we can check for to help fix the issue?

Cheers,
Mark

eth0 Link encap:Ethernet HWaddr 00:18:8B:46:4A:CD
inet addr:172.24.189.23 Bcast:172.24.189.63
Mask:255.255.255.192 inet6 addr: fe80::218:8bff:fe46:4acd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:998452 errors:0 dropped:0 overruns:0 frame:0
TX packets:572 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:85531264 (81.5 MiB) TX bytes:25459 (24.8 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:174 errors:0 dropped:0 overruns:0 frame:0
TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18657 (18.2 KiB) TX bytes:18657 (18.2 KiB)

peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1501876 errors:0 dropped:0 overruns:0 frame:0
TX packets:431312 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:312379199 (297.9 MiB) TX bytes:146152245 (139.3 MiB)
Interrupt:16 Memory:f8000000-f8011100

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:572 errors:0 dropped:0 overruns:0 frame:0
TX packets:998452 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:25459 (24.8 KiB) TX bytes:85531264 (81.5 MiB)

vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:72721 errors:0 dropped:0 overruns:0 frame:0
TX packets:1092862 errors:0 dropped:170 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18409842 (17.5 MiB) TX bytes:207173494 (197.5 MiB)

vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:318959 errors:0 dropped:0 overruns:0 frame:0
TX packets:1306207 errors:0 dropped:413 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:117331450 (111.8 MiB) TX bytes:175019480 (166.9 MiB)

xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:995548 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:71388816 (68.0 MiB) TX bytes:0 (0.0 b)


Messenger's gone Mobile! Get it now!
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Strange dom0 networking error with Debian "Etch" amd64, Mark <=