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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm pause causing lockup
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Wed, 13 Apr 2005 20:03:48 -0700
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 14 Apr 2005 03:04:33 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WJgoxCu4sLJGm76PFsmveo71PE+F/7kTGkbOGj6Xe8qOdm9lVzizZoGD6MBViDolJno6Apu71hynLdtquoGgEI7nShd1REDyyIoThC98Bf4K7eVB/rstIo86VBzScBbZ7IQxW/HYyaHmB4lZHPpfPxa9+wO1xpqbLM7gbnDdIEE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4afce18847157fad34cd38e14fb83c2c@xxxxxxxxxxxx>
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> <4afce18847157fad34cd38e14fb83c2c@xxxxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Dom0 is unpingable, all network connections timeout.
               
                             -Kip 


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

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