From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 590] Transmit errors with i40e VF using SR-IOV on a vSphere VM
Date: Fri, 04 Dec 2020 02:04:39 +0000 [thread overview]
Message-ID: <bug-590-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=590
Bug ID: 590
Summary: Transmit errors with i40e VF using SR-IOV on a vSphere
VM
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: christopher.swindle@metaswitch.com
Target Milestone: ---
Overview:
I am trying to make use of DPDK with an XXV710 VF using SR-IOV on a vSphere VM,
however I am finding that with DPDK 20.11 that I am unable to transmit any
packets in my application. When running testpmd I find that there are no
packets transmitted and the tx-error stat just keeps getting incremented when a
packet is transmitted.
I did some further testing of different DPDK versions and found that the
following commit is the one that stopped these cards working in a vSphere VM:
https://github.com/DPDK/dpdk/commit/34283fc94847f237677edd5909639503c605daeb
When I revert this commit I find that i40e VFs on vSphere do work with DPDK
20.11.
Steps to Reproduce:
This can be reproduced with the following steps:
- Add an XXV710 VF SR-IOV interface to a vSphere VM
- Use testpmd to transmit packets on the vSphere VM (I used `testpmd -l 2,4,6
-- --stats-period=5 --forward-mode=mac --port-topology=loop`)
Actual Results:
The tx-error stats are incremented and no packets are transmitted.
Expected Results:
The packets should be transmitted.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-12-04 2:04 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-590-3@http.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.