From: B Gopikrishna <b.gopikrishna@tcs.com>
To: dev@dpdk.org
Subject: [dpdk-dev] rte_eth_dev_configure fails on VM with e1000 drivers
Date: Fri, 18 Apr 2014 17:39:37 +0530 [thread overview]
Message-ID: <OF525AF595.018F8F54-ON65257CBE.0042CC6D-65257CBE.0042CC9B@tcs.com> (raw)
In-Reply-To:
Hi
when I run the l3fwd application with the below command line, I am observing the error "Cannot configure device: err=-22, port=0". The complete log is posted below.
./build/l3fwd -c 0x03 -n 2 -- -p 0x03 --config="(0,0,0),(1,1,1)"
Setup:
a) Virtual machine booted with Fedora20 with 2 virtual CPU
b) compiled DPDK git version
c) configured 2 vNIC's with e1000 drivers
Any help in resolving the error would be of great help.
********************************************************************
Network devices using IGB_UIO driver
====================================
0000:00:0b.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=
0000:00:0c.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=igb_ui
********************************************************************
EAL: Master core 0 is ready (tid=8ac3e880)
EAL: Core 1 is ready (tid=3f1b0700)
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: probe driver: 1af4:1000 rte_virtio_pmd
EAL: 0000:00:03.0 not managed by UIO driver, skipping
EAL: PCI device 0000:00:0b.0 on NUMA socket -1
EAL: probe driver: 8086:100e rte_em_pmd
EAL: PCI memory mapped at 0x7fa58abe8000
EAL: PCI device 0000:00:0c.0 on NUMA socket -1
EAL: probe driver: 8086:100e rte_em_pmd
EAL: PCI memory mapped at 0x7fa58abc8000
Initializing port 0 ... Creating queues: nb_rxq=1 nb_txq=2... EAL: Error - exiting with code: 1
Cause: Cannot configure device: err=-22, port=0
********************************************************************
Regards
Gopi Krishna B
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
next reply other threads:[~2014-04-18 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 12:09 B Gopikrishna [this message]
2014-04-18 12:31 ` Thomas Monjalon
2014-04-18 12:37 ` Tomasz K
2014-04-29 9:28 ` B Gopikrishna
2014-04-29 9:39 ` Marc Sune
2014-04-29 9:30 ` [dpdk-dev] rte_eth_dev_configure fails on VM with e1000 drivers #PERSONAL# B Gopikrishna
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=OF525AF595.018F8F54-ON65257CBE.0042CC6D-65257CBE.0042CC9B@tcs.com \
--to=b.gopikrishna@tcs.com \
--cc=dev@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).