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-devel

[Xen-devel] network hang

To: "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] network hang
From: James Harper <JamesH@xxxxxxxxxxxxxxxx>
Date: Thu, 2 Sep 2004 10:55:34 +1000
Delivery-date: Thu, 02 Sep 2004 02:12:24 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcSQh42ZbZ9v6yciSo2rOHEbi0I4OA==
Thread-topic: network hang
I'm playing with nbd+raid1, and am finding that during a resync the network in xenU is dying and simply not sending packets anymore. At first I thought this was a bridging problem, but in xen0 I have removed the vif from the bridge and given it its own ip address, and given the eth interface in xenU a similar ip address, but no traffic is passing anymore.
 
After a while though, it seemed to come good again and I was able to add the interface to the bridge again and it started working.
 
The only strange thing in the kernel logs was this in xenU:
 
eth0: full queue wasn't stopped!
but i'm not sure at what point this was logged though.
 
James