[Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest

["Andy Burns" <xen.lists@xxxxxxxxxxx>]

I have my box back working under xen 3.3.0 (thanks to whoever created
the repo at http://www.gitco.de/repo/xen3.3.0) seems my hypervisor
wasn't built correctly, I can now start my domUs.

I have two DVB-T tuners, previously with xen 3.2.0 I did the following
in dom0 to setup the PCI passthrough to domU

rmmod saa7134
modprobe pciback
SLOT1=0000:08:00.0
SLOT2=0000:08:01.0
echo -n $SLOT1 > /sys/bus/pci/drivers/pciback/new_slot
echo -n $SLOT2 > /sys/bus/pci/drivers/pciback/new_slot
echo -n $SLOT1 > /sys/bus/pci/drivers/pciback/bind
echo -n $SLOT2 > /sys/bus/pci/drivers/pciback/bind
xm create mythbe32.cfg

with the config file
memory = 384
name = "mythbe32"
vif = [ 'mac=00:16:3E:76:E8:92, bridge=eth0' ]
disk = [ 'phy:/dev/vgr1/lvmythbe32,xvda,w', 'phy:/dev/vgr5/lvmythdata,xvdb,w' ]
pci = ['08:00.0', '08:01.0']
bootloader = "/usr/bin/pygrub"
vcpus = 1
on_reboot = 'restart'
on_crash = 'restart'

Now when I do exactly the same under xen 3.3.0 I get this error

Error: pci: 0000:08:03.0 must be co-assigned to the same guest with 0000:08:00.0

As far as I can see, the PCI device 08:03.0 is totally unrelated to
the two PCI cards, it's a firewire controller on the motherboard, here
is the dom0 lspci

08:00.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
        Subsystem: Compro Technology, Inc. Videomate DVB-T200
        Flags: medium devsel, IRQ 16
        Memory at febffc00 (32-bit, non-prefetchable) [disabled] [size=1K]
        Capabilities: [40] Power Management version 1

08:01.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
        Subsystem: Compro Technology, Inc. Videomate DVB-T200
        Flags: medium devsel, IRQ 17
        Memory at febff800 (32-bit, non-prefetchable) [disabled] [size=1K]
        Capabilities: [40] Power Management version 1

08:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev c0) (prog-if 10 [OHCI])
        Subsystem: ASUSTeK Computer Inc. Unknown device 81fe
        Flags: bus master, medium devsel, latency 64, IRQ 19
        Memory at febff000 (32-bit, non-prefetchable) [size=2K]
        I/O ports at ec00 [size=128]
        Capabilities: [50] Power Management version 2

Why is xen insisting the firewire controller is passed through to the domU?

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