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] Heavy Dom0 traffic stops network

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Heavy Dom0 traffic stops network
From: Simon Hobson <linux@xxxxxxxxxxxxxxxx>
Date: Sun, 11 Oct 2009 16:12:29 +0100
Delivery-date: Sun, 11 Oct 2009 08:13:19 -0700
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I've just experienced a rather strange one ...

I was trying to create a new DomU using debootstrap as I've done before - and everything stopped, quickly followed by a voice from downstairs asking why the internet had stopped ! This first happened yesterday, and assuming I'd perhaps managed some form of resource exhaustion I rebooted the system.

Today I tried again (but without the "when will it be working ?" from downstairs) and found this.

If I do a ping from my laptop to a DomU, then the responses just stop a short while after I hit the network from Dom0 (it only takes a few MB). If I stop the traffic and wait, then it all comes back again after about 5 minutes :

64 bytes from 192.168.0.34: icmp_seq=465 ttl=64 time=0.290 ms
64 bytes from 192.168.0.34: icmp_seq=466 ttl=64 time=0.292 ms
64 bytes from 192.168.0.34: icmp_seq=467 ttl=64 time=0.338 ms
64 bytes from 192.168.0.34: icmp_seq=468 ttl=64 time=297024.510 ms
64 bytes from 192.168.0.34: icmp_seq=469 ttl=64 time=296024.293 ms
64 bytes from 192.168.0.34: icmp_seq=470 ttl=64 time=295024.138 ms
Note that packets don't seem to have been lost, just queued up.

"brctl showmacs eth0" shows MAC addresses aging in the bridge.

Dom0 has one bridge on the inside network, internet access is via a router running in a DomU with external ethernet interface made available to it via pciback.

Dom0 is Debian Etch, linux-image-2.6.18-6-xen-amd64  2.6.18.dfsg.1-23etch1
running on xen-hypervisor-3.2-1-amd64  3.2.1-2~bpo4+1

The guests are running Lenny.

Nothing appears to be logged when the problem happens. Any ideas ?

--
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Heavy Dom0 traffic stops network, Simon Hobson <=