[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Error: pci: 0000:02:06.0 must be co-assigned to the same guest with 0000:02:05.0


  • To: nig@xxxxxxxx, "Velten Spägele" <xen@xxxxxxxxx>
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Sun, 4 Jan 2009 16:45:03 -0500
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 04 Jan 2009 13:45:53 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=icJ1HZmFbrqI8vpikqZQjA5IBn0M8CJd09fgb+zT48bydMVEC9ngzCtFK0oAtrm9rS JA1E5pGVr2Co4Dm/2+HpMAsBzipH4URRvYeDEbIKDJCQwcK3fCez71IU/sgxfJw090OY KfaFVzZWL8w7y1/llQH3zGW96OIY71rGpKhpA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Sun, Jan 4, 2009 at 3:01 PM, Frank Mueller <frank.mueller@xxxxxxxx> wrote:
> Hi Velten,
>
> you could try to put the isdn card in a different pci-slot.
>
> You get around the "co-assigned" message with assigning the pci devices xen
> wants into one domU, however this might not be always possible ( eg.
> motherboard devices)
>

If you can't use different PCI slots for whatever reason, you should be
able to disable Function Level Reset in the xend scripts.

Here is a patch:
http://xen.markmail.org/search/?q=disable+flr#query:disable
flr+page:1+mid:7dbm675e4x4dawec+state:results

It may be able to be applied to the pci.py file on your system without
any recompiling etc., since it is just a python code change.

Hope that helps.


> However, i am testing xen3.3.1 on opensuse11 at the moment and it looks
> like the pv pci-passtrough is seriously broken.
>

You should report bugs on xen bugzilla and to xen-devel if you can.

> pv pci-passtrough worked wonderful in opensuse10.3 which xen 3.1. Trying the
> same ( with same domU config file) in xen3.3.1 just gives you the
> "co-assigned" and even worse, if you assign all pci devices xen wants in the
> domu, the domU starts, but it looks like the  domU does not get the
> interrupt from the device.
>
> I believe the VT-d passtrough code messed up the pv passtrough, hope this
> gets fixed soon.
>
> Regards
>
> Frank
>
>
>
>> next step... :)
>>
>> i got pcihiding on, with modprobe an manual hiding, but now
>>
>> # xm create auto/fli4l
>> Using config file "/etc/xen/auto/fli4l".
>> Error: pci: 0000:02:06.0 must be co-assigned to the same guest with
>> 0000:02:05.0
>>
>>
>> 02:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>> RTL-8139/8139C/8139C+ (rev 10)
>> 02:06.0 Network controller: Cologne Chip Designs GmbH ISDN network
>> controller [HFC-PCI] (rev 02)
>>
>>
>> i need the Ethernet controller in Fli4l-domain and the ISDN Controller
>> in an asterisk domain....
>>
>>
>> how can i fix this ?
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.