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] [PATCH] Add tool to attempt to crash HVM guests

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Add tool to attempt to crash HVM guests
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Thu, 29 Jul 2010 16:57:33 +0100
Cc: Paul Durrant <Paul.Durrant@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 29 Jul 2010 09:02:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19537.41851.741783.702287@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <c28224c0f0657aa29c13.1280326524@xxxxxxxxxxxxxxxxxxxxx> <19537.41851.741783.702287@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Thu, 29 Jul 2010, Ian Jackson wrote:
> Paul Durrant writes ("[Xen-devel] [PATCH] Add tool to attempt to crash HVM 
> guests"):
> > This tool reads the CPU save records, overwrites RIP with a bogus
> > value, and then restores them. This is, of course, not guaranteed
> > to crash the guest (since the CPUs may not be executing in kernel
> > at the time) but it's good for breaking into some tight loops that
> > would be hard to debug otherwise.
> 
> Surely there must be a better way of doing this!  Isn't it sufficient
> to pause the guest and then inspect it ?  Or do we need a new domctl
> to crash the guest explicitly ?
> 

Explicitly crashing the guest can be very useful for testing, I had to
use this tool myself few times...

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