http://bugzilla.novell.com/show_bug.cgi?id=573311 http://bugzilla.novell.com/show_bug.cgi?id=573311#c3 --- Comment #3 from mail ignored <0.bugs.only.0@gmail.com> 2010-01-27 15:07:56 PST --- fyi, (1) Re: [Xen-devel] Re: follow up to a pciback "pv pci-passthrough co-assign" http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00937.html
sure. would it not be reasonable to have a similar config-file option in xen 3.x -- with similar warnings etc -- as is done in 4.x? if all that's required for a workaround is a patch similar to that above ...
thanks
The option was introduced by changeset 20179. It's small. It can be back ported to Xen 3.x if need.
It would be good to backport this.
The point here is, I think, that before the VT-d stuff you could passthrough for example each port from a dual-port NIC to different PV guests, even if it was not the recommended way.
Now at some point it stopped working for many people, and Xen started complaining that the devices need to be passed to the same guest.
I know some people are also using another port from a dual-port NIC in the dom0, and another port passthroughed to a PV guest. And they've been doing this for a long time.
(2) [Xen-devel] PV PCI passthrough - summary/status http://lists.xensource.com/archives/html/xen-devel/2009-10/msg01226.html Bug #1340: The Function Level Reset reset requires that PCI devices behind a bridge be owned by the same guest. Based on the comments, without the FLR capability in 3.2, the PCI devices worked fine. We could provie a 'flr_inhibit' flag which would revert back to 3.2 and not do an FLR? -> "[1340] 3.3.0 PCI devices ... must be co-assigned to the same guest" http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1340 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.