Skip to contentSkip to conversation

Vhost multi-queue reconnection failed with QEMU version 4.2.0 to 5.1.0

DPDK/vhost/virtio Bug 1658 [email protected] 1 participant 2 messages Feb 3, 2025 – Feb 7, 2025

lore
Share & tools
lore
#0 lore raw

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: [email protected]
          Reporter: [email protected]

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).

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=1658

Kevin Traynor ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[email protected]

--- Comment #1 from Kevin Traynor ([email protected]) --- 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.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.