From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/vhost/virtio Bug 1658] Vhost multi-queue reconnection failed with QEMU version 4.2.0 to 5.1.0
Date: Mon, 03 Feb 2025 04:36:57 +0000 [thread overview]
Message-ID: <bug-1658-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1658
Bug ID: 1658
Summary: Vhost multi-queue reconnection failed with QEMU
version 4.2.0 to 5.1.0
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: vhost/virtio
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
It’s a QEMU regression bug (bad commit: c6beefd674ff). QEMU only saves acked
features for one vhost-net when vhost quits. When vhost reconnects to
virtio-net/virtio-pmd in multi-queue situations, the features been set multiple
times are not consistent. QEMU-5.2.0 fixes this issue in commit f66337bdbfda
(“vhost-user: save features of multiqueues if chardev is closed”).
Implication
Vhost cannot reconnect back to virtio-net/virtio-pmd normally.
Resolution/Workaround:
It is possible to filter the incorrect acked features at vhost-user side.
Affected Environment/Platform:
ALL.
Driver/Module:
Virtual Device Poll Mode Driver (PMD).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3135 bytes --]
next reply other threads:[~2025-02-03 4:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 4:36 bugzilla [this message]
2025-02-07 11:54 ` [DPDK/vhost/virtio Bug 1658] Vhost multi-queue reconnection failed with QEMU version 4.2.0 to 5.1.0 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-1658-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.