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

RE: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified


  • To: "Han, Weidong" <weidong.han@xxxxxxxxx>
  • From: "Cinco, Dante" <Dante.Cinco@xxxxxxx>
  • Date: Tue, 13 Oct 2009 16:56:18 -0600
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 13 Oct 2009 15:56:53 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcpLyDKxWB1WEei4SHScRAl7Gpk4LwABIf2AABabBtAADCdgwA==
  • Thread-topic: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified

Weidong,
 
You were right. I was not using the latest Xen. The changeset in my previous email show 20296 and the one I'm using now is 20303. I'm able to hide my device now using pci-stub, it shows up in "xm pci-list-assignable-devices" and I'm able to assign/pass it through to the domU. It shows up in "lspci" from domU.
 
Thanks.
 
Dante


From: Cinco, Dante
Sent: Tuesday, October 13, 2009 10:16 AM
To: 'Han, Weidong'
Cc: 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: RE: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified

Weidong,
 
Is the pci-stub hiding different for PCIe devices? How do I tell which latest version of xend I should be using? Does "xm info" help?
 
Dante
 
xm info
host                   : kaan-12
release                : 2.6.31.1
version                : #13 SMP Mon Oct 12 09:21:06 PDT 2009
machine                : x86_64
nr_cpus                : 16
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 2533
hw_caps                : bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 12134
free_memory            : 131
node_to_cpu            : node0:0-15
node_to_memory         : node0:131
xen_major              : 3
xen_minor              : 5
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Thu Oct 08 09:24:32 2009 +0100 20296:1d7221667204
cc_compiler            : gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
cc_compile_date        : Fri Oct  9 16:02:02 PDT 2009
xend_config_format     : 4


From: Han, Weidong [mailto:weidong.han@xxxxxxxxx]
Sent: Monday, October 12, 2009 11:22 PM
To: 'Bruce Edge'
Cc: Cinco, Dante; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: RE: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified

There are PCIe devices. Per following message, I'm sure you didn't use the latest xend code (did you make tools and install it?).
 
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.
 
 
pls make -C tools, and make install it. Because it doesn't support FLR, I guess you still need to hide all functions (07:00.0,07:00.1, 07:00.2, 07:00.3) although you just assign one.
 
Regards,
Weidong


From: Bruce Edge [mailto:bruce.edge@xxxxxxxxx]
Sent: 2009年10月13日 13:44
To: Han, Weidong
Cc: Cinco, Dante; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified

Here's the output from lspci -vvv (I work with Dante)

-Bruce


2009/10/12 Han, Weidong <weidong.han@xxxxxxxxx>
Dante,
 
I guess 07:00.0 and 07:00.1 are two PCI (non-PCIe) devices in your system. PCI devices under the same bridge must be assigned to one guest. Pls hide both of them by pci-stub, then you can assign both of them to a guest, or just assign one. Pls attach the output of 'lspci -vvv'.
 
Regards,
Weidong


From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Cinco, Dante
Sent: 2009年10月13日 8:48
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified

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

 


Rackspace

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