From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1789] vmxnet3_dev_start fails in vmxnet3_v4_rss_configure() for single queue in ESX8.0 causing application to exit
Date: Fri, 19 Sep 2025 20:15:01 +0000 [thread overview]
Message-ID: <bug-1789-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2638 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1789
Bug ID: 1789
Summary: vmxnet3_dev_start fails in vmxnet3_v4_rss_configure()
for single queue in ESX8.0 causing application to exit
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: amiyaranjan.mohakud@gmail.com
Target Milestone: ---
DPDK Version: 19.11
ESX version: ESX8.0
We faced an exact similar issue as mentioned in
https://mails.dpdk.org/archives/users/2025-April/008236.html.
Context Details:
-----------------
In ESXi 8.0 setup with dpdk-19.11, when the HW compatibility version is ESX8.0
and with single queue pair configuration, the RSS gets enabled. As a result,
vmxnet3_v4_rss_configure() gets called and fails while writing/reading from
BAR1 hw register. It looks to be some compatibility issue with dpdk-19.11 and
ESX8.0.
if (VMXNET3_VERSION_GE_4(hw) &&
dev->data->dev_conf.rxmode.mq_mode == ETH_MQ_RX_RSS) {
/* Check for additional RSS */
ret = vmxnet3_v4_rss_configure(dev);
if (ret != VMXNET3_SUCCESS) {
PMD_INIT_LOG(ERR, "Failed to configure v4 RSS");
return ret;
}
}
As a result, it causes the application to exit.
Proposed fix:
I have a plausible fix for this. The fix is to disable RSS for such a case (
the fix should go only in 19.11). During dev_configure(), we can set the
mq_mode to ETH_MQ_RX_NONE if the num_rx_queues is 1. This would avoid calling
of vmxnet3_v4_rss_configure().
/* Disabling RSS for single queue pair */
if (dev->data->nb_rx_queues == 1) {
dev->data->dev_conf.rxmode.mq_mode = ETH_MQ_RX_NONE;
PMD_INIT_LOG(ERR, "WARN: Disabling RSS for single Rx queue");
}
Pls verify and let me know if it can be upstreamed. Once confirmed/approved, If
required, I can generate a main stream patch for it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4674 bytes --]
reply other threads:[~2025-09-19 20:15 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=bug-1789-3@https.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).