From: Alan Beadle <ab.beadle@gmail.com>
To: users@dpdk.org
Subject: Help Running Example
Date: Sun, 6 Aug 2023 11:33:43 -0400 [thread overview]
Message-ID: <CANTAOdzZuYy5AjAn7an1y=T_FOny8JqYntsjYTD+d3Oq53C13g@mail.gmail.com> (raw)
Hi,
I need some help getting DPDK working. I am running Ubuntu 20.04 with
a modified Linux 5.4 kernel, but I have also tried the stock Ubuntu
5.15 kernel with the same results.
Here is my NIC info from lspci:
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (3)
I219-LM (rev 09)
I built and installed DPDK from source, and applied the following boot
flags: "intel_iommu=on iommu=pt"
After booting I did the following as root:
echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
ifconfig enp0s31f6 down
dpdk-devbind.py --bind=vfio-pci 0000:00:1f.6
All of this appeared to work.
I tried running the "skeleton" example program and got the following output:
sudo ./build/basicfwd
EAL: Detected CPU lcores: 16
EAL: Detected NUMA nodes: 1
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
EAL: 0000:00:1f.6 VFIO group is not viable! Not all devices in IOMMU
group bound to VFIO or unbound
EAL: Requested device 0000:00:1f.6 cannot be used
TELEMETRY: No legacy callbacks, legacy socket not created
EAL: Error - exiting with code: 1
Cause: Error: number of ports must be even
I'm not at all familiar with DPDK or VFIO. What might the problem be?
-Alan
next reply other threads:[~2023-08-06 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 15:33 Alan Beadle [this message]
2023-08-07 19:40 ` Stephen Hemminger
2023-08-08 0:26 ` Stephen Hemminger
2023-08-08 15:25 ` Alan Beadle
2023-08-08 15:31 ` Alan Beadle
2023-08-08 16:01 ` Stephen Hemminger
[not found] ` <CA+3hWewvP9xSncfK4vcUz+KH7cQsO7hjXU4=hgDdntHNjfJ2-w@mail.gmail.com>
2023-08-08 3:23 ` Fwd: " Fuji Nafiul
2023-08-08 3:25 ` Fuji Nafiul
2023-08-09 17:35 ` Alan Beadle
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='CANTAOdzZuYy5AjAn7an1y=T_FOny8JqYntsjYTD+d3Oq53C13g@mail.gmail.com' \
--to=ab.beadle@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).