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

Re: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices: i

To: "Cinco, Dante" <Dante.Cinco@xxxxxxx>
Subject: Re: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 13 Oct 2009 10:20:38 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 13 Oct 2009 07:28:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <2B044E14371DA244B71F8BF2514563F503ECD879@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <2B044E14371DA244B71F8BF2514563F503ECD879@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Mon, Oct 12, 2009 at 06:48:11PM -0600, Cinco, Dante wrote:
> I followed the procedure for "binding devices to pci-stub" but when I ran "xm 
> pci-list-assignable-devices," no device showed up. I can see the device 
> though in /sys/bus/pci/drivers/pci-stub/ and "lspci -v -s 0:07:0.1" reports 
> the driver in use as pci-stub. When I tried to bringup the domU (Linux 
> 2.6.30.1), I get an error message:

What is the Dom0 you are using? There is no support yet in 2.6.30.1 for the 
pciback (I am working on this
right now, testing it to be exact).

Nor is there a pci-front in the 2.6.31.1.

Why use pci-stub? It just hides devices, but does not do anything else?

> 
> Error: pci: improper device assignment specified: pci: 0000:07:00.0 must be 
> co-assigned to the same guest with 0000:07:00.0, but it is not owned by 
> pciback.
> 
> I'm only bringing up one domU so I don't quite understand the error message.
> 
> Here's a breakdown of my steps:
> 
> ls -ltr /sys/bus/pci/drivers/pci-stub/
> total 0
> --w------- 1 root root 4096 Oct  9 05:29 unbind
> --w------- 1 root root 4096 Oct  9 05:29 uevent
> --w------- 1 root root 4096 Oct  9 05:29 remove_id
> --w------- 1 root root 4096 Oct  9 05:29 new_id
> --w------- 1 root root 4096 Oct  9 05:29 bind
> 
> lspci -n|grep 8032
> 07:00.0 0c04: 11f8:8032 (rev 05)
> 
> echo "11f8 8032" > /sys/bus/pci/drivers/pci-stub/new_id
> echo "0000:07:00.0" > /sys/bus/pci/devices/0000:07:00.0/driver/unbind
> echo "0000:07:00.0" > /sys/bus/pci/drivers/pci-stub/bind
> 
> lspci -v -s 0:07:0.0 | grep driver
>         Kernel driver in use: pci-stub
> 
> ls -ltr /sys/bus/pci/drivers/pci-stub/
> total 0
> --w------- 1 root root 4096 Oct  9 05:29 uevent
> --w------- 1 root root 4096 Oct  9 05:29 remove_id
> --w------- 1 root root 4096 Oct  9 05:30 unbind
> --w------- 1 root root 4096 Oct  9 05:30 new_id
> --w------- 1 root root 4096 Oct  9 05:30 bind
> lrwxrwxrwx 1 root root    0 Oct  9 05:30 0000:07:00.0 -> 
> ../../../../devices/pci0000:00/0000:00:09.0/0000:07:00.0
> 
> xm pci-list-assignable-devices
> (Nothing)
> 
> xm create -c /root/cfg
> (vcpus=1)
> (device_model = 'qemu-dm')
> (pci=['07:00.0'])
> Error: pci: improper device assignment specified: pci: 0000:07:00.0 must be 
> co-assigned to the same guest with 0000:07:00.0, but it is not owned by 
> pciback.
> 
> (XEN) Latest ChangeSet: Thu Oct 08 09:24:32 2009 +0100 20296:1d7221667204
> 
> dom0 kernel: 2.6.31.1
> 
> Thanks in advance.
> 
> Dante
> 

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel