From: venkataprasad k <prasaddml@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] testpmd + EAL: No probed ethernet devices + dpdk-17.11.1
Date: Mon, 23 Apr 2018 18:05:06 +0530 [thread overview]
Message-ID: <CABFMH+eknWzTH4XUFAM6UM1v5+1kS8Tq2aLL+LvTYX-h_xgj4g@mail.gmail.com> (raw)
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
next reply other threads:[~2018-04-23 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 12:35 venkataprasad k [this message]
2018-04-23 16:25 ` Rosen, Rami
2018-04-24 4:14 ` venkataprasad k
2018-04-24 5:06 ` Stephen Hemminger
2018-04-24 9:23 ` venkataprasad k
2018-04-24 12:31 ` Rosen, Rami
2018-04-24 13:16 ` venkataprasad k
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABFMH+eknWzTH4XUFAM6UM1v5+1kS8Tq2aLL+LvTYX-h_xgj4g@mail.gmail.com \
--to=prasaddml@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).