| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] capturing windows crash dumps
> On 18/08/2009 07:47, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
>
> > 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).
>
> 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.
James
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home