From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Pavel Mateja <pavel@netsafe.cz>
Cc: 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 10:06:42 -0400 [thread overview]
Message-ID: <20121011140640.GB1883@localhost.localdomain> (raw)
In-Reply-To: <201210111514.23294.pavel@netsafe.cz>
On Thu, Oct 11, 2012 at 03:14:22PM +0200, Pavel Mateja wrote:
> > 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.
Does your lspci (in dom0) for the device you are passing in, show
'virtual' for the BARs? If so, then it is a kernel issue.
I did another patch for this and it ought to be on the v3.6.x and
v3.5.x train:
commit c341ca45ce56143804ef5a8f4db753e554e640b4
Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date: Tue Sep 25 16:48:24 2012 -0400
xen/pciback: Restore the PCI config space after an FLR.
> >
> > 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
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
prev parent reply other threads:[~2012-10-11 14:06 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
2012-10-11 14:06 ` Konrad Rzeszutek Wilk [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=20121011140640.GB1883@localhost.localdomain \
--to=konrad@kernel.org \
--cc=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).