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: Fri, 07 Feb 2025 11:54:11 +0000 [thread overview]
Message-ID: <bug-1658-3-3VZCXgRuk0@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1658-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1658
Kevin Traynor (ktraynor@redhat.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
CC| |ktraynor@redhat.com
--- Comment #1 from Kevin Traynor (ktraynor@redhat.com) ---
Just to note looking at Qemu code and when bug and fix were committed, this
affects only Qemu versions between v4.2.0 and v5.1.0.
Closing as this is a Qemu bug and there is no action required for DPDK.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2956 bytes --]
prev parent reply other threads:[~2025-02-07 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 4:36 [DPDK/vhost/virtio Bug 1658] Vhost multi-queue reconnection failed with QEMU version 4.2.0 to 5.1.0 bugzilla
2025-02-07 11:54 ` bugzilla [this message]
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-3VZCXgRuk0@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.