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] when dom0 loadavg above 1, domUs not available

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] when dom0 loadavg above 1, domUs not available
From: Tomasz Chmielewski <mangoo@xxxxxxxx>
Date: Mon, 03 Jul 2006 12:45:15 +0200
Delivery-date: Mon, 03 Jul 2006 03:46:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
User-agent: Thunderbird 1.5.0.4 (X11/20060613)
I have a xen 3.0.2 running on a 733 MHz server, 1 GB RAM.
It has two domU domains.
dom0 has 512 MB, domUs have 256 MB each.

Whenever load average on dom0 is above 1-2 (for example, compressing 200 MB file), I can't reach any domU domain.

Ping replies to domUs take very long time (it's on LAN), and there are packet losses:

64 bytes from 192.168.11.61: icmp_seq=7 ttl=64 time=4140 ms
64 bytes from 192.168.11.61: icmp_seq=8 ttl=64 time=39548 ms


When I ping dom0, it replies immediately, there are no packet losses:

64 bytes from 192.168.111.173: icmp_seq=1 ttl=64 time=4.07 ms
64 bytes from 192.168.111.173: icmp_seq=2 ttl=64 time=0.406 ms


It's problematic to get to the domU with "xm console domain": it takes really long to get the login prompt, and even if I get it, it times out when waiting for the password.

There are no problems logging to dom0.


I found a similar problem here, but it didn't have any conclusions:

http://lists.xensource.com/archives/html/xen-users/2005-12/msg00728.html


Is it a known problem, and if so, is there a remedy for this?

It makes things a bit unreliable when one system makes some job, and other can't be accessed because of it.


--
Tomasz Chmielewski
http://syneticon.net

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

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