Re: [Xen-devel] USB virtualization question

[Xin Zhao <zhaoxin@xxxxxxxxxxxxxx>]

Thanks. Mark and Harry.

Now I understand the current status.

-x



On Fri, 6 May 2005, Mark Williamson wrote:

> > Thanks a lot for your reply. But what I really want to know is the
> > feasibility of differentiating
> > multiple USB ports and restrict ,say, USB port1 to be accessed by a
> > specified virtual machine.
>
> You can give different USB ports to different domains.  This should work even
> for devices on hubs.
>
> > Your reply sounds like differentiation is doable, but whether you
> > can do access control on certain ports is undetermined. Is my
> > interpretation right?
>
> Something else we'd like to have (which I think Harry was referring to) is the
> ability to associate *particular devices* with a virtual machine and give it
> access to them regardless of where you plug in.  E.g. your domain will get
> access to your digital camera, no matter when / where you plug it in.  We'd
> like to build this in later.
>
> Cheers,
> Mark
>
> >
> > Thanks,
> > -x
> >
> > On Fri, 6 May 2005, Harry Butterworth wrote:
> > > On Fri, 2005-05-06 at 02:46 -0400, Xin Zhao wrote:
> > > > Is it possible to differentiate multiple USB ports and assign one port
> > > > to be used only by a specified virtual machine when doing usb
> > > > virtualization?
> > >
> > > This is the intended behaviour of the current 2.4 code and the 2.6 code
> > > I'm working on will also implement this behaviour.  There is a question
> > > as to whether we want to be able to assign specific devices to virtual
> > > machines when they are plugged in regardless of the port.  This feature
> > > might be added later.
> > >
> > > I've only tested the 2.4 code with one device and one front end domain
> > > though so I can't guarantee it actually works.
> > >
> > > > As USB devices are enumerated, I don't see a way to do that.
> > > >
> > > > Any insignts on this issue?
> > > >
> > > > Thanks in advance!
> > > >
> > > > -x
> > > >
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-devel
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel