From: Kip Macy <kmacy@fsmware.com>
To: Mark Williamson <maw48@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, Chotu Ram <chotwo@hotmail.com>
Subject: Re: xm pause <domain>
Date: Sun, 23 Jan 2005 15:34:15 -0800 (PST) [thread overview]
Message-ID: <20050123152519.C63308@demos.bsdclusters.com> (raw)
In-Reply-To: <200501232314.11757.maw48@cl.cam.ac.uk>
> Cool!
Enthusiasm is always welcome :-).
>
> Some information here:
> http://lkcd.sourceforge.net/doc/linuxworld2000/LKCD.html
>
> There may be some more hanging around somewhere - I suspect that's the paper I
> remembered reading...
>
> Of course, for non-Linux guests these tools won't necessarily be much (any?)
> use, so ELF format core files might prove more generally useful (I don't know
> if the LKCD lcrash tool can support ELF dump files - it'd be real nice if it
> did).
Having worked _briefly_ with elf coredumps as a starting point for
process checkpointing, I don't think they would be well suited for this.
An elf coredump defines all of a running applications mappings in the
program header. In a VM, there will be MANY mappings, which may be
fragmented, corresponding to many page directory pointers. If all I
cared about were the kernel state, that would be fine, but I think users
would like to be able to see what processes were doing at the time.
Examining the user-state will of course be very OS-specific.
Nonetheless, I think that it is important that the information be there,
so that if someone does choose to develop the tool, the pieces will
already be there.
Any corrections or contrary opinions are welcome ...
-Kip
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-23 23:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 15:14 xm pause <domain> Chotu Ram
2005-01-23 14:41 ` Mark Williamson
2005-01-23 23:09 ` Kip Macy
2005-01-23 23:14 ` Mark Williamson
2005-01-23 23:34 ` Kip Macy [this message]
2005-01-24 0:46 ` Mark Williamson
2005-01-26 2:56 ` Kip Macy
2005-01-26 16:23 ` Mark A. Williamson
2005-01-26 16:47 ` Rolf Neugebauer
2005-01-26 17:02 ` Kip Macy
2005-01-26 19:57 ` Mark Williamson
2005-01-24 22:51 ` Daniel Stekloff
2005-01-25 13:46 ` Mark Williamson
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=20050123152519.C63308@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=chotwo@hotmail.com \
--cc=maw48@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.