From: Murali Krishna <murali.krishna@broadcom.com>
To: users@dpdk.org
Subject: [dpdk-users] error while launching dpdk-pdump with ovs-dpdk setup
Date: Wed, 2 Jan 2019 12:15:31 +0530 [thread overview]
Message-ID: <a428012bbeeecbc49afbf1b2932ef7b9@mail.gmail.com> (raw)
Hello Everyone,
I am trying to capture packets using dpdk-pdump in ovs-dpdk environment.
I am using dpdk-17.11 and openvswitch 2.9.3, I enabled below config options
in dpdk/common/config_base.
CONFIG_RTE_LIBRTE_PMD_PCAP=y
CONFIG_RTE_LIBRTE_PDUMP=y
Configured ovs bridge with one dpdk port
I am getting below error while launching dpdk-dpump.
# ./x86_64-native-linuxapp-gcc/app/dpdk-pdump -- --pdump
port=0,queue=*,rx-dev=/tmp/pkts.pcap
--server-socket-path=/usr/local/var/run/openvswitch
EAL: Detected 32 lcore(s)
EAL: Probing VFIO support...
EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the
kernel.
EAL: This may cause issues with mapping memory into secondary processes
EAL: PCI device 0000:0b:00.0 on NUMA socket 0
EAL: probe driver: 14e4:16d7 net_bnxt
EAL: PCI device 0000:0b:00.1 on NUMA socket 0
EAL: probe driver: 14e4:16d7 net_bnxt
EAL: PCI device 0000:0b:02.0 on NUMA socket 0
EAL: probe driver: 14e4:16c1 net_bnxt
EAL: PCI device 0000:0b:02.1 on NUMA socket 0
EAL: probe driver: 14e4:16c1 net_bnxt
EAL: PCI device 0000:0b:0a.0 on NUMA socket 0
EAL: probe driver: 14e4:16c1 net_bnxt
bnxt_dev_init(): Broadcom NetXtreme driver bnxt
EAL: PCI device 0000:0b:0a.1 on NUMA socket 0
EAL: probe driver: 14e4:16c1 net_bnxt
PMD: Initializing pmd_pcap for net_pcap_rx_0
PMD: Creating pcap-backed ethdev on numa socket -1
PDUMP: failed to send to server:No such file or directory,
pdump_create_client_socket:703
PDUMP: client request for pdump enable/disable failed
PDUMP: failed to send to server:No such file or directory,
pdump_create_client_socket:703
PDUMP: client request for pdump enable/disable failed
EAL: Error - exiting with code: 1
Cause: Unknown error -1
Any help is much appreciated.
Thanks in advance,
Murali
next reply other threads:[~2019-01-02 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 6:45 Murali Krishna [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-02 6:18 Murali Krishna
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=a428012bbeeecbc49afbf1b2932ef7b9@mail.gmail.com \
--to=murali.krishna@broadcom.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).