From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH 2 of 2] xl: Accept a list for usbdevice in config file Date: Thu, 29 Nov 2012 12:27:36 +0000 Message-ID: <50B754B8.40900@eu.citrix.com> References: <20121128151119.GC8912@reaktio.net> <1354187200.25834.143.camel@zakaz.uk.xensource.com> <50B74AA8.3090504@eu.citrix.com> <1354191956.25834.169.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1354191956.25834.169.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 29/11/12 12:25, Ian Campbell wrote: > On Thu, 2012-11-29 at 12:20 +0000, George Dunlap wrote: >> On Thu, Nov 29, 2012 at 11:44 AM, George Dunlap >> wrote: >> qemu.git/vl.c suggests other options might include, "disk:", >> "serial:", "net:" and "bt:"; other non-colon-including options >> include "keyboard", "mouse", "wacom-tablet", and "braile". >> >> On the other hand, a number of these seem to require >> supplementary options to work well; e.g., network and bt >> (bluetooth) require one argument to hook up a USB device, and >> another option to say how it's connected to what. >> >> It's also interesting to note that the KVM documentation >> doesnt' mention using "-usb" and "-usbdevice" at all -- they >> seem to prefer using "-device" to specify hubs &c. >> >> Speaking of which, the KVM docs refer to "-usb" and "-usbdevice" as >> "legacy interfaces", which will only get you piix3. > This is a concern for other types of device too. We seem to invoke new > qemu with a mixture of legacy and new-style interfaces. > >> It seems like exposing the full capabilities of qemu would mean >> either 1) coming up with a full specifciation which we can then >> translate into qemu directives, as libvirt seems to do, or 2) just >> recommend people construct their own qemu command-line options to pass >> through. > Does libvirt let you care about topologies or just it just automatically > create a new USB controller for every N devices you add and hook things > up in some order? No idea -- I took a quick glance through the libvirt docs and I didn't see anything particular about a topology. I don't have a system set up with libvirt, so I can't try it and see what the resulting qemu command line looks like :-) http://libvirt.org/formatdomain.html#elementsUSB -George