Andy Burns
2008-Sep-02 19:48 UTC
[Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
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@lists.xensource.com
http://lists.xensource.com/xen-users
Joseph L. Casale
2008-Sep-02 19:59 UTC
RE: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
>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.Thanks for that pointer! I also have an issue with a poorly built 3.3.0! Why aren''t you simply generating a new initrd with a --preload=pciback? I wonder if that''s not part of the issue (though that''s a weird error msg). I expected to see that for some devices like dual/quad port nics where two ports share the same pci location. Keep us posted as to your success with this version of Xen... jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andy Burns
2008-Sep-02 20:22 UTC
Re: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
2008/9/2 Joseph L. Casale <JCasale@activenetwerx.com>:> Thanks for that pointer! I also have an issue with a poorly built 3.3.0!Yes I was pleased to find it.> Why aren''t you simply generating a new initrd with a --preload=pciback?Laziness I guess ;-) I couldn''t use pciback=blah as it''s build as a module in centOS5.2 kernel, so the /sys method was a a quick way out, I was going to blacklist the saa* drivers in modprobe.conf but never got around to it.> I wonder if that''s not part of the issue (though that''s a weird error msg).It used to work fine on xen 3.2.0> I expected to see that for some devices like dual/quad port nics where two > ports share the same pci location.Yes, I don''t expect to be able to split different functions of a single PCIID between domains!> Keep us posted as to your success with this version of Xen...So far so good with non-PCI passthrough domains, I''ll have a play with pv-grub on a windows domU in a while. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andy Burns
2008-Sep-03 09:13 UTC
Re: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
2008/9/2 Joseph L. Casale <JCasale@activenetwerx.com>:> that''s a weird error msg.http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1340 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andy Burns
2008-Sep-03 09:49 UTC
Re: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
2008/9/2 Andy Burns <xen.lists@burns.me.uk>:> I''ll have a play with > pv-grub on a windows domU in a while.I think I meant pv-grub on a linux domU and ioemu-remote for a windows domU, sleep is good! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bryan York
2008-Sep-03 17:39 UTC
Re: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
Hello, I''m also having the same problem. You may be better off mailing the xen-devel list. I already did, and they asked me to enable serial output, but I think my serial output on my board may be damaged. Also, can you confirm that this is working on Xen 3.2.x? -Bryan On Wed, Sep 3, 2008 at 2:49 AM, Andy Burns <xen.lists@burns.me.uk> wrote:> 2008/9/2 Andy Burns <xen.lists@burns.me.uk>: > > > I''ll have a play with > > pv-grub on a windows domU in a while. > > I think I meant pv-grub on a linux domU and ioemu-remote for a windows > domU, sleep is good! > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andy Burns
2008-Sep-03 17:52 UTC
Re: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
2008/9/3 Bryan York <bryan.york@gmail.com>:> I''m also having the same problem. You may be better off mailing the > xen-devel list.I was hoping developers would pick it up from the bugzilla entry I linked earlier ...> I already did, and they asked me to enable serial output, > but I think my serial output on my board may be damaged. > > Also, can you confirm that this is working on Xen 3.2.x?Definitely worked with 3.2.0, I bypassed 3.2.1 and went straight to 3.3.0 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andy Burns
2008-Sep-03 18:00 UTC
Re: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
2008/9/3 Bryan York <bryan.york@gmail.com>:> I''m also having the same problem.Do you mean your posting from 9th August 2008 01:35? If so, it seems a different issue to me, you are using vt-d, my board doesn''t support that (more''s the pity as it has X38 which I believe is vt-d capable subject to BIOS support), you get a different error message too. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users