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

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

  • To: Richie <listmail@xxxxxxxxxxxx>
  • From: István HERCZEG <advoper@xxxxxxxxx>
  • Date: Sat, 30 Oct 2010 18:35:35 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 30 Oct 2010 09:36:56 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LI5OyMYDZ4Dh/iy78jJ8I+jQKDXZhnh/mWko8+iqn6Yw1cd92LxZzI8xawvr59+t28 f1dm4/lBYvh5RoPL/ytkm/J7PLq3U6+WXlMyX6j7ZRtkx67KnKNwZqFMNGWEqLXrfpEa SYJ9iVnz2InF9KEqNahy035EqwQTqFQqNm4/M=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

... and finally I correct my last mistake. When I start my xen study on my machine I set up Intel VT-d support in my BIOS. Using openSUSE 11.3 and then openSUSE 11.2 I found some instability with this BIOS option. Later I turn off this option and system becomes more stable.
Now I read carefully some instructions from turning on Intel VT-d and I did it (because xm create comply with me and VT-d).
After cold boot the system works properly and xm create windows-xp2 has no error message. Which is more important I can access my USB directly in Windows XP guest. USB works fine I can use my MF printer/scanner.

thank you for the ideas,

2010. október 30. 18:05 István HERCZEG írta, <advoper@xxxxxxxxx>:
I found the reason way I can't find the ../pciback directory. The pciback module makes available ../pciback.
After I did
modprobe pciback
then I can access /sys/bus/pci/drivers/pciback and wirte the new_slot and bind (instead of bindcat)

 dmesg | grep -i seiz
[ 1613.652339] pciback 0000:00:1a.0: seizing device
[ 1700.984342] pciback 0000:00:1d.0: seizing device

seems ok.

xm create windowsxp-2 pci=00:1a.0 pci=00:1d.0
Using config file "./windowsxp-2".
Error: failed to assign device: maybe the platform doesn't support VT-d, or VT-d isn't enabled properly?

:( failure again...

2010. október 30. 17:56 Richie írta, <listmail@xxxxxxxxxxxx>:

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

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


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

Xen-users mailing list



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