From: Arseniy Zaostrovnykh <arseniy.zaostrovnykh@epfl.ch>
To: users@dpdk.org
Subject: Re: [dpdk-users] error running l3fwd on kvm
Date: Thu, 12 Nov 2015 17:48:22 +0100 [thread overview]
Message-ID: <5644C2D6.6040407@epfl.ch> (raw)
In-Reply-To: <5644C251.4070907@epfl.ch>
Another possible cause just come to my mind:
some drivers do not support more than 1 queues in each direction. You
have 2 transmission queues (nb_txq=2) here.
On 12.11.2015 17:46, Arseniy Zaostrovnykh wrote:
> You may lack memory. Make sure you are allocating enough hugepages (at
> least 1Gb)
>
> On 12.11.2015 17:13, Arevalo, Mario Alfredo C wrote:
>> From: Arevalo, Mario Alfredo C
>> Sent: Thursday, November 12, 2015 7:54 AM
>> To: users@dpdk.org
>> Subject: error running l3fwd on kvm
>>
>> Hello guys, I'm trying to run l3fwd, it works very well when I
>> run it in bare-metal, however
>> when I try to run in a Virtual Machine I get the next error:
>>
>> EAL: Detected lcore 0 as core 0 on socket 0
>> EAL: Detected lcore 1 as core 0 on socket 0
>> EAL: Detected lcore 2 as core 1 on socket 0
>> EAL: Detected lcore 3 as core 1 on socket 0
>> EAL: Detected lcore 4 as core 2 on socket 0
>> EAL: Detected lcore 5 as core 2 on socket 0
>> EAL: Detected lcore 6 as core 3 on socket 0
>> EAL: Detected lcore 7 as core 3 on socket 0
>> EAL: Support maximum 128 logical core(s) by configuration.
>> EAL: Detected 8 lcore(s)
>> EAL: VFIO modules not all loaded, skip VFIO support...
>> EAL: Setting up physically contiguous memory...
>> EAL: Ask a virtual area of 0x600000 bytes
>> EAL: Virtual area found at 0x7f9905000000 (size = 0x600000)
>> EAL: Ask a virtual area of 0x200000 bytes
>> EAL: Virtual area found at 0x7f9904c00000 (size = 0x200000)
>> EAL: Ask a virtual area of 0x35400000 bytes
>> EAL: Virtual area found at 0x7f98cf600000 (size = 0x35400000)
>> EAL: Requesting 430 pages of size 2MB from socket 0
>> EAL: TSC frequency is ~2294687 KHz
>> EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using
>> unreliable clock cycles !
>> EAL: open shared lib librte_pmd_virtio.so
>> EAL: Master lcore 0 is ready (tid=634d1c0;cpuset=[0])
>> EAL: lcore 1 is ready (tid=cf3f6700;cpuset=[1])
>> EAL: PCI device 0000:00:02.0 on NUMA socket -1
>> EAL: probe driver: 1af4:1000 rte_virtio_pmd
>> EAL: PCI device 0000:00:03.0 on NUMA socket -1
>> EAL: probe driver: 1af4:1000 rte_virtio_pmd
>> EAL: PCI device 0000:00:04.0 on NUMA socket -1
>> EAL: probe driver: 1af4:1000 rte_virtio_pmd
>> EAL: PCI device 0000:00:05.0 on NUMA socket -1
>> EAL: probe driver: 1af4:1000 rte_virtio_pmd
>> 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
>>
>> has someone seen this error before?
>>
>> Thank you.
>> Mario.
>>
>>
>
--
Respectfully,
Arseniy.
next prev parent reply other threads:[~2015-11-12 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6594B51DBE477C48AAE23675314E6C460F77F91B@fmsmsx107.amr.corp.intel.com>
2015-11-12 16:13 ` Arevalo, Mario Alfredo C
2015-11-12 16:46 ` Arseniy Zaostrovnykh
2015-11-12 16:48 ` Arseniy Zaostrovnykh [this message]
2015-11-12 16:56 ` Mario Carrillo
2015-11-12 17:12 ` Mario Carrillo
2015-11-12 18:25 ` Arseniy Zaostrovnykh
2015-11-12 20:50 ` Mario Carrillo
2015-11-13 14:47 ` Mario Carrillo
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=5644C2D6.6040407@epfl.ch \
--to=arseniy.zaostrovnykh@epfl.ch \
--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).