DPDK patches and discussions
 help / color / mirror / Atom feed
From: Puneet singh <Puneet.singh@truringsoftek.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] "Incompatible UPT  version” error when running DPDK on VMWare with VMXNET3 interface ,ESXI Version 6.5/6.7
Date: Mon, 1 Oct 2018 09:48:34 +0000	[thread overview]
Message-ID: <MA1PR01MB0715E31E432A91C8D376B3DA9EEF0@MA1PR01MB0715.INDPRD01.PROD.OUTLOOK.COM> (raw)

Hi Everyone,


We're trying to run DPDK test-pmd app in a guest machine running Red Hat 7.5. The host is ESXi version 6.5/6.7.

I'm building dpdk on the guest machine , I've tried both DPDK versions 18.08 and 17.11. We have created three interfaces on esxi for connection to our guest. One management port and two data ports. We're binding these two data ports to DPDK. The ports are all VMXNET3 interfaces.

I am using test-pmd application, it worked only when I start the app for first time. We are getting following error when I restart the application ,tried using the uio_pci_generic and igb_uio driver, same issue with both the driver.

Whenever I reboot the VM ,test-pmd works fine for first time ,if i restart the test-pmd it always giving following error.
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:0c:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL:   Not managed by a supported kernel driver, skipped
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
EAL:   PCI memory mapped at 0x140000000
EAL:   PCI memory mapped at 0x140001000
EAL:   PCI memory mapped at 0x140002000
PMD: eth_vmxnet3_dev_init():  >>
PMD: eth_vmxnet3_dev_init(): Hardware version : 1
PMD: eth_vmxnet3_dev_init(): Using device version 1

PMD: eth_vmxnet3_dev_init(): UPT hardware version : 0
PMD: eth_vmxnet3_dev_init(): Incompatible UPT version.
EAL:   PCI memory unmapped at 0x140000000
EAL:   PCI memory unmapped at 0x140001000
EAL:   PCI memory unmapped at 0x140002000
EAL: Requested device 0000:13:00.0 cannot be used
EAL: PCI device 0000:1b:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15ad:7b0 net_vmxnet3
EAL:   Not managed by a supported kernel driver, skipped
EAL: No probed ethernet devices
Interactive-mode selected
USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176, socket=0
Done



Any help to resolve above issue would be greatly appreciated. Thanks!



Regards

Puneet Singh

                 reply	other threads:[~2018-10-01  9:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=MA1PR01MB0715E31E432A91C8D376B3DA9EEF0@MA1PR01MB0715.INDPRD01.PROD.OUTLOOK.COM \
    --to=puneet.singh@truringsoftek.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).