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] dom0 hangs when doing heavy I/O on domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] dom0 hangs when doing heavy I/O on domU
From: Joost Roeleveld <joost@xxxxxxxxxxxx>
Date: Thu, 21 Apr 2011 15:39:58 +0200
Delivery-date: Thu, 21 Apr 2011 06:41:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTinrKXZFHtGi2uEgY0bD1JRyRxNPnQ@xxxxxxxxxxxxxx>
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: <BANLkTin3aOg2CYcvDgtwwHdrhwExr80zaw@xxxxxxxxxxxxxx> <BANLkTinrKXZFHtGi2uEgY0bD1JRyRxNPnQ@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/4.6 beta4 (Linux/2.6.36-gentoo-r5; KDE/4.6.2; x86_64; ; )
On Thursday 21 April 2011 12:59:17 Florian Heigl wrote:
> Hi Chang,
> 2011/4/20 Kiefer Chang <zapchang@xxxxxxxxx>:
> > Hi all,
> > We are using XEN as hypervisor to setup our private cloud.
> > The framework is Eucalyptus and using CentOS 5.4 as dom0 OS.
> > Sometimes we find some machines' dom0 become unresponsive, the symptoms
> > are: (1) We can't log into dom0 via ssh. After typing password, it just
> > stops there.
> > (2) We can ping dom0 successfully.
> > (3) We can log into domU without problem.
> > The unresponsive dom0 eventually "alive" after a period of time. Maybe
> > half hour or even several hours.
> So one of your domUs is trashing the disks and dom0 can't get enough
> performance, right?
> - are they sharing a disk?
> - can you check what I/O scheduler you are using?
>   (with cfq you can then use ionice to lower prio on all blkback
> threads a little. that way dom0 will "win the race")
> In general, your dom0 is privileged in terms of IO access rights, but
> not in IO peformance. So if one domU goes crazy, it will affect
> anything.
> ... until you take measures :)
> I'd suggest you switch to deadline scheduler and re-test.
> dom0 on a different disk media is also very advisable imho.

Another possible cause for this is if dom0 is not pinned to a "private" cpu-
I noticed similar issues before I pinned dom0 to cpu0 and configured all the 
other domUs to use the other 3 cores.


Xen-users mailing list