DPDK usage discussions
 help / color / mirror / Atom feed
From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: VM SR-IOV VF fails dpdk
Date: Tue, 12 Dec 2023 16:33:51 +0000	[thread overview]
Message-ID: <PH0PR01MB6730815FCA914E4044F0858E8F8EA@PH0PR01MB6730.prod.exchangelabs.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

Hi,
I am finding an issue on ESXi host running our Linux VM application.  The DPDK version is 17.11 and VM OS is 3.10.0-1160.81.1.el7.x86_64.
ESXi host version is 7.03.
The NIC is the Intel x710-DA2 in SR-IOV mode.  Configured on ESXi host 4 virtual functions.
Our VM has one of the four virtual functions from the x710 NIC for DPDK port.

In our application, when we initialize the port and all the checks pass, but rte_eth_dev_start() fails for -1 return code.
The failure from gdb is:
i40evf_configure_vsi_queues(): Failed to execute command of VIRTCHNL_OP_CONFIG_VSI_QUEUES
i40evf_dev_start(): configure queues failed

Our application requires 1 Rx queue and 4 Tx queues.

When I change the number of Tx queues from 4 to 1 the failure is not seen.  However our application requires 4 Tx queues so not an option.
This same VM ran successfully when ESXi host was 5.5.

We had our IT department do a sanity check on the ESXi host and upgrade any VIBs recommended, but did not resolve the problem.

Tried testpmd and also failed for DPDK start.

Thanks,
Ed



[-- Attachment #2: Type: text/html, Size: 3451 bytes --]

             reply	other threads:[~2023-12-12 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 16:33 Lombardo, Ed [this message]
2023-12-12 16:43 ` Stephen Hemminger

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=PH0PR01MB6730815FCA914E4044F0858E8F8EA@PH0PR01MB6730.prod.exchangelabs.com \
    --to=ed.lombardo@netscout.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).