From: Gordan Bobic <gordan@bobich.net>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: usbdevice option and specifying a specific device
Date: Mon, 05 Aug 2013 12:27:51 +0100 [thread overview]
Message-ID: <53656e1e164ffe2568a9ec0116fead16@mail.shatteredsilicon.net> (raw)
In-Reply-To: <51FF8B78.8070504@eu.citrix.com>
On Mon, 5 Aug 2013 12:24:40 +0100, George Dunlap
<george.dunlap@eu.citrix.com> wrote:
> On 31/07/13 11:12, Ian Campbell wrote:
>> On Wed, 2013-07-31 at 09:25 +0100, George Dunlap wrote:
>>> On 30/07/13 09:23, Ian Campbell wrote:
>>>> On Mon, 2013-07-29 at 20:17 +0100, Gordan Bobic wrote:
>>>>> I'm trying to use usbdevice option in the config file (instead of
>>>>> passing USB PCI devices), and the documentation says to specify
>>>>> the
>>>>> device in the form host:xxxx:yyyy where xxxx:yyyy is the USB
>>>>> vendor:device ID.
>>>>>
>>>>> Except there is a problem with this - I have two identical
>>>>> keyboards and
>>>>> mice, one set of which I want to pass to the host, and the other
>>>>> set
>>>>> which I want to pass to the guest. Since the xxxx:yyyy will be
>>>>> the same
>>>>> for both devices of each type, how can I deterministically
>>>>> specify which
>>>>> I want to keep on the host and which I want to pass to the guest?
>>>>>
>>>>> Is there a way to use something like BusID:DeviceID instead in
>>>>> order to
>>>>> provide a more deterministic outcome?
>>>> I think George (CCd) had some plans to improve this initial
>>>> implementation in the 4.4 time frame.
>>>>
>>>> Since it looks like the devices which you pass are given direct to
>>>> qemu's -usbdevice option it seems like host:bus.addr should work
>>>> too.
>>>> "Supporting" this option is perhaps just a docs patch away?
>>> Yes, I think "host:bus.addr" should work as well. Let us know if
>>> it
>>> doesn't.
>> If it does then we should add it to our docs as something which we
>> support passing on to qemu.
>
> Gordan, did you try this?
Yes, it works, but only if BusID != 8. See the bug report I posted
yesterday. I will double check tonight whether the BusID=8 gets
clobbered into BusID=0 at xl or qemu-dm level.
Gordan
prev parent reply other threads:[~2013-08-05 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 19:17 usbdevice option and specifying a specific device Gordan Bobic
2013-07-29 20:01 ` Gordan Bobic
2013-07-29 21:18 ` Pasi Kärkkäinen
2013-07-29 21:40 ` Gordan Bobic
2013-07-30 8:23 ` Ian Campbell
2013-07-31 8:25 ` George Dunlap
2013-07-31 10:12 ` Ian Campbell
2013-08-05 11:24 ` George Dunlap
2013-08-05 11:27 ` Gordan Bobic [this message]
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=53656e1e164ffe2568a9ec0116fead16@mail.shatteredsilicon.net \
--to=gordan@bobich.net \
--cc=Ian.Campbell@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.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).