DPDK usage discussions
 help / color / Atom feed
* [dpdk-users] Facing an issue in running DPDK in a container along with SR-IOV.
@ 2019-11-05 10:13 Prashanth Fernando
  0 siblings, 0 replies; only message in thread
From: Prashanth Fernando @ 2019-11-05 10:13 UTC (permalink / raw)
  To: users

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




^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-05 10:13 [dpdk-users] Facing an issue in running DPDK in a container along with SR-IOV Prashanth Fernando

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox