RE: [Xen-devel] Strange PCI Passthrough problem

["Cui, Dexuan" <dexuan.cui@xxxxxxxxx>]

Hi Todd,
Can you attach the output log of 'lspci -tv' and 'lspci -xxx -vvv'?

I'm afraid you meet with the co-assignment limit.
If a device(including multi-function device) hasn't a proper standard FLR 
method, we have to use the SecondaryBusReset as a FLR method, so we require the 
co-assignment.
You can refer to http://xenbits.xensource.com/xen-unstable.hg?rev/e61978c24d84 
for details.

Thanks,
-- Dexuan


-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Todd Deshane
Sent: 2008年10月10日 5:23
To: xen-devel mailing list
Subject: [Xen-devel] Strange PCI Passthrough problem

I have successfully passed through a video card, network card,
USB mouse, and USB keyboard to a MS Vista guest. That
works well.

I am trying to add another PCI device, such as a audio card
or PCI USB hub, but I am running into a strange problem.

When I plug the PCI audio (or USB card) to the motherboard.
It makes it so that the PCI video card is no longer an
"assignable device" (xm pci-list-assignable-devices doesn't
see it anymore, but previously I had passed it through
successfully).

Things I have thought to check.

pciback (in proc) still owns the device.

dmesg still shows the proper output, i.e. seizing device,
interupt --> IRQ, device disabled, just like they should be.

The problem at first glance, seems to be the fact that
there are two devices on 03:XX.X

The video card shows up as 03:02.0 and the next card
plugged into the motherboard shows up as 03:00.0.

The other devices (besides the video card) that I have
successfully passed all had 00:XX.X, so when adding
the second PCI card to the motherboard, that is the
first time there are two 03:XX.X devices on the bus.

I am using a relatively recent pull of xen-unstable with
a 2.6.18.8-xen kernel from xenbits as well.

Suggestions on how to debug further?

Thanks in advance,
Todd


--
Todd Deshane
http://todddeshane.net
http://runningxen.com

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel