From: "Douglas, Frederick E" <fed2@illinois.edu>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] no driver found for pcap-based virtual NIC (eth_pcap0)
Date: Fri, 11 Mar 2016 18:46:32 +0000 [thread overview]
Message-ID: <BFE986AFFB13EF4C9B7536D7E896431DBF75AF66@chimbx2.ad.uillinois.edu> (raw)
I'm new to DPDK. I've gotten the basics working, but I'm having trouble with the .pcap file-based virtual interface. The EAL is failing to set things up when I ask it to use a pcap virtual interface, with:
--vdev 'eth_pcap0,rx_pcap=/full/path/to/iperf_udp.pcap,tx_pcap=/full/path/to/NEW.pcap'
It says "EAL: no driver found for eth_pcap0; EAL: failed to initialize eth_pcap0 device; PANIC in rte_eal_init(): Cannot init pmd devices".
Everything works fine with the all-in-memory virtual interfaces (--vdev=eth_ring0 --vdev=eth_ring1). I even confirmed (with chunks of code from https://github.com/marty90/DPDK-Dump) that I can get testpmd to use a pcap_dumper_t to dump the traffic it processes to a .pcap file.
There doesn't seem to be anything in the setup.sh consolidated setup menu about pcap, and the part of the manual describing the pcap vdev (http://dpdk.org/doc/guides/nics/pcap_ring.html#libpcap-based-pmd) doesn't mention anything that needs to be done - in fact it's in the manual right together with the in-memory ring-based driver. I found a drivers/net/pcap directory with a Makefile that had never been made, but nothing changed after making it.
In case any of this might matter:
=I'm trying to run testpmd (with some slight modifications, which work as expected with the ring vdev)
=Ubuntu 14.04; DPDK configured for x86_64-native-linuxapp-gcc
=1024 2MiB hugepages
So, does anyone have any idea? I have a feeling I'm missing something really simple... but I'm out of ideas about what that might be!
next reply other threads:[~2016-03-11 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 18:46 Douglas, Frederick E [this message]
2016-03-14 9:05 ` Panu Matilainen
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=BFE986AFFB13EF4C9B7536D7E896431DBF75AF66@chimbx2.ad.uillinois.edu \
--to=fed2@illinois.edu \
--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).