From: Max Krasnyansky <maxk@kernel.org>
To: Avi Kivity <avi@qumranet.com>
Cc: "Guido Günther" <agx@sigxcpu.org>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
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 [thread overview]
Message-ID: <48A9C37B.3070704@kernel.org> (raw)
In-Reply-To: <48A7D8CA.4050803@qumranet.com>
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
next prev parent reply other threads:[~2008-08-18 18:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 4:22 [Qemu-devel] [PATCH 0/5] Various USB fixes and improvements Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] [PATCH 1/5] husb: support for USB host device auto disconnect Max Krasnyansky
2008-08-14 16:28 ` [Qemu-devel] " Anthony Liguori
2008-08-14 19:26 ` Max Krasnyansky
2008-08-14 21:41 ` Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] [PATCH 2/5] husb: support for USB host device auto connect Max Krasnyansky
2008-08-14 16:41 ` [Qemu-devel] " Anthony Liguori
2008-08-14 19:38 ` Max Krasnyansky
2008-08-14 20:21 ` Anthony Liguori
2008-08-14 20:34 ` Max Krasnyansky
2008-08-14 20:41 ` Anthony Liguori
2008-08-14 21:14 ` François Revol
2008-08-15 7:46 ` Guido Günther
2008-08-15 18:24 ` Max Krasnyansky
2008-08-15 18:31 ` Javier Guerra
2008-08-18 18:21 ` Max Krasnyansky
2008-08-18 18:52 ` Javier Guerra
2008-08-18 18:56 ` Jamie Lokier
2008-08-17 7:52 ` Avi Kivity
2008-08-18 18:46 ` Max Krasnyansky [this message]
2008-08-18 14:11 ` Anthony Liguori
2008-08-18 18:16 ` Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] [PATCH 3/5] usb: generic packet handler cleanup and documentation Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] [PATCH 4/5] uhci: rewrite UHCI emulator, fully async operation with multiple outstanding transactions Max Krasnyansky
2008-08-14 17:51 ` [Qemu-devel] " Anthony Liguori
2008-08-14 19:49 ` Max Krasnyansky
2008-10-11 23:54 ` [Qemu-devel] " Juergen Lock
2008-10-15 19:54 ` Max Krasnyansky
2008-10-15 22:05 ` andrzej zaborowski
2008-10-16 21:25 ` Juergen Lock
2008-08-14 4:22 ` [Qemu-devel] [PATCH 5/5] husb: rewrite Linux host USB layer, fully async operation Max Krasnyansky
2008-08-15 14:24 ` Paul Brook
2008-08-15 19:04 ` Max Krasnyansky
2008-08-15 19:53 ` Paul Brook
2008-08-18 18:40 ` Max Krasnyansky
2008-08-14 17:55 ` [Qemu-devel] Re: [PATCH 0/5] Various USB fixes and improvements Anthony Liguori
2008-08-14 19:55 ` Max Krasnyansky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A9C37B.3070704@kernel.org \
--to=maxk@kernel.org \
--cc=agx@sigxcpu.org \
--cc=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).