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] DomU network dies

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] DomU network dies
From: Olav Lavell <olav@xxxxxxxxx>
Date: Wed, 01 Sep 2010 22:52:52 +0200
Delivery-date: Wed, 01 Sep 2010 13:54:12 -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
User-agent: RoundCube Webmail/0.4-beta
Hello, I would like to ask for some help with troubleshooting,

A few days ago I installed Debian Squeeze (amd64) with the Xen kernel and
Xen 4 (from the Debian repos) on a small computer. I used Xen-tools to
create a DomU (also Squeeze/amd64) which is now my e-mail and web server.
This is all purely for hobbyist/educational use.

Now the problem is that my DomU will occasionally lose all network
connectivity. If that happens, it can't be pinged or anything (no route to
host). Also, it leaves no trace as far as I can tell in any of the log
files. The network just seems to go out silently. The Dom0 does not seem to
be affected. I can SSH into the Dom0 and from there, "xm console myserver"
into the DomU. This works well except that there is no network, not even
after "/etc/init.d/networking restart". Only after I reboot the DomU,
everything seems to be in order again. It may then run for 18 hours without
a problem, or fail again within a much shorter time. This seems to be
completely random, ie. it doesn't look like it is related to any heavy
network traffic or even CPU load.

I tried to use "post-up ethtool -K eth0 tx off" in the
/etc/network/interfaces file of the DomU, because the comment says it
"might resolve problems for some users." It doesn't in my case.

Because I am quite new to Xen I have no clue about how to troubleshoot
this situation. My attempts at googling probably were a little uneducated
as well. Any hints would be appreciated. If I need to post log files,
configuration files or any command output I will gladly do so as well.

I have thought of "downgrading" to Debian Lenny (after all, Squeeze is
still the "testing" distro) and Xen 3.2 (I prefer to use whatever version
of Xen that Debian offers as packages). But will I be able to just copy my
DomU files (images and configuration) over to the "older" version and still
use them?

Regards,
Olav

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

<Prev in Thread] Current Thread [Next in Thread>