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-devel] xm shutdown timeout

To: John Levon <levon@xxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm shutdown timeout
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 23 May 2007 09:11:46 +0100
Delivery-date: Wed, 23 May 2007 01:10:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070523025146.GA17438@xxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcedEgFKQCWjfgkFEdyD7QAX8io7RQ==
Thread-topic: [Xen-devel] xm shutdown timeout
User-agent: Microsoft-Entourage/

On 23/5/07 03:51, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

> xend has a timeout such that if an 'xm shutdown' request does not result
> in the domain shutting down within a certain time period, the domain is
> violently destroyed.
> This seems like a strange choice - if the domain isn't responding
> properly to such requests, then it must be in a buggy state, and should
> surely be preserved for administrator action (dumping core, destroying,
> whatever).
> Is there any other purpose to this timeout?

There are a set of config options to choose what to do on various guest
state transitions. I think these are probably what you're looking for. See
the final bit of tools/example/xmexample1.

Hmmm... Actually it may be that we unconditionally kill the domain if it
ignores shutdown. If that is the case, we should instead force it into
whatever the the target of the 'sm shutdown' command was, and then execute
the action specified in the config file. We'd like a patch if this is the
case. :-)

 -- Keir

Xen-devel mailing list