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] Crashing a guest domain

To: Kieran Mansley <kmansley@xxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Crashing a guest domain
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 24 Sep 2007 16:16:10 +0100
Delivery-date: Mon, 24 Sep 2007 08:16:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1190646503.4169.15.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: Acf+vdY9FMMUOmqxEdyHAwAX8io7RQ==
Thread-topic: [Xen-devel] Crashing a guest domain
User-agent: Microsoft-Entourage/
If you want to crash it as in shut it down, and execute crash hooks in the
toolstack, then SCHEDOP_remote_shutdown is what you want. After that call,
the guest will no longer be runnable and will be in state 'shutdown' with
reason code 'crashed'. If you actually want to get an oops message in the
guest, or something like that, then you somehow need to inject a crash fault
into the guest. There's no Xen support for doing that.

Your problem may be that the guests' config file specified
'on_crash=preserve', in which case the guest will be hanging around after
your remote shutdown request!

 -- Keir

On 24/9/07 16:08, "Kieran Mansley" <kmansley@xxxxxxxxxxxxxx> wrote:

> The problem I'm trying to solve is how, from dom0, to crash a guest
> domain.  The reason for wanting to do this is when dom0 detects that the
> guest is misbehaving (in this specific example, claiming it has stopped
> using a grant when in fact it hasn't) the most sensible action is to
> crash it.  Rather like BUG(), but where the effect should be to crash
> the misbehaving guest rather than the caller.
> I've not been able to dig up anything that obviously does this.  Is
> there an API to do it?  I'd hoped that a HYPERVISOR_sched_op with
> SCHEDOP_remote_shutdown might do the trick, but it appears not to
> (returns zero, but no visible effect).
> Thanks
> Kieran
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>