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/
Home Products Support Community News


Re: [Xen-users] domU loses network after a while

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU loses network after a while
From: Erwan RENIER <erwan.renier@xxxxxxxxxxx>
Date: Thu, 18 Nov 2010 22:35:46 +0100
Delivery-date: Thu, 18 Nov 2010 15:29:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CE5715F.7090005@xxxxxxxxx>
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>
References: <4CE0CC70.8080301@xxxxxxxxx> <4CE5687F.6070007@xxxxxxxxx> <4CE5715F.7090005@xxxxxxxxx>
Reply-to: erwan.renier@xxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv: Gecko/20101027 Thunderbird/3.1.6
Le 18/11/2010 19:33, Stein van Oevelen a écrit :

Nathan Friess wrote:

I have a host running Debian Squeeze with Xen 4.0.1 installed from the Debian repository.  My host is working fine running 10 domUs, except that after some number of days one or more domUs lose their network interface.  In dom0 and domU I'm running kernel 2.6.32-5-xen-amd64 (PV kernel in Debian repo), and interfaces are in a bridged config.

In case anyone runs into something similar, I did figure out how to resolve my issue without having to reboot the domU... which is a slight improvement I suppose.

   xm network-detach domUName 0

Causes eth0 to disappear in the domain, and the following to show up in dmesg:

  net eth0: xennet_release_rx_bufs: fix me for copying receiver.

Then running an xm network-attach will bring eth0 back and everything will be okay.

I also tried rmmoding xen_netfront in domU before I figured out the network-detach, but this doesn't help.  When modprobing again, the domU says "eth0: link is not ready".  This also causes any subsequent attempt to network-detach in dom0 to get stuck and eventually timeout with "Device 0 (vif) could not be disconnected."

Also, when the vif is stuck, the TX dropped packets shown in dom0 is steadily increasing.  It seems that dom0 is having trouble sending packets to domU because one of the two gets stuck in an unexpected state.  At least doing a network-detach will reset the state and allow things to run properly again.


Xen-users mailing list

I have a similar issue, however my DomU's seem to get their connection back after a while automatically, most of the time it happens when I physically login to the Dom0 :/
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
Same for me, anyone knows if a bug report has been filled somewhere for this ?
Xen-users mailing list