From: Prashanth Fernando <prashanth.fernando@tatacommunications.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Facing an issue in running DPDK in a container along with SR-IOV.
Date: Tue, 5 Nov 2019 10:13:07 +0000 [thread overview]
Message-ID: <SG2PR04MB3352EA7458A2F233A80424BCF87E0@SG2PR04MB3352.apcprd04.prod.outlook.com> (raw)
Hi,
I am trying to run DPDK in a container and listen on a VF, I am unable to run DPDK. It fails with the following error.
Not sure what I am missing.
EAL: Detected 72 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:19:00.0 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:19:00.1 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:19:00.2 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:19:00.3 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:5e:00.0 on NUMA socket 0
EAL: probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:5e:00.1 on NUMA socket 0
EAL: probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:5e:00.2 on NUMA socket 0
EAL: probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:5e:00.3 on NUMA socket 0
EAL: probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:5e:02.0 on NUMA socket 0
EAL: probe driver: 8086:154c net_i40e_vf
EAL: 0000:5e:02.0 not managed by VFIO driver, skipping
EAL: PCI device 0000:5e:02.1 on NUMA socket 0
EAL: probe driver: 8086:154c net_i40e_vf
EAL: PCI device 0000:5e:02.2 on NUMA socket 0
EAL: probe driver: 8086:154c net_i40e_vf
EAL: PCI device 0000:5e:02.3 on NUMA socket 0
EAL: probe driver: 8086:154c net_i40e_vf
EAL: PCI device 0000:5e:02.4 on NUMA socket 0
EAL: probe driver: 8086:154c net_i40e_vf
EAL: PCI device 0000:5e:02.5 on NUMA socket 0
EAL: probe driver: 8086:154c net_i40e_vf
EAL: PCI device 0000:60:00.0 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:60:00.1 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:86:00.0 on NUMA socket 1
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:86:00.1 on NUMA socket 1
EAL: probe driver: 8086:1583 net_i40e
EAL: Error - exiting with code: 1
Cause: No physical ports!
-----------------------------------------------------------------------------------------------------
Before Binding Interface:
====================
/usr/src/dpdk/usertools/dpdk-devbind.py -s
Network devices using kernel driver
===================================
0000:5e:02.0 'Ethernet Virtual Function 700 Series 154c' if=veth0 drv=iavf unused=vfio-pci *Active*
-----------------------------------------------------------------------------------------------------
Binding an interface:
=====================
#/usr/src/dpdk/usertools/dpdk-devbind.py --bind=vfio-pci 0000:5e:02.0
-----------------------------------------------------------------------------------------------------
After Binding Interface:
====================
# /usr/src/dpdk/usertools/dpdk-devbind.py -s
Network devices using DPDK-compatible driver
============================================
0000:5e:02.0 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci unused=iavf
reply other threads:[~2019-11-05 10:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=SG2PR04MB3352EA7458A2F233A80424BCF87E0@SG2PR04MB3352.apcprd04.prod.outlook.com \
--to=prashanth.fernando@tatacommunications.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).