All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@fsmware.com>
To: Rolf Neugebauer <rolf.neugebauer@intel.com>
Cc: mark.williamson@cl.cam.ac.uk, xen-devel@lists.sourceforge.net
Subject: Re: xm pause <domain>
Date: Wed, 26 Jan 2005 09:02:30 -0800 (PST)	[thread overview]
Message-ID: <20050126085901.Q41276@demos.bsdclusters.com> (raw)
In-Reply-To: <1106758049.21057.19.camel@wyvis.research.intel-research.net>

>
> why do you want to add this to xend? I might be missing something here,
> but can't you just provide a stand-alone util to do this.
>
I'd like it be possible as an option to have xen, before destroying a
domain, dump its core. This would require notifying xend. I'd also like
to add a HYPERVISOR_panic(char *) call so that guests can dump core
before going off into the weeds.



				-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

  reply	other threads:[~2005-01-26 17:02 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
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 [this message]
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=20050126085901.Q41276@demos.bsdclusters.com \
    --to=kmacy@fsmware.com \
    --cc=mark.williamson@cl.cam.ac.uk \
    --cc=rolf.neugebauer@intel.com \
    --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.