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

On Wed, 2005-01-26 at 16:23, Mark A. Williamson wrote:
> > I've written the code for a generic xen guest coredump, I'll write a
> > separate tool to post-process the header into something either LKCD or
> > FreeBSD's gdb will recognize.
> 
> Cool.
> 
> > Now the question is, can you give me some guidance on adding it into
> > xend - it doesn't look as straightforward as I had hoped.
> 
> You'll need a function in tools/libxc/ that'll do the dump (I guess this is 
> what you have already).
> 
> Then you'll need to add a Python wrapper for this function in 
> tools/python/xen/lowlevel/xc/xc.c.  This shouldn't be too hard, using the 
> other functions in there as a template...

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. 

having bindings both for C (in libxc) and in python would still be
useful.

Rolf

> Finally you'll need to provide a means to dump using the xm tool.  This 
> touches quite a few files, I'm afraid, although none of them require complex 
> changes...
> 
> It looks like you'll need to edit:
> * tools/python/xen/xm/main.py to add a subprogram for doing a dump.
> * tools/python/xen/xend/XendClient.py to add a method for requesting a dump 
> from the server
> * tools/python/xen/xend/server/SrvDomain.py to add an operation for dumping a 
> domain (this will get activated when the client makes a request)
> * tools/python/xen/xend/XendDomain.py to add a domain_dump() method to be 
> called by SrvDomain.py (this will pause the domain, call your Xc dump 
> function and unpause it)
> 
> You may find it helpful to compare the call paths triggered by a destroy or a 
> save, which will be similar to what you want.
> 
> For icing on the cake, you could also rig up some kind of dumping in the 
> reap() function in XendDomain.py to autodump crashed domains before 
> restarting / destroying them.
> 
> HTH,
> Mark
> 
> 
> -------------------------------------------------------
> 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
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
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 16:47 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 [this message]
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=1106758049.21057.19.camel@wyvis.research.intel-research.net \
    --to=rolf.neugebauer@intel.com \
    --cc=kmacy@fsmware.com \
    --cc=mark.williamson@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.