| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Problem with pv-ops dom0 and pci-stub to hide devices:
On Tue, Oct 13, 2009 at 7:20 AM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> 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?
xen/master, 2.6.31.1
> 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).
Do you mean 30.1 or 31.1?
>
> Nor is there a pci-front in the 2.6.31.1.
What is the right mechanism to pass PCI devices to a domU when running
the pv-ops dom0 kernel?
>
> Why use pci-stub? It just hides devices, but does not do anything else?
>
I admit some confusion here. What is the difference between these?
- pciback/pcifront
- pci passthorugh
- pci-stub
I'll gladly RTFM if somone could refer me to the appropriate link.
We're running 2.6.31.1 pv-ops dom0, and hvm 2.6.30.1 for the domU.
Thanks
-Bruce
- Hide quoted text -
>>
>> 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
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home