From mboxrd@z Thu Jan 1 00:00:00 1970 From: Max Krasnyansky Subject: Re: [Qemu-devel] Re: [PATCH 2/5] husb: support for USB host device auto connect. Date: Mon, 18 Aug 2008 11:46:19 -0700 Message-ID: <48A9C37B.3070704@kernel.org> References: <48A46033.3070200@codemonkey.ws> <48A489D3.5070900@kernel.org> <48A493DE.40506@codemonkey.ws> <48A496E9.2030800@kernel.org> <48A49878.1010502@codemonkey.ws> <20080815074638.GA31016@bogon.ms20.nix> <48A5C9F2.5080400@kernel.org> <48A7D8CA.4050803@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: =?ISO-8859-1?Q?Guido_G=FCnther?= , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from hera.kernel.org ([140.211.167.34]:44018 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754109AbYHRSqg (ORCPT ); Mon, 18 Aug 2008 14:46:36 -0400 In-Reply-To: <48A7D8CA.4050803@qumranet.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > Max Krasnyansky wrote: >> btw Interface to HAL might still be useful in general to monitor other >> device >> classes that we may want to automatically assign to the VMs. So I'll play >> around with that too (some day :)). >> > > Assign to which VMs? > > Interfacing with HAL is definitely the management layer's tasks, not > qemu, which only knows about one guest. With my USB patches you can now do qemu -name VM1 ... -usb -usbdevice host:5.* which will dynamically grab any USB device that is attached to port 5. And you can start another instance with qemu -name VM2 ... -usb -usbdevice host:6.* and so on. That's what I meant by assigning to the VM. ie In the example above port5 is assigned to VM1 and port6 to VM2. We might want to do this with other devices (disks maybe). Max