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-devel

Re: [Xen-devel] xm pause causing lockup

To: Kip Macy <kip.macy@xxxxxxxxx>
Subject: Re: [Xen-devel] xm pause causing lockup
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 14 Apr 2005 04:03:59 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 14 Apr 2005 03:00:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <b1fa291705041319464ffdb42a@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <b1fa291705041319464ffdb42a@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 14 Apr 2005, at 03:46, Kip Macy wrote:

Is there some critical section where "xm pause" might cause a lockup?
When I run FreeBSD to some point (I don't know where - the console
isn't giving output) - and then pause it, the machine locks up. I
can't even get info from xen apart from switching the switching the
serial input.

Does dom0 wedge completely (e.g., unpingable) or might it just be xend that goes awol? The pause code isn't that complicated, and most of it is used in various not uncommon situations, so I'll be surprised if this is the hypervisor's fault.

 -- Keir


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