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

Re: [Xen-users] domU does not see the pci nic - pci passthrough



Marco Strullato wrote:
Hi Mark,
lspci does
[root@localhost tmp]# lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.

Dom0: Centos 5, 32 bit, kernel 2.6.18-8.el5xen. The /boot/config file contains:
CONFIG_X86_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030203
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PRIVCMD=y
CONFIG_XEN_XENBUS_DEV=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=m
CONFIG_XEN_BLKDEV_TAP=m
CONFIG_XEN_NETDEV_BACKEND=m
CONFIG_XEN_NETDEV_LOOPBACK=m
CONFIG_XEN_PCIDEV_BACKEND=m
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
CONFIG_XEN_PCIDEV_BACKEND_PASS=y
CONFIG_XEN_PCIDEV_BACKEND_SLOT=y
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_FRAMEBUFFER=y
CONFIG_XEN_KEYBOARD=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_SYSFS=y
CONFIG_XEN_COMPAT_030002_AND_LATER=y
CONFIG_XEN_COMPAT_030002=y
CONFIG_XEN_UTIL=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_DEVMEM=y
CONFIG_XEN_SKBUFF=y
CONFIG_XEN_REBOOT=y
CONFIG_XEN_SMPBOOT=y


DomU: Centos 5. 32 bit, kernel 2.6.9-55.ELxenU

Each server has centos kernel.

I noticed that domU does not have the e100 module... the domU kernel is very poor, it does not have many modules..

I always have e100 module in my RHEL5 xen kernel.

[root@dhcp6-102 ~]# find /lib/modules/2.6.18-53.el5xen/| grep e100
/lib/modules/2.6.18-53.el5xen/kernel/drivers/net/e1000
/lib/modules/2.6.18-53.el5xen/kernel/drivers/net/e1000/e1000.ko
/lib/modules/2.6.18-53.el5xen/kernel/drivers/net/e1000e
/lib/modules/2.6.18-53.el5xen/kernel/drivers/net/e1000e/e1000e.ko
/lib/modules/2.6.18-53.el5xen/kernel/drivers/net/e100.ko

[root@dhcp6-102 ~]# find /lib/modules/2.6.18-8.el5xen/| grep e100
/lib/modules/2.6.18-8.el5xen/kernel/drivers/net/e1000
/lib/modules/2.6.18-8.el5xen/kernel/drivers/net/e1000/e1000.ko
/lib/modules/2.6.18-8.el5xen/kernel/drivers/net/e100.ko

Your problem is something else. On successful pci passthrough, your domU should list your pci card in the lspci output regardless of the availability of e100 module in the xen kernel.

--Sadique


Regards,

Marco



2007/12/4, Mark Williamson <mark.williamson@xxxxxxxxxxxx <mailto:mark.williamson@xxxxxxxxxxxx>>:

    Hi Ma

    rco,

    Everything you've shown looks OK as far as it goes...  Weird that
    the guest
    isn't working for you.

    What does lspci in the guest give?

    What distro are you runing in the dom0 and domU?  Where have your
    Xen-enabled
    kernels come from?  Self compiled, or distro packages?  Does your
    domU
    definitely have an installed driver for the device?

    Cheers,
    Mark

    On Monday 03 December 2007, Marco Strullato wrote:
    > Hi all!
    > I want to assign a physical network card  (e100) to a domU:
    > I think  Dom0 is ok but domU does not recognize the pci nic.
    >
    > into DomU I don't know wath should I see: I have nothing in
    dmesg nor in
    > messages...
    >
    > Into Dom0 I have
    >
    > this modules.conf:
    > options pciback hide=(0000:03: 08.0)
    > install e100 /sbin/modprobe pciback; /sbin/modprobe
    --ignore-install e100
    >
    > This is dmesg:
    > pciback 0000:03:08.0: seizing device
    > ACPI: PCI Interrupt 0000:03:08.0[A] -> GSI 20 (level, low) -> IRQ 21
    > ACPI: PCI interrupt for device 0000:03:08.0 disabled
    > tg3.c:v3.65-rh (November 20, 2006)
    > ACPI: PCI Interrupt 0000:03: 09.0[A] -> GSI 21 (level, low) ->
    IRQ 22
    > eth0: Tigon3 [partno(BCM95703A30U_HYB) rev 1100 PHY(5703)]
    > (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:10:18:24:d2:a6
    > eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0]
    WireSpeed[1]
    > TSOcap[1]
    > eth0: dma_rwctrl[763f0000] dma_mask[64-bit]
    > e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
    > e100: Copyright(c) 1999-2005 Intel Corporation
    >
    > this is the lspci line:
    > 03:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100
    Ethernet
    > Controller (rev 02)
    >
    > this is the content of the dir /lrwxrwxrwx 1 root root    0
    Dec  3 16:07
    > 0000:03:08.0 -> ../../../../devices/pci0000:00/0000:00:
    1e.0/0000:03:08.0
    > --w------- 1 root root 4096 Dec  3 16:07 bind
    > lrwxrwxrwx 1 root root    0 Dec  3 16:07 module ->
    > ../../../../module/pciback
    > --w------- 1 root root 4096 Dec  3 16:07 new_id
    > --w------- 1 root root 4096 Dec  3 16:07 new_slot
    > -rw------- 1 root root 4096 Dec  3 16:07 permissive
    > -rw------- 1 root root 4096 Dec  3 16:07 quirks
    > --w------- 1 root root 4096 Dec  3 16:07 remove_slot
    > -r-------- 1 root root 4096 Dec  3 16:07 slots
    > --w------- 1 root root 4096 Dec  3 16:07
    unbindsys/bus/pci/drivers/pciback/
    >
    > This is the domU confguration file:
    > name = "VMTEST"
    > memory = "256"
    > disk = [ 'phy:/dev/VolGroup00/VMTEST,xvda,w', ]
    > vif = [ 'mac=00:16:3e:21:33:b2, bridge=xenbr0', ]
    > uuid = "a1532b7c-5aa4-3eb5-a150-930402abd72f"
    > bootloader="/usr/bin/pygrub"
    > vcpus=2
    > on_reboot   = 'restart'
    > on_crash    = 'restart'
    > pci = ['03.08.0']



    --
    Dave: Just a question. What use is a unicyle with no seat?  And no
    pedals!
    Mark: To answer a question with a question: What use is a skateboard?
    Dave: Skateboards have wheels.
    Mark: My wheel has a wheel!


------------------------------------------------------------------------

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


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


 


Rackspace

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