[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] capturing windows crash dumps


  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Tue, 18 Aug 2009 22:16:33 +1000
  • Cc:
  • Delivery-date: Tue, 18 Aug 2009 05:17:00 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acofz9MVLlNDi4WlRf6lT2clrHIXXwACTnrJAAPGsMAABTJUowAAJgrg
  • Thread-topic: [Xen-devel] capturing windows crash dumps

> On 18/08/2009 11:42, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> >> Could it be as simple as write the guest physical address of a
> > pre-allocated
> >> buffer into xenstore (from GPLPV drivers)? Then dump that area of
> > guest
> >> memory on guest bugcheck, even as a manual operation from dom0?
> >
> > The memory in question could be anything from 64kb (minidump) to the
> > size of DomU memory (full dump) or somewhere inbetween (kernel
dump).
> > I'm normally just interested in the kernel dump which is normally a
much
> > more respectable size, but still not the size of memory you can
easily
> > find when the system has gone belly up.
> 
> Hmm, okay. Could you dump it out over the emulated serial line?
> 

I was thinking about that. It could work, then I could just do 'xm
console <domu> >dump' and parse the dump from there or something.

James


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.