Hi, You need to bind a device to DPDK before launching testpmd, with the usertools/dpdk-devbind.py script. Did you do it? What is the output of ./usertools/dpdk-devbind.py -s on your host ? do you see any entries under "Network devices using DPDK-compatible driver" when running ./usertools/dpdk-devbind.py -s?
Please take a look in the "Linux Getting Started Guide", section 4.4: "Binding and Unbinding Network Ports to/from the Kernel Modules" http://dpdk.org/doc/guides/linux_gsg/linux_drivers.html#binding-and-unbinding-network-ports-to-from-the-kernel-modules Regards, Rami Rosen -----Original Message----- From: users [mailto:[email protected]] On Behalf Of venkataprasad k Sent: Monday, April 23, 2018 15:35 To: [email protected] Subject: [dpdk-users] testpmd + EAL: No probed ethernet devices + dpdk-17.11.1 Hello, I am trying to run testpmd application and getting the following error "EAL: No probed ethernet devices" version: dpdk-stable-17.11.1 Log: [root@localhost dpdk-stable-17.11.1]# ./build/app/testpmd –l 12,13,14 –n 4 -- -i EAL: Detected 80 lcore(s) EAL: No free hugepages reported in hugepages-1048576kB EAL: Probing VFIO support... EAL: VFIO support initialized EAL: PCI device 0000:01:00.0 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device 0000:01:00.1 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device 0000:01:00.2 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device 0000:01:00.3 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb *EAL: No probed ethernet devices* Interactive-mode selected USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=779456, size=2176, socket=0 USER1: create a new mbuf pool <mbuf_pool_socket_1>: n=779456, size=2176, socket=1 USER1: create a new mbuf pool <mbuf_pool_socket_2>: n=779456, size=2176, socket=2 USER1: create a new mbuf pool <mbuf_pool_socket_3>: n=779456, size=2176, socket=3 Done testpmd> show config fwd io packet forwarding - ports=0 - cores=0 - streams=0 - NUMA support enabled, MP over anonymous pages disabled testpmd> from the dpdk-setup script, i see there are devices supported by dpdk Network devices using DPDK-compatible driver ============================================ 0000:03:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused= 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused= 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused= 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused= 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused= 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused= 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused= 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused= Network devices using kernel driver =================================== 0000:01:00.0 'I350 Gigabit Network Connection 1521' if=enp1s0f0 drv=igb unused=vfio-pci *Active* 0000:01:00.1 'I350 Gigabit Network Connection 1521' if=enp1s0f1 drv=igb unused=vfio-pci 0000:01:00.2 'I350 Gigabit Network Connection 1521' if=enp1s0f2 drv=igb unused=vfio-pci 0000:01:00.3 'I350 Gigabit Network Connection 1521' if=enp1s0f3 drv=igb unused=vfio-pci Other Network devices ===================== <none> My understanding is, it should consider the devices under "Network devices using DPDK-compatible driver", but it is not. The nic that i am using Intel 82599, which is supported by dpdk. can someone help me to understand what is wrong here? Thanks, Venkat
