Hello,

I am having difficulties running dpdk-pdump on a fresh setup.  I previously had 
it working on a different VM/app/DPDK version combo, but somehow it now doesn't 
(version 18.05, testpmd being the primary app).  Error is "failed to parse 
device".  Does anyone have an idea of how to debug this?

>:~/dpdk-18.05/out/bin$ sudo ./dpdk-pdump -- --pdump 
>'device_id=0002:00:02.0,queue=*,rx-dev=/home/dashel/capture-rx.pcap,tx-dev=/home/dashel/capture-tx.pcap'
EAL: Detected 8 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_18627_e6fcbc35bcdc
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable 
clock cycles !
EAL: PCI device 0001:00:02.0 on NUMA socket 0
EAL:   probe driver: 15b3:1004 net_mlx4
PMD: net_mlx4: PCI information matches, using device "mlx4_0" (VF: true)
PMD: net_mlx4: 1 port(s) detected
PMD: net_mlx4: port 1 MAC address is 00:0d:3a:06:8c:55
EAL: PCI device 0002:00:02.0 on NUMA socket 0
EAL:   probe driver: 15b3:1004 net_mlx4
PMD: net_mlx4: PCI information matches, using device "mlx4_1" (VF: true)
PMD: net_mlx4: 1 port(s) detected
PMD: net_mlx4: port 1 MAC address is 00:0d:3a:06:58:2f
ERROR: failed to parse device "net_pcap_rx_0"
EAL: Error - exiting with code: 1
  Cause: vdev creation failed:create_mp_ring_vdev:631

Verified that CONFIG_RTE_LIBRTE_PDUMP=y

I am launching the primary app first, then the PDUMP binary.  Like I said, this 
flow worked previously, but now doesn't and I can't figure out where to start 
debugging this.  If anyone ran into something similar recently, would 
appreciate any pointers.

Daniel

Reply via email to