|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] Problems with pci passthrough with Xen 3.4.2
Thank's Stefan but I've not found a diff path to apply the source code
of Xen... I'll do a deep search, thank's again.
Pasi, the two lines in lspci are the two gigabit ethernet interfaces
built in the mainboard, when I hide them the dom0 gets no ethernet
link. (eth0 not found)
Maybe I need to buy an simple pci-ethernet-gigabit and asign it to the domU?
J.
2009/12/9 Pasi Kärkkäinen <pasik@xxxxxx>:
> On Wed, Dec 09, 2009 at 06:13:14PM +0100, francisco javier funes nieto wrote:
>> Hi all!.
>>
>> First of all sorry about my English it's not very fluid.
>>
>> I have a small server based upon Supermicro X7DBN (Chipset Intel®
>> 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM
>> RAM.
>>
>> The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny
>> in domU (2.6.26-2-xen-amd64).
>>
>
> You might want to try the latest 'official' Xen 3.4.x dom0 kernel:
> http://xenbits.xen.org/linux-2.6.18-xen.hg
>
> I know someone who got pci-passthrough working with Xen 3.4.2 and
> 2.6.18-xen dom0 kernel.
>
>
>> Xen is 3.4.2 compiled from sources.
>>
>> The problem comes when I need to passthrough the second gigabit
>> ethernet interface to a domU. I've got an "pci: improper device
>> assignment specified:" error.
>>
>> Here is the menu.lst:
>>
>> module /boot/vmlinuz-2.6.26-2-xen-amd64 root=/dev/sda1 ro
>> console=tty0 pci=nomsi pciback.hide=(04:00.1)
>>
>>
>> Here is the lspci output:
>>
>> main:~# lspci |grep Ethernet
>>
>> 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit
>> Ethernet Controller (Copper) (rev 01)
>> 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit
>> Ethernet Controller (Copper) (rev 01)
>>
>
>
> So this is a so called multi-function device?
> I think you should hide both the functions from dom0!
>
>
>> Here's the xm info:
>>
>> main:~# xm info
>> host : main.chauchinasincables.es
>> release : 2.6.26-2-xen-amd64
>> version : #1 SMP Thu Nov 5 04:27:12 UTC 2009
>> machine : x86_64
>> nr_cpus : 4
>> nr_nodes : 1
>> cores_per_socket : 4
>> threads_per_core : 1
>> cpu_mhz : 1866
>> hw_caps :
>> bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001:00000000
>> virt_caps : hvm
>> total_memory : 4094
>> free_memory : 128
>> node_to_cpu : node0:0-3
>> node_to_memory : node0:128
>> xen_major : 3
>> xen_minor : 4
>> xen_extra : .2
>> 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 : unavailable
>> cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1)
>> cc_compile_by : root
>> cc_compile_domain : chauchinasincables.es
>> cc_compile_date : Tue Dec 8 20:57:01 CET 2009
>> xend_config_format : 4
>>
>> Here's the domU config file with pci device:
>>
>> pci = ['04:00.1']
>>
>>
>>
>> And here's the error when I try to create the VM:
>>
>> main:~# xm create /etc/xen/proxy.chauchinasincables.es.cfg
>> Using config file "/etc/xen/proxy.chauchinasincables.es.cfg".
>> Error: pci: improper device assignment specified: pci: 0000:04:00.0
>> must be co-assigned to the same guest with 0000:04:00.1, but it is not
>> owned by pciback.
>>
>
> There it is.. you have to passthrough _both_ of the functions at the
> same time.
>
>>
>> With Xen from Debian Repository (3.2-1) it works very well!
>> But not the same result with compiled from source Xen (3.4.2).
>>
>> Can anyone show me how to configure this?
>>
>> I've tried xm pci-attach but pci-list-assignable-devices shows nothing
>> and pciback module show that the device is seized from dom0.
>>
>> I'm really lost...
>>
>> thanks in advance.
>>
>
> Try passing both of the PCI ids, and see if it works then.
>
> -- Pasi
>
>
--
_____________________________________________
Francisco Javier Funes Nieto [esencia@xxxxxxxxx]
CANONIGOS
Servicios Informáticos para PYMES.
Cl. Cruz 2, 1º Oficina 7
Tlf: 958.536759 / 661134556
Fax: 958.521354
GRANADA - 18002
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|