Hi Stefan,
I think you mean you don't specify the "iommu" parameter at all in Xen grub 
entry (so VT-d is not turned on by default) and then you try to create a PV 
guest with "pci=['xx:xx.x']" specified in the PV guest config file and you meet 
with the "co-assignment issue". Correct?
I didn't test the traditional PV-only PCI passthrough.
We only specify a string "pci=['xx:xx.x']" in pv guest config file. How can 
Xend tell whether we're using the traditional PCI passthrough or the VT-d 
passthrough? Judging by the "iommu=pv or no-pv" xen parameter? I'm not sure 
about that for now...
Thanks,
-- Dexuan
________________________________
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
stefan-neuwirth@xxxxxxxxxxx
Sent: 2008年10月16日 15:20
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen 3.3.0 pv pci passthrough co-assigned problem
After upgrading from xen 3.2.x to xen 3.3.0 I get an error message
when using pci passthrough with pv guests (my system is not vt-d
enabled):
xm create -c /etc/xen/domU/myguest
Using config file "/etc/xen/domU/myguest".
Error: pci: 0000:0e:05.0 must be co-assigned to the same guest with 0000:0f:0a.0
Sharing diffrent pci devices behind a pci bridge used to work in older
xen versions for pv guests. It seems the restriction for the vt-d
passthrough is also applied to the pv passthrough - any reason for
this? For me this is a real big regression.
 Stefan

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