From: Pavel Mateja <pavel@netsafe.cz>
To: xen-devel@lists.xen.org
Subject: Re: PCI USB Passthrough on Kernel 3.5 and 3.6 not working (HVM or PVM)
Date: Thu, 11 Oct 2012 15:14:22 +0200 [thread overview]
Message-ID: <201210111514.23294.pavel@netsafe.cz> (raw)
In-Reply-To: <1349511545.3350.8.camel@multiplex>
> Hi Xenners,
>
> I have tried to upgrade to kernel 3.5 and experienced the USB/PCI
> passthrough problem. This has not been "fixed" in 3.6 either. I do not
> know if this is qemu, xen or kernel related.
>
> I am using Xen 4.2 final and Xen 4.3-unstable to test.
>
> DomU is Windows 7 64 bit or Linux Fedora 17. In Windows, I get the
> little yellow triangle with Code 10 (I know this means nothing...
> really). In linux, the PCI device is recognised, but a few seconds
> later disabled due to a "fatal error", no more details than that in
> dmesg.
>
> Dom0 retains full control over the USB controller (this is not the case
> when passthrough works, xl switches between Dom0 and DomU depending on
> who claims the device).
>
> In both Windows and Linux (lspci), the device is "seen" but cannot be
> activated.
>
> In Dom0, the device is assigned to the guest (xl pci-list show that it
> is assigned and has a valid guest PCI ID).
>
> Xen logs are normal, devices get assigned as if they were working with a
> kernel 3.3.4 Dom0 - no errors according to xen logs or xl dmesg.
>
> VGA PCI passthrough works 100%.
>
> I tried also with device model qemu-xen, but then passthrough doesn't
> work at all (no VGA either), even with upstream QEMU from git.
>
> Please tell me if I'm missing something obvious or if I can provide more
> information for troubleshooting!
>
> Kind regards,
> Andi
Hi,
did you try the resource_allignment workaround?
What is your HW anyway?
--
Pavel Mateja
next prev parent reply other threads:[~2012-10-11 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 8:19 PCI USB Passthrough on Kernel 3.5 and 3.6 not working (HVM or PVM) Andi Reinbrech
2012-10-11 13:14 ` Pavel Mateja [this message]
2012-10-11 14:06 ` Konrad Rzeszutek Wilk
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=201210111514.23294.pavel@netsafe.cz \
--to=pavel@netsafe.cz \
--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).