From: Daniel Stekloff <dsteklof@us.ibm.com>
To: xen-devel@lists.xensource.com
Cc: Charles Coffing <ccoffing@novell.com>, christian.limpach@gmail.com
Subject: Re: Control tools work
Date: Tue, 31 May 2005 14:48:53 -0700 [thread overview]
Message-ID: <200505311448.53675.dsteklof@us.ibm.com> (raw)
In-Reply-To: <s29c82f6.031@sinclair.provo.novell.com>
On Tuesday 31 May 2005 14:29, Charles Coffing wrote:
> Christian,
>
> I've done a pull and now see the functionality in XendCheckpoint.py; thanks
> for the heads-up.
>
> But how do you see things outside of xm & xend accessing this
> functionality? In particular, I'm thinking of a CIMOM provider written in
> C++. Forking/exec-ing an "xm migrate" command is less than ideal, for
> several reasons (progress reporting, error reporting without having to grok
> text, overhead on a busy server, ...) In my ideal world, this level of
> functionality would be in C or C++ libraries, so you can put whatever you
> want on top of it, be it Python commands or C++ CIMOM code or anything
> else.
>
> I don't necessarily want to revive the old Python debate, but this does
> complicate things.
Hi Charles,
Please look at vm-tools, a set of C tools for managing Xen systems. It's a
work in progress, but it's coming along. We have single purpose C tools that
can easily be used to do what you require, whether wrapping them with scripts
or accessing them directly.
Here's Anthony's post mentioned the latest version:
http://lists.xensource.com/archives/html/xen-devel/2005-05/msg01080.html
Here's where to get it:
http://www.cs.utexas.edu/users/aliguori/vm-tools/
Thanks,
Dan
next prev parent reply other threads:[~2005-05-31 21:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 21:29 Control tools work Charles Coffing
2005-05-31 21:48 ` Daniel Stekloff [this message]
2005-05-31 22:25 ` Steven Hand
2005-06-01 0:25 ` Christian Limpach
2005-06-03 1:01 ` Anthony Liguori
[not found] <s29d6a51.010@sinclair.provo.novell.com>
2005-06-01 20:13 ` Christian Limpach
-- strict thread matches above, loose matches on Subject: below --
2005-06-01 13:56 Charles Coffing
[not found] <s29c82f6.030@sinclair.provo.novell.com>
2005-06-01 0:15 ` Christian Limpach
2005-05-31 17:57 Charles Coffing
2005-05-31 21:07 ` Christian Limpach
2005-05-31 23:33 ` Jacob Gorm Hansen
2005-06-01 10:28 ` Grzegorz Milos
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=200505311448.53675.dsteklof@us.ibm.com \
--to=dsteklof@us.ibm.com \
--cc=ccoffing@novell.com \
--cc=christian.limpach@gmail.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.