From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: merc1984@f-m.fm
Cc: Xen-devel@lists.xen.org
Subject: Re: Bug: USB Bridge Will Not PassThru
Date: Wed, 18 Jun 2014 09:48:57 +0300 [thread overview]
Message-ID: <20140618064857.GY18930@reaktio.net> (raw)
In-Reply-To: <1403071231.18741.130039173.1102B089@webmail.messagingengine.com>
On Tue, Jun 17, 2014 at 11:00:31PM -0700, merc1984@f-m.fm wrote:
>
> I have a device which is a programmable bridge by Cirrus Semiconductor.
> It converts parallel TTL to USB2. I've built udev rules to upload its
> firmware when detected (by VID/PID), and to set the permissions and a
> systemd alias of its new identity after the firmware is loaded.
>
> With Xen 4.3 its Cirrus (unprogrammed) identity would not show up when
> passed thru to an HVM, but after it got its firmware its new identity
> (Anchor) would pass thru, and worked fine. With Xen 4.4 its
> unprogrammed and programmed identities no longer pass through. The
> error in dmesg is not helpful. I'll follow up with that tomorrow.
>
> I know that this is a special case, but there are alot of these
> programmable bridges out there for various functions. And actually,
> with Xen 4.4 I am not able to pass through -any- of my USB devices
> anymore. The mouse, keyboard, Canon scanner, sd card reader, all fail
> to show in the HVM domU. PCI forwarding dom0's USB hub is not an option
> as there is only one hub for the whole machine that handles all 14
> ports.
>
Are you using qemu-traditional or qemu-upstream for this HVM guest?
Note that qemu-traditional only supports USB 1.1 emulated passthru,
while qemu-upstream also supports USB2 and USB3.
-- Pasi
next prev parent reply other threads:[~2014-06-18 6:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 6:00 Bug: USB Bridge Will Not PassThru merc1984
2014-06-18 6:48 ` Pasi Kärkkäinen [this message]
2014-06-18 13:45 ` merc1984
2014-06-18 14:10 ` Pasi Kärkkäinen
2014-06-18 15:28 ` merc1984
2014-06-18 15:47 ` Pasi Kärkkäinen
2014-06-18 16:26 ` merc1984
2014-06-18 17:22 ` Pasi Kärkkäinen
2014-06-18 17:55 ` Pasi Kärkkäinen
2014-06-18 18:13 ` merc1984
2014-06-18 19:02 ` merc1984
2014-06-18 20:30 ` merc1984
2014-06-18 11:34 ` George Dunlap
2014-06-18 15:17 ` merc1984
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=20140618064857.GY18930@reaktio.net \
--to=pasik@iki.fi \
--cc=Xen-devel@lists.xen.org \
--cc=merc1984@f-m.fm \
/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.