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] capturing windows crash dumps

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] capturing windows crash dumps
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Tue, 18 Aug 2009 16:47:59 +1000
Delivery-date: Mon, 17 Aug 2009 23:48:26 -0700
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
Thread-index: Acofz9MVLlNDi4WlRf6lT2clrHIXXw==
Thread-topic: capturing windows crash dumps
Windows has provision for a driver to get called when a bug check occurs
(KeRegisterBugCheckCallback etc), and also to get called every time some
data is to be written to the dump file.

I would like to be able to capture that information into Dom0 somehow,
as a few of the bug check's I've had in GPLPV in the past have rendered
the block device driver inoperable and therefore unable to write out the
dump file.

Is there an existing communication channel that could be used for this
or do I need to invent write my own? The more low level the better (as
in xenstore may not be accessible depending on the circumstances of the
crash).

Thanks

James


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