DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: 宋捷 <songj@zctt.com>
Cc: "'users'" <users@dpdk.org>
Subject: Re: [dpdk-users] testpmd can't start vmxnet3 nic
Date: Wed, 27 Feb 2019 11:01:54 -0800	[thread overview]
Message-ID: <20190227110154.5ffa57f1@shemminger-XPS-13-9360> (raw)
In-Reply-To: <5c75fe76.1c69fb81.40165.b34fSMTPIN_ADDED_BROKEN@mx.google.com>

On Wed, 27 Feb 2019 11:05:13 +0800
宋捷 <songj@zctt.com> wrote:

> Hi All,
> 
>  
> 
> I try to using testpmd with virtual NICs (e1000 and vmxnet3) in Esxi VM.
> 
> I bound one e1000 and one vmxnet3 into igb uio module, it’s Ok. 
> 
> But testpmd will be exit with below message:
> 
>  
> 
> EAL: Detected 4 lcore(s)
> 
> EAL: Detected 1 NUMA nodes
> 
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> 
> EAL: No free hugepages reported in hugepages-1048576kB
> 
> EAL: Probing VFIO support...
> 
> EAL: PCI device 0000:04:00.0 on NUMA socket -1
> 
> EAL:   Invalid NUMA socket, default to 0
> 
> EAL:   probe driver: 15ad:7b0 net_vmxnet3
> 
> EAL: PCI device 0000:0b:00.0 on NUMA socket -1
> 
> EAL:   Invalid NUMA socket, default to 0
> 
> EAL:   probe driver: 8086:10d3 net_e1000_em
> 
> EAL: PCI device 0000:0c:00.0 on NUMA socket -1
> 
> EAL:   Invalid NUMA socket, default to 0
> 
> EAL:   probe driver: 8086:10d3 net_e1000_em
> 
> EAL: PCI device 0000:13:00.0 on NUMA socket -1
> 
> EAL:   Invalid NUMA socket, default to 0
> 
> EAL:   probe driver: 15ad:7b0 net_vmxnet3
> 
> testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=6144,
> socket=0
> 
> testpmd: preferred mempool ops selected: ring_mp_mc
> 
> Configuring Port 0 (socket 0)
> 
> Port 0: 00:50:56:97:E9:44
> 
> Configuring Port 1 (socket 0)
> 
> Fail to configure port 1 rx queues

Some part of queue setup failed. Add log-level option to enable more logging
on vmxnet3 driver to find more detail.
	--log-level='pmd.net.vmxnet3.*:debug'

The vmxnet3 driver has a number of restrictions on size of Rx ring etc.

       reply	other threads:[~2019-02-27 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5c75fe76.1c69fb81.40165.b34fSMTPIN_ADDED_BROKEN@mx.google.com>
2019-02-27 19:01 ` Stephen Hemminger [this message]
2019-02-27  3:05 宋捷

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=20190227110154.5ffa57f1@shemminger-XPS-13-9360 \
    --to=stephen@networkplumber.org \
    --cc=songj@zctt.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).