WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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:05:27 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 30 Oct 2010 09:07:38 -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=50ibE2rKkfimMyEgdhc+AaUEBn65wmZ8ICfqzO1rsC8=; b=I3H/bCMEzYTrEumBkDXfWI9F/42IZTHKw1e9zW3Jy8HLJy77tRiHNV0vocJv2xLF7+ x0dy+LWQ/1t43lkDUrGa8S+uTG7TYqN7DFQFjooZ9VwTTLC7cNshOc+YgNIjkadHD+kb ZL1sHy0OGsbmL4i0qtspdSesckv0o8c5Q2Ws0=
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=kmXQUmDNpREaLYOED3xRaM6lmVL/hWBD5cCMGBpnsIrYhvT0sBAkXZbIixzruX/HkI NIL9XYuNGwSfNgBauYstnYNH9d6ZVFomVCr9fB1xcpnRHRZTktm7+/dVH2HQJjX/Yyyn 61ZA8uu1bwpFFvqexBXkFm0Y7ToW1aiWAvNas=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CCC402F.3000102@xxxxxxxxxxxx>
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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