Re: [Xen-devel] capturing windows crash dumps

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 20/08/2009 10:56, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

> I like #2 best for the following reasons:
> . qemu needs patching for a second serial port anyway. I don't want to
> use the primary as I'm already using it for something else in the
> environment I'm thinking of.
> . much more efficient
> . works with PV (irrelevant though if there are no PV domains that
> support writing out a dump file)
> . easy for the DomU to tell if there is something waiting to capture the
> crash dump (no parameter present = no crash dump)
> . less code on the windows side of things, vs trying to access the
> serial port hardware directly for which there is no 'blessed' mechanism
> to do in a crash dump environment afaik

Well, obviously you can knock up #2 yourself, with an accompanying little
dom0 daemon, which you can ship with the GPLPV drivers. The two components
can communicate via xenstore at start-of-day to prime themselves for later
possible crash dumps.

 -- Keir



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