This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Richie <listmail@xxxxxxxxxxxx>
Subject: Re: [Xen-users] can not unbind pci device, xen kernel, openSUSE
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Vs4Tem21quRhocsEmSn1KTGeviZ4wAfsuPp9/UX/fNA=; b=MFGuvN6NLtBNZ2Tsgill6xGXOGeKOK80ViGM1yyxQaUNyAvhT93AMRAXUTvU9PrbdF dZGwrS9QOt7NZKNfZitj0InVl6V28lyI9ricFjb0YLBWh/2qy3JgwBMzehS5qx0jWiiQ Rujqdx30xkidJGapf6irqry5QneZd4hZToeRU=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikLdXNkRkBSm30-kLqBJF1=iNAcLykGikfvr48Z@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTikajmnnb+aSp35ABKFiqCkk1QRZRBixGc+nA_pR@xxxxxxxxxxxxxx> <4CCC289F.1070803@xxxxxxxxxxxx> <AANLkTi=7aH=pugQPWkdMAw-XpCCbOjogzV2rRGOXhFX7@xxxxxxxxxxxxxx> <4CCC402F.3000102@xxxxxxxxxxxx> <AANLkTikLdXNkRkBSm30-kLqBJF1=iNAcLykGikfvr48Z@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
... 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