|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-users
Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE
 
... 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, reagrds Istvan
 
 
 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) 
 doing:  dmesg | grep -i seiz [ 1613.652339] pciback 0000:00:1a.0: seizing device [ 1700.984342] pciback 0000:00:1d.0: seizing device
  seems ok.
  but 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: 
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 
 
 
  
  
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread> |  
- [Xen-users] can not unbind pci device, xen kernel, openSUSE, István HERCZEG
- Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE, Richie
- Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE, István HERCZEG
- Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE, Richie
 - Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE, Richie
 
- Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE, István HERCZEG
 - Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE,
István HERCZEG <=
 
  
  
 
 
 
 |  
  
 | 
    | 
  
  
    |   | 
    |