From: "James Harper" <james.harper@bendigoit.com.au>
To: xen-devel@lists.xensource.com
Subject: produce windows compatible dump file from Dom0
Date: Wed, 23 Feb 2011 22:07:19 +1100 [thread overview]
Message-ID: <AEC6C66638C05B468B556EA548C1A77D01C558B2@trantor> (raw)
I'm interested in being able to produce a windows dump file from Dom0,
which would help immensely in tracking down crashes when they happen.
What it would involve is:
. PV driver would need to prepare a crash dump header via Windows API
(in advance, and then at crash dump time if possible), store it in
non-paged memory, and write the PFN out to xenstore
. xc would need to detect a parameter (eg -w), check for the value in
xenstore, then write out that as the header and then write out the rest
of the data in windows dump format. The header could also be detected by
scanning memory (eg if the crash happened before xenbus was able to
start) but would be a bit less reliable.
It might also be possible to manufacture the header from Dom0, but I
can't say for sure.
Does this feature or similar already exist in any incantations of the
dom0 tools?
If not, would it be considered for inclusion into some future version of
xen?
Thanks
James
next reply other threads:[~2011-02-23 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 11:07 James Harper [this message]
2011-02-23 13:34 ` produce windows compatible dump file from Dom0 Paul Durrant
2011-02-23 22:15 ` James Harper
2011-05-25 9:54 ` David Markey
2011-05-25 10:17 ` Tim Deegan
2011-05-25 12:16 ` James Harper
2011-05-26 12:52 ` Konrad Rzeszutek Wilk
2011-11-08 15:15 ` David Markey
2011-11-08 15:40 ` Konrad Rzeszutek Wilk
2011-11-08 16:20 ` Paul Durrant
2011-11-08 16:28 ` David Markey
2011-11-08 16:48 ` Paul Durrant
2011-11-08 22:04 ` Tim Deegan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AEC6C66638C05B468B556EA548C1A77D01C558B2@trantor \
--to=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).