From: Anthony Liguori <aliguori@us.ibm.com>
To: Mark Williamson <maw48@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, Nivedita Singhvi <niv@us.ibm.com>
Subject: Re: [PATCH] VM-Tool: C-based Xen management tools
Date: Mon, 14 Feb 2005 10:10:06 -0600 [thread overview]
Message-ID: <4210CD5E.7030207@us.ibm.com> (raw)
In-Reply-To: <200502112238.39080.maw48@cl.cam.ac.uk>
Mark Williamson wrote:
>Nice work!
>
>
Thanks :-)
>As far as making the interface intuitive... I think it's reasonably sane to
>specify this stuff the way the current tools do, although arguably it would
>be useful to have some sort of abstraction so that users don't have to think
>about PCI config space / USB port IDs.
>
>
Yes, PCI wouldn't be too hard to abstract. Abstracting USB worries me a
bit though. On the one hand, you want to abstract at the device level.
However, not all USB devices make it easy to be uniquely identified (too
much optional information). This is a problem the devfs/udev guys have
faced.
It's even hairer with virtualization though. Say you had two harddrives
that were USB and not uniquely identifiable. You want to assign each
harddrive to a separate VM. If you unplug them and swap ports, and
you're using the old configurations, you really want that each VM to see
the harddrive they previously saw. Swapping them could lead to
confusion and even worse, security problems.
Not sure the best solution here. One of the reasons I've held off on USB.
Regards,
>Cheers,
>Mark
>
>
>
>>>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
next prev parent reply other threads:[~2005-02-14 16:10 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
2005-02-11 22:38 ` Mark Williamson
2005-02-14 16:10 ` Anthony Liguori [this message]
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=4210CD5E.7030207@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=maw48@cl.cam.ac.uk \
--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.