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

Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE



On 10/30/2010 11:56 AM, Richie wrote:
On 10/30/2010 11:39 AM, István HERCZEG wrote:
Hi,

thank you for quick answer. You was right I missed the format. But I still have a problem. Continue the PCI unbind procedure the wiki says[1]:

echo -n "0000:00:1a.0" /sys/bus/pci/drivers/pciback/new_slot

and ..
echo -n "0000:00:1a.0" /sys/bus/pci/drivers/pciback/bind_cat

In my openSUSE 11.2 there are no /sys/bus/pci/drivers/pciback directory. OK. I have /sys/bus/pci/drivers/pci-stub maybe this would be nice[2]:

continuing the procedure:

echo -n "0000:00:1a.0" /sys/bus/pci/drivers/pci-stub/new_slot
-bash: new_slot: No such file or directory
echo -n "0000:00:1a.0" /sys/bus/pci/drivers/pci-stub/bindcat
-bash: bindcat: No such file or directory

I get these messages ...

Regards,
Istvan



This is from some notes I have, but
first find your device in lspci -n output

Say I had a device as follows:
00:01.0 0604: 8086:29a1 (rev 02)

I'd try:
echo "8086 29a1" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:01.0" > /sys/bus/pci/devices/0000:00:01.0/driver/unbind
echo "0000:00:01.0" > /sys/bus/pci/drivers/pci-stub/bind


Additionally, I have some notes that pci-stub works only with hvm and not a xenified kernel and that pciback works with anything [i hope this is accurate, someone from the list can confirm]. You may want to look at either getting pciback built into your dom0 or make sure it is added to /etc/modules so that it gets loaded [if you already have it compiled as a module].

_______________________________________________
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®.