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] SHUTDOWN_crash and vcpu deferrals

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] SHUTDOWN_crash and vcpu deferrals
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Fri, 20 Feb 2009 17:03:05 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 20 Feb 2009 14:03:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5C4D294.3310%keir.fraser@xxxxxxxxxxxxx>
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>
References: <20090220210155.GA5872@xxxxxxxxxxxxxxxxx> <C5C4D294.3310%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Feb 20, 2009 at 09:35:16PM +0000, Keir Fraser wrote:

> Hm. If qemu is down you're kind of screwed anyway.

You're totally screwed. But what happens today is this: you get some
weird message about sentinels in xend.log (if you happen to read it),
and a domain state that looks like this:

domu-224                        2  1024     1     ------ 0.0

which is not exactly very useful. But we detect qemu failures now in
xend. So we turn on this code:

        # ideally we would like to forcibly crash the domain with
        # something like
        #    xc.domain_shutdown(self.vm.getDomid(), DOMAIN_CRASH)
        # but this can easily lead to very rapid restart loops against
        # which we currently have no protection

(The comment being completely incorrect), but then the crash doesn't
work because of the bug I pointed out.

All I want to do is mark a domain without a qemu process as crashed. Is
that clearer?

And yes, it's pretty trivial to make qemu break. Most typically by
passing bogus parameters (say, a broken kernel image, an incorrect NIC,
etc.)

regards,
john

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