From: Eduard Gibert Renart <edugibert@gmail.com>
To: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: [dpdk-dev] Cannot run l3fwd
Date: Thu, 6 Nov 2014 14:39:41 -0500 [thread overview]
Message-ID: <236BCFEC-58FD-47D2-9B5E-E892CE8FBF6D@gmail.com> (raw)
In-Reply-To: <545BBBF4.7010501@bisdn.de>
Hi Everyone:
When I try to run l3fwd inside my VM I get the following error:
ubuntu@ubuntu-VirtualBox:~/Desktop/dpdk-1.7.1/examples/l3fwd/build$ sudo ./l3fwd -c 0x3 -n 2 -- -p 0x3 --config="(0,0,0),(1,0,1)"
EAL: Cannot read numa node link for lcore 0 - using physical package id instead
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Cannot read numa node link for lcore 1 - using physical package id instead
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Support maximum 64 logical core(s) by configuration.
EAL: Detected 2 lcore(s)
EAL: Setting up memory...
EAL: cannot open /proc/self/numa_maps, consider that all memory is in socket_id 0
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0xb6400000 (size = 0x400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0xb6000000 (size = 0x200000)
EAL: Ask a virtual area of 0xf000000 bytes
EAL: Virtual area found at 0xa6e00000 (size = 0xf000000)
EAL: Ask a virtual area of 0x1e200000 bytes
EAL: Virtual area found at 0x88a00000 (size = 0x1e200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x88600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x88200000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x87e00000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x87a00000 (size = 0x200000)
EAL: Ask a virtual area of 0xe400000 bytes
EAL: Virtual area found at 0x79400000 (size = 0xe400000)
EAL: Ask a virtual area of 0x2200000 bytes
EAL: Virtual area found at 0x77000000 (size = 0x2200000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x76200000 (size = 0xc00000)
EAL: Ask a virtual area of 0xe00000 bytes
EAL: Virtual area found at 0x75200000 (size = 0xe00000)
EAL: Requesting 512 pages of size 2MB from socket 0
EAL: TSC frequency is ~2503668 KHz
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
EAL: Master core 0 is ready (tid=b75c2800)
EAL: Core 1 is ready (tid=751ffb40)
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: probe driver: 8086:100e rte_em_pmd
EAL: 0000:00:03.0 not managed by UIO driver, skipping
EAL: PCI device 0000:00:08.0 on NUMA socket -1
EAL: probe driver: 8086:100e rte_em_pmd
EAL: PCI memory mapped at 0xb7572000
EAL: PCI device 0000:00:09.0 on NUMA socket -1
EAL: probe driver: 8086:100e rte_em_pmd
EAL: PCI memory mapped at 0xb7552000
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: probe driver: 8086:100e rte_em_pmd
EAL: 0000:00:03.0 not managed by UIO driver, skipping
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
Any ideas on what is causing the error?
Thanks,
Eduard Gibert Renart
next prev parent reply other threads:[~2014-11-06 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 0:17 [dpdk-dev] [RFC PATCH] Adding RTE_KNI_PREEMPT configuration option Marc Sune
2014-11-06 18:20 ` Marc Sune
2014-11-06 19:39 ` Eduard Gibert Renart [this message]
2014-11-06 20:57 ` [dpdk-dev] Cannot run l3fwd Thomas Monjalon
2014-11-06 23:44 ` Ananyev, Konstantin
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=236BCFEC-58FD-47D2-9B5E-E892CE8FBF6D@gmail.com \
--to=edugibert@gmail.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).