[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v7 RFC 0/2] libxl USB prototype and design discussion

On 06/18/2014 01:57 PM, Ian Campbell wrote:
* Is it possible for the toolstack to tell if domU has a working and
connected PVUSB front-end?
It can observe the state variable being 4 I suppose. Why do you need to

It might be nice to be able to create both a pv and an emulated controller in the config file, and then have "xl usb-attach [foo]" to automatically plug it into the PV controller if the PV frontend seems to be up, and into the emulated controller if it doesn't seem to be up.

But that doesn't change the elements of the interface, just what the default would be if the controller field is empty.

* Do we want to be able to create virtual hubs for qemu-backed
controllers at some point in the future?  Is there any groundwork we
want to lay for that?
qemu-backed emulated or PV controllers?

I don't think emulated would make sense for a PV guest and if qemu
wanted to be a PV backend it would have to implement the usual xenstore
watches etc.

I mean, emulate an actual USB hub -- you know, it plugs into your USB controller and you can plug other USB devices into it.

I'm inclined not to bother with it at this point.

-- snip --

Given that, here is a potential config file format:

-- snip --
# Create two controllers, one pv, one emulated

# Create a controller with the defaults; PV for PV guests, emul for HVM guests

# Same as above, but defaulting to version 2

# I think we should be able to automatically detect which format to
# use; so I think we should re-use usbdevice.  I could be convinced otherwise.
Does this require that the usbcontroller have been specified?

I think it would be good if xl would by default create some number of
appropriate controllers without my having to specify them explicitly,
iow just saying usbdevice=[...] should be enough.

I'm not saying that you shouldn't support more specific syntax for
people who want more control, just that it shouldn't be required to do

(I'm just talking xl here, at the libxl layer I think it would be fine
to require them to be explicit).

That makes sense.

* Rather than having to specify a controller, automatically hot-plug
controllers as-needed.
At the xl level I think this would be good.

OK, sounds good.  Thanks for the input.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.