From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [PATCH 2 of 2] xl: Accept a list for usbdevice in config file Date: Thu, 29 Nov 2012 17:03:11 +0200 Message-ID: <20121129150311.GG8912@reaktio.net> 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" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline 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: George Dunlap , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Thu, Nov 29, 2012 at 12:25:56PM +0000, 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? > Not sure about libvirt.. quick googling suggests that libvirt doesn't allow specifying the usb controller. with qemu-kvm you can assign host usb devices to specific usb controllers using the "bus=" option: http://www.linux-kvm.com/content/qemu-kvm-11-adds-experimental-support-usb-30 qemu-kvm -device nec-usb-xhci,id=xhci -device usb-storage,bus=xhci.0,drive=usbstick -- Pasi