All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: [PATCH] VM-Tool: C-based Xen management tools
Date: Fri, 11 Feb 2005 16:29:21 -0600	[thread overview]
Message-ID: <420D31C1.1010407@us.ibm.com> (raw)
In-Reply-To: <420D2FA6.10905@us.ibm.com>

Nivedita Singhvi wrote:

> The tools are still very rough.  This version is pretty much a 
> proof-of-concept.  It should not be used in a production environment.  
> In fact, you shouldn't use them with any domains that are important to 
> you.  While I've never seen any data corruption caused by the tools 
> there's just not been enough testing yet.
>
> Can you tell us on what you tested, and which configurations, so far?

Sure, I've tested on Fedora Core 3 and on Gentoo both running various 
copies of xen-unstable (ranging from a few weeks ago to a day ago).  
There are a number of others (Mike, Woody, Dan) that have tested on 
other platforms.

By tested, I mean was able to create and destroy domains with various 
arrangements of block devices and network devices (0, 1, 2, etc, etc.).  
I've tested using a custom busybox based ramdisk and ttylinux as DomU.  
Other DomU configuration should also work (although haven't been tested).

> Are you going to be doing the USB and PCI stuff as well?
> Will you need any help on that?

Yes, the goal was to minimize the amount of features to the least amount 
required before release.  We're very interested in hearing feedback on 
what the tools should look like.

USB and PCI support isn't that hard.  Doing in a way that people feel is 
intuitive is another matter.  Feed-back on what sort of interfaces these 
tools should have is extremely useful.

> So there will be no effort to backport, correct?

That depends on demand.  The tools could be modified to open the 
controls channels directly instead of going through xcs, but I'd rather 
encourage an xcs based world where Xend and vm-tools can live together.  
Of course, if someone was willing to backport the old Xend to xcs... :-)

Thanks,
Anthony Liguori


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-11 22:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 21:53 [PATCH] VM-Tool: C-based Xen management tools Anthony Liguori
2005-02-11 22:20 ` Nivedita Singhvi
2005-02-11 22:29   ` Anthony Liguori [this message]
2005-02-11 22:38     ` Mark Williamson
2005-02-14 16:10       ` Anthony Liguori
2005-02-14 16:35         ` Mark Williamson
2005-02-14 17:15           ` Anthony Liguori
2005-02-14 17:19             ` Mark Williamson
2005-02-14 19:37               ` Anthony Liguori
2005-02-20  2:23 ` Jacob Gorm Hansen
2005-02-20  3:31   ` Anthony Liguori
2005-02-20  3:36     ` Jacob Gorm Hansen
2005-02-20  4:12       ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2005-02-15  4:41 Neugebauer, Rolf

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=420D31C1.1010407@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=niv@us.ibm.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.