From: Anthony Liguori <anthony@codemonkey.ws>
To: Mark Williamson <maw48@cl.cam.ac.uk>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
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 11:15:22 -0600 [thread overview]
Message-ID: <4210DCAA.2050200@codemonkey.ws> (raw)
In-Reply-To: <200502141635.48773.maw48@cl.cam.ac.uk>
Mark Williamson wrote:
>The current implementation sidesteps all these by specifying port IDs. e.g.
>port 1 on my root hub always belongs to VM1 (when running), port 2 on hub 3
>always belongs to VM2 (when running), etc.
>
>
Yeah, I think we'll always have to support this as a fallback option.
>>Not sure the best solution here. One of the reasons I've held off on USB.
>>
>>
>
>For comparison, do you know what abstraction other systems do? Do they assign
>ports or associate devices with VMs?
>
>
Not sure. The only thing I know that does USB virtualization is VMware
and I've not played with that feature (I think it's a relatively new
feature).
udev/namedev have to deal with this to ensure that devices have a unique
(and consistent) /dev entry. It currently uses a tiered approach to
determine exactly what the device is. It's not perfect but it works
reasonably well. The best link I could find explaining it with a quick
google is:
http://www.gentoo.org/doc/en/udev-guide.xml
A GUI would be really handy for PCI/USB because it would provide an easy
way to pick devices by name (instead of specifying an series of
identifiers/bus/etc in the config).
>The latter is definitely an attractive option... If we added support for both
>ways of doing things, paranoid people (or people with weird devices!) could
>use the port specifiers, whilst others used device IDs.
>
>
I agree completely. I'm currently adding proper documentation to
vm-tools but after that's done I'll add USB virtualization and try to
implement a mechanism to select by device ID and push out another
version to the list.
Regards,
--
Anthony Liguori
anthony@codemonkey.ws
-------------------------------------------------------
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 17:15 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
2005-02-14 16:35 ` Mark Williamson
2005-02-14 17:15 ` Anthony Liguori [this message]
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=4210DCAA.2050200@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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.