From: Markus Fohrer <markus.fohrer@webked.de>
To: virtualization@lists.linux-foundation.org
Cc: mst@redhat.com, jasowang@redhat.com, davem@davemloft.net,
edumazet@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [REGRESSION] Massive virtio-net throughput drop in guest VM with Linux 6.8+
Date: Wed, 02 Apr 2025 23:12:07 +0200 [thread overview]
Message-ID: <1d388413ab9cfd765cd2c5e05b5e69cdb2ec5a10.camel@webked.de> (raw)
Hi,
I'm observing a significant performance regression in KVM guest VMs using virtio-net with recent Linux kernels (6.8.1+ and 6.14).
When running on a host system equipped with a Broadcom NetXtreme-E (bnxt_en) NIC and AMD EPYC CPUs, the network throughput in the guest drops to 100–200 KB/s. The same guest configuration performs normally (~100 MB/s) when using kernel 6.8.0 or when the VM is moved to a host with Intel NICs.
Test environment:
- Host: QEMU/KVM, Linux 6.8.1 and 6.14.0
- Guest: Linux with virtio-net interface
- NIC: Broadcom BCM57416 (bnxt_en driver, no issues at host level)
- CPU: AMD EPYC
- Storage: virtio-scsi
- VM network: virtio-net, virtio-scsi (no CPU or IO bottlenecks)
- Traffic test: iperf3, scp, wget consistently slow in guest
This issue is not present:
- On 6.8.0
- On hosts with Intel NICs (same VM config)
I have bisected the issue to the following upstream commit:
49d14b54a527 ("virtio-net: Suppress tx timeout warning for small tx")
https://git.kernel.org/linus/49d14b54a527
Reverting this commit restores normal network performance in affected guest VMs.
I’m happy to provide more data or assist with testing a potential fix.
Thanks,
Markus Fohrer
next reply other threads:[~2025-04-02 21:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 21:12 Markus Fohrer [this message]
2025-04-03 13:04 ` Michael S. Tsirkin
2025-04-03 13:51 ` Markus Fohrer
2025-04-03 14:03 ` Michael S. Tsirkin
2025-04-03 14:26 ` Willem de Bruijn
2025-04-03 20:00 ` Markus Fohrer
2025-04-03 20:35 ` Markus Fohrer
2025-04-03 20:07 ` Markus Fohrer
2025-04-03 21:06 ` Michael S. Tsirkin
2025-04-03 21:24 ` Markus Fohrer
2025-04-03 21:49 ` Willem de Bruijn
2025-04-03 22:05 ` Michael S. Tsirkin
2025-04-04 11:32 ` Markus Fohrer
2025-04-04 8:16 ` Markus Fohrer
2025-04-04 8:29 ` Michael S. Tsirkin
2025-04-04 8:52 ` Markus Fohrer
2025-04-04 11:40 ` Markus Fohrer
2025-04-04 15:13 ` Willem de Bruijn
2025-04-04 20:23 ` Markus Fohrer
2025-04-04 22:05 ` Ilya Maximets
2025-04-05 6:15 ` Markus Fohrer
2025-04-05 12:18 ` Ilya Maximets
2025-04-04 7:59 ` Torsten Krah
2025-04-04 8:26 ` Michael S. Tsirkin
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=1d388413ab9cfd765cd2c5e05b5e69cdb2ec5a10.camel@webked.de \
--to=markus.fohrer@webked.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®