DPDK usage discussions
 help / color / Atom feed
* [dpdk-users] EAL: Failed to hotplug add device
@ 2020-09-01  8:00 Dinesh Ramesh
  0 siblings, 0 replies; only message in thread
From: Dinesh Ramesh @ 2020-09-01  8:00 UTC (permalink / raw)
  To: users

I am trying to test my application with trex and dpdk l3fwd.
It's like sending the traffic from trex port 0 and it should land on l3fwd
app port 1 and it should reverse the traffic again from port 1 to port 0.
port 0 is ingress and port 1 is egress.
sending the traffic in port 0 from trex, and l3fwd app running on port 1.
To verify the packet is correctly landing on the l3fwd app, I am using
dpdk-pdump. But I am facing the below issue while running the dpdk-pdump

EAL: Failed to hotplug add device
EAL: Error - exiting with code: 1
  Cause: vdev creation failed:create_mp_ring_vdev:770

*l3fwd app logs:*
=============
[root@localhost l3fwd]# ./build/l3fwd -c 0x2 -n 1 -- -P -p 0x2
--config="(1,0,1)" --parse-ptype --eth-dest 1,00:0c:29:1a:14:d3
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL: PCI device 0000:0b:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL: PCI device 0000:13:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
soft parse-ptype is enabled
LPM or EM none selected, default LPM on

Skipping disabled port 0
Initializing port 1 ... Creating queues: nb_rxq=1 nb_txq=1... Port 1
modified RSS hash function based on hardware support,requested:0xa38c
configured:0x104
 Address:00:0C:29:05:6D:E1, Destination:00:0C:29:1A:14:D3, Allocated mbuf
pool on socket 0
LPM: Adding route 198.18.1.0 / 24 (1)
LPM: Adding route 2001:200:0:0:1:: / 48 (1)
txq=1,0,0

Initializing rx queues on lcore 1 ... rxq=1,0,0

Port 1: softly parse packet type info

Checking link statusdone
Port1 Link Up. Speed 10000 Mbps -full-duplex
L3FWD: entering main loop on lcore 1
L3FWD:  -- lcoreid=1 portid=1 rxqueueid=0
EAL: failed to parse device "vdev:net_pcap_rx_0"
EAL: Failed to hotplug add device on primary

*dpdk-pdumo logs:*
*=====================*

[root@localhost dpdk-19.11]# ./build/app/dpdk-pdump -- --pdump
'port=1,queue=*,rx-dev=/tmp/capture.pcap'
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_23775_af66fc548a2ec
EAL: Selected IOVA mode 'PA'
EAL: Probing VFIO support...
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL: PCI device 0000:0b:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL: PCI device 0000:13:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL: Failed to hotplug add device
EAL: Error - exiting with code: 1
  Cause: vdev creation failed:create_mp_ring_vdev:770
[root@localhost dpdk-19.11]#

Can you please help me on this and what i am missing here.

Thanks,
DR

^ 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 --
2020-09-01  8:00 [dpdk-users] EAL: Failed to hotplug add device Dinesh Ramesh

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