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

[Xen-devel] SHUTDOWN_crash and vcpu deferrals

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] SHUTDOWN_crash and vcpu deferrals
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Fri, 20 Feb 2009 16:01:55 -0500
Delivery-date: Fri, 20 Feb 2009 13:02:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
If an HVM guest is waiting for an ioemu assist, when qemu isn't running, and
domain_shutdown(SHUTDOWN_crash) is called, then the domain isn't crashed
properly:

446 void domain_shutdown(struct domain *d, u8 reason)
447 { 
...
466  for_each_vcpu ( d, v )
467  {
468   if ( v->defer_shutdown )
469    continue; 

Nothing will ever end the deferral. I added code to bust through the
deferral if SHUTDOWN_crash was the reason, and it seemed to help, but
I'm not sure it's the right fix.

regards
john

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