From: Don Zickus <dzickus@redhat.com>
To: xen-devel@lists.xensource.com
Subject: capturing a dom0 corefile
Date: Tue, 21 Mar 2006 10:50:41 -0500 [thread overview]
Message-ID: <20060321155041.GB12138@redhat.com> (raw)
I was trying to look at how a corefile for dom0 could be captured by the
hypervisor when the dom0 kernel on linux panics.
Is it difficult to start another dom0 kernel, which in turn would run the
userspace tools to collect the memory contents of the original dom0
kernel? Or even better, can I start a backup dom0 by loading and pausing
it and upon the first dom0 panicing, unpause the backup?
I know lots of people have talked about dom0 failovers and how
straightforward they should be. But before I started hacking away, I
wanted to understand the right direction.
Any thoughts or suggestions would be great.
Cheers,
Don
reply other threads:[~2006-03-21 15:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060321155041.GB12138@redhat.com \
--to=dzickus@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.