[dpdk-dev] pci_unbind.py failure

Jose Gavine Cueto pepedocs at gmail.com
Wed Nov 13 12:27:01 CET 2013


Hi,

How are you using it? I've successfully used it with vbox.

Cheers
On Nov 13, 2013 7:17 PM, "Jyotiswarup Raiturkar" <jyotisr5 at googlemail.com>
wrote:

> hi
>
> I got my application running inside a vm (vmplayer) where the VM emulates a
> e1000 NIC (82545EM). But rte_eth_dev_count() seems to return 0.. From the
> website looks like it's a supported NIC . My lspci and pci_ubind status is
> below. Any pointers?
>
> # ./tools/pci_unbind.py --status
>
> Network devices using IGB_UIO driver
> ====================================
> 0000:02:06.0 '82545EM Gigabit Ethernet Controller (Copper)' drv=igb_uio
> unused=e1000
>
> Network devices using kernel driver
> ===================================
> 0000:02:01.0 '79c970 [PCnet32 LANCE]' if=eth1 drv=pcnet32 unused= *Active*
>
> Other network devices
> =====================
> <none>
>
>
> # lspci -vt
> -[0000:00]-+-00.0  Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host
> bridge
>            +-01.0-[01]--
>            +-07.0  Intel Corporation 82371AB/EB/MB PIIX4 ISA
>            +-07.1  Intel Corporation 82371AB/EB/MB PIIX4 IDE
>            +-07.3  Intel Corporation 82371AB/EB/MB PIIX4 ACPI
>            +-07.7  VMware Virtual Machine Communication Interface
>            +-0f.0  VMware SVGA II Adapter
>            +-10.0  LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual
> Ultra320 SCSI
>            +-11.0-[02]--+-00.0  VMware USB1.1 UHCI Controller
>            |            +-01.0  Advanced Micro Devices [AMD] 79c970
> [PCnet32 LANCE]
>            |            +-02.0  Ensoniq ES1371 [AudioPCI-97]
>            |            +-03.0  VMware USB2 EHCI Controller
>            |            +-05.0  VMware Device 07e0
>            |            \-06.0  Intel Corporation 82545EM Gigabit Ethernet
> Controller (Copper)
>            +-15.0-[03]--
>            +-15.1-[04]--
>            +-15.2-[05]--
>            +-15.3-[06]--
>            +-15.4-[07]--
>            +-15.5-[08]--
>            +-15.6-[09]--
>            +-15.7-[0a]--
>            +-16.0-[0b]--
>            +-16.1-[0c]--
>            +-16.2-[0d]--
>            +-16.3-[0e]--
>            +-16.4-[0f]--
>            +-16.5-[10]--
>            +-16.6-[11]--
>            +-16.7-[12]--
>            +-17.0-[13]--
>            +-17.1-[14]--
>            +-17.2-[15]--
>            +-17.3-[16]--
>            +-17.4-[17]--
>            +-17.5-[18]--
>            +-17.6-[19]--
>            +-17.7-[1a]--
>            +-18.0-[1b]--
>            +-18.1-[1c]--
>            +-18.2-[1d]--
>            +-18.3-[1e]--
>            +-18.4-[1f]--
>            +-18.5-[20]--
>            +-18.6-[21]--
>            \-18.7-[22]--
>
>
> Regards
> Jyotiswarup
>
>
> On Tue, Nov 5, 2013 at 9:34 PM, Cyril Cressent <cyril.cressent at intel.com
> >wrote:
>
> > On Tue, Nov 05, 2013 at 08:01:06PM +0530, Jyotiswarup Raiturkar wrote:
> >
> > > Thanks for the quick reply. I saw some definitions of e1000_phy_82579
> > hence
> > > I thought (hoped) the NIC would be supported. I will try to run my dpdk
> > app
> > > inside a VM with an emulated e1000 NIC (just to test the code ..).
> >
> > As a general rule, even if you find references to a NIC in the poll mode
> > drivers, if it's not listed in
> > lib/librte_eal/common/include/rte_pci_dev_ids.h
> > then consider the NIC as not supported.
> >
> > Good luck with the VM,
> >
> > Cyril
> >
>


More information about the dev mailing list