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] Mysterious Server Lockups

To: James Pifer <jep@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Mysterious Server Lockups
From: Nick Anderson <nick@xxxxxxxxxxxx>
Date: Fri, 13 Feb 2009 09:08:31 -0600
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 Feb 2009 07:09:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1234536603.1854.45.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <20090213144204.GA10025@tp> <1234536603.1854.45.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Feb 13, 2009 at 09:50:03AM -0500, James Pifer wrote:
> outages. Not sure I can even call it a lockup, because I could still
> ping dom0, but it's screen was blank, and the domU's were hosed. 
Yesterdays "lockup" was slightly different in that I was already
shelled into dom0 when the lockup started. I was out smoking and got
notified. I ran in and for about 10 seconds I was able to do things in
dom0. I made the mistake of trying to correct the problem before
assessing the situation so I didn't get any information :(. I tried
doing and xm shutdown on the vm that was unresponsive at the time. It
wasn't long from there that dom0 was locked and I couldn't even get any
information without rebooting and trying to do post-mortem.

Thanks for sharing, with the steal going up it makes me hope that
upgrading to xen 3.2 will help.

Show the percentage of time spent in involuntary
wait by the virtual CPU or CPUs while the hypervisor was servicing
another virtual processor.

Anyone else have any thoughts or input?
Nick Anderson <nick@xxxxxxxxxxxx>

Attachment: signature.asc
Description: Digital signature

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>