From: Daniel Veillard <veillard@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [Libvir] virDomainDump() API (equivalent to xm dump) in libvirt?
Date: Fri, 3 Nov 2006 11:56:55 -0500 [thread overview]
Message-ID: <20061103165655.GS28384@redhat.com> (raw)
In-Reply-To: <1162571792.4518.485.camel@rei.boston.devel.redhat.com>
On Fri, Nov 03, 2006 at 11:36:32AM -0500, Lon Hohberger wrote:
> On Fri, 2006-11-03 at 10:53 -0500, Daniel Veillard wrote:
> > - can we implement it with current xen, again yes, we should be able
> > if we have a full connection (root) to do the same as 'xm dump-core'
>
> Yes, given that xm dump-core can do it ;)
>
> > - is the API clean enough, I guess the semantic is relatively clear
> > instead of stating 'If you set the lowest-bit in flags' I would rather
> > define a DumpFlags enum and state that flags is an or'ing of any of them
> > I would probably name the function virDomainDumpCore though to not
> > confuse with virDomainSave
>
> Totally correct here, it should be an enum of flags (with only one
> defined initially; I don't know what other flags there might be.
>
> > So yes, why not, you want to work on it ? Or should I (or any candidate).
>
> Give me a few; I'll check on this. I don't have problems trying it, but
> I will have a learning curve of course.
Let's see if I was to do it I would:
0/ check out a CVS tree http://libvirt.org/downloads.html
1/ look how xm communicate with xend on that command
2/ isolate another similar entry point from xend_internal.c and
see how to generate the same kind of command but for the core dump
for example xenDaemonDomainSave ()
test by linking statically from a small test program
then the next steps are rather integration problems
3/ extend the back-end driver to add a DumpCore entry point and the
enum in the header (beware it's include/libvirt/libvirt.h.in)
4/ modify all the drivers to have NULL entry points except for the
virDriver xenDaemonDriver one adding the new function at the end.
5/ create the real entry point in libvirt.c, add the initial check for
the flag and the domain status
basically if you just have 1 and 2, sending the diff here I can take care
quickly of the purely integration details,
hope this helps,
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
next prev parent reply other threads:[~2006-11-03 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 15:38 [Cluster-devel] virDomainDump() API (equivalent to xm dump) in libvirt? Lon Hohberger
2006-11-03 15:53 ` [Cluster-devel] Re: [Libvir] " Daniel Veillard
2006-11-03 16:36 ` Lon Hohberger
2006-11-03 16:40 ` Lon Hohberger
2006-11-03 16:56 ` Daniel Veillard [this message]
2006-11-16 15:36 ` Daniel Veillard
2006-11-22 17:01 ` Daniel Veillard
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=20061103165655.GS28384@redhat.com \
--to=veillard@redhat.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.