WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: "Xen Users" <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
From: "Andy Burns" <xen.lists@xxxxxxxxxxx>
Date: Tue, 2 Sep 2008 20:48:26 +0100
Cc:
Delivery-date: Tue, 02 Sep 2008 12:49:03 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition:x-google-sender-auth; bh=9rWqCsgXFQDCuyXFWl6sTsu/FZyIuqpBoCn7XV6Q5cI=; b=uTTKoDB5EfmUfaaTebTpeSIf9uMolae1aKACSn3iwCxAZYyd/mNrnHmc2KXQU1JpJy 5U60TxBzvOXaXXBDrSmgbW9e1BmhQ9CpgfRxaPloq4YeUNgrx+JMCtX7D0rbmwBubpgv gyY2jr9wgbk337U2xRdU2YIZpcyngcm8qq/ik=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:x-google-sender-auth; b=vgdeH8AIr9+lyEXY4siHybnHC/oYPGu66AENxsoy1kVb7KyVtBKZO60c2dA9s1+fAK LeKgnLJO2dZFCFpYYShSI6zLsnbI5Rz/UCZ4DslskxLPYtEAQR1B5K3u0vSD26vAsezE ma2w2OkSCcYeSdePBZu0AXDWzG9aHh333o4ds=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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