From: Gordan Bobic <gordan@bobich.net>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Bug in usbdevices option handling when BusID=8
Date: Sun, 04 Aug 2013 12:36:36 +0100 [thread overview]
Message-ID: <51FE3CC4.7070709@bobich.net> (raw)
In-Reply-To: <51FE362A.3000300@bobich.net>
On 08/04/2013 12:08 PM, Gordan Bobic wrote:
> Configuration: Xen 4.3.0, xl
>
> I have been trying to pass USB mouse and keyboard through do a domU
> using usbdevices = [] option. The success/failure seems to be related to
> the bus.device option.
>
> Specifically, in quemu log:
>
> husb: open device 0.2
> /dev/bus/usb/000/002: No such file or directory
> Warning: could not add USB device host:008.002
> husb: open device 6.2
> husb: config #1 need -1
> husb: 2 interfaces claimed for configuration 1
> husb: grabbed usb device 6.2
>
> In domU config:
> usbdevice = [ 'host:008.002', 'host:006.002' ]
>
> At a glance, this looks like something buggy happens when BusID=8. It
> sees that the device is host:008.002, but then goes and tries to open
> /dev/bus/usb/000/002 instead of /dev/bus/usb/008/002.
>
> If I change the port where the device is connected and it gets a
> different ID, and I change the config to:
>
> usbdevice = [ 'host:003.002', 'host:006.002' ]
>
> the log then says:
>
> husb: open device 3.2
> husb: config #1 need -1
> husb: 1 interfaces claimed for configuration 1
> husb: grabbed usb device 3.2
> husb: open device 6.2
> husb: config #1 need -1
> husb: 2 interfaces claimed for configuration 1
> husb: grabbed usb device 6.2
>
> and both devices are availble in domU.
>
> Bug?
There also appears to be a further bug in handling of usb devices. When
I change the device to not be on bus 8, I get this for some devices:
husb: open device 3.2
husb: config #1 need -1
husb: 2 interfaces claimed for configuration 1
husb: grabbed usb device 3.2
husb: open device 4.2
husb: config #1 need -1
husb: 2 interfaces claimed for configuration 1
husb: grabbed usb device 4.2
usb_linux_update_endp_table: Invalid or incomplete multibyte or wide
character
The device seems to get added (stops working in dom0), but then doesn't
appear to work in domU, presumably due to the error line above.
Gordan
next prev parent reply other threads:[~2013-08-04 11:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 11:08 Bug in usbdevices option handling when BusID=8 Gordan Bobic
2013-08-04 11:36 ` Gordan Bobic [this message]
2013-08-05 7:29 ` Ian Campbell
2013-08-05 13:22 ` George Dunlap
2013-08-05 19:20 ` Gordan Bobic
2013-08-06 9:24 ` George Dunlap
2013-08-06 9:25 ` Gordan Bobic
2013-08-06 9:28 ` George Dunlap
2013-08-06 9:30 ` Processed: " xen
2013-12-12 17:01 ` Anthony PERARD
2013-12-12 17:29 ` George Dunlap
2013-12-12 19:32 ` Anthony PERARD
2013-12-13 11:04 ` George Dunlap
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=51FE3CC4.7070709@bobich.net \
--to=gordan@bobich.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.