From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1534] Transmit errors with iavf VF using SR-IOV on VM
Date: Fri, 06 Sep 2024 06:57:22 +0000 [thread overview]
Message-ID: <bug-1534-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1534
Bug ID: 1534
Summary: Transmit errors with iavf VF using SR-IOV on VM
Product: DPDK
Version: 24.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: Junya.Oda@anritsu.com
Target Milestone: ---
Overview:
I have created an application based on “examples/l2fwd”.
There is a problem that unable to transmit any packets.
(Receiving packets is working)
It seems similar to the following bug:
https://bugs.dpdk.org/show_bug.cgi?id=590
Steps to Reproduce:
1. Create SR-IOV VF on Hypervisor
2. Create VM with SR-IOV-Passthrough
3. Bind "igb_uio" to VF
4. Launch software
At step2, VF can communicate a external switch
Actual Results:
No packets are transmitted.
When "rte_eth_stats_get" is executed,
“oerrors” matched the number of packets that were attempted to be sent.
Expected Results:
The packets should be transmitted.
--- VM information ---
OS : Ubuntu 22.04.4 LTS
NIC : Intel E810
```
lspci -Dknn
0000:07:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Adaptive
Virtual Function [8086:1889] (rev 02)
Subsystem: Intel Corporation Ethernet Adaptive Virtual Function
[8086:0000]
Kernel driver in use: iavf
Kernel modules: iavf
```
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3638 bytes --]
next reply other threads:[~2024-09-06 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 6:57 bugzilla [this message]
2024-10-08 3:59 ` [DPDK/ethdev Bug 1534] Transmit errors with iavf VF using SR-IOV on VM bugzilla
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-1534-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.