-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.4
-
Regression
-
sst_virtualization_networking
-
ssg_virtualization
-
1
-
False
-
-
Red Hat Enterprise Linux
-
None
-
-
Unspecified
-
None
What were you trying to do that didn't work?
Boot a guest with multi queues vdpa device, then qemu output error messages after reboot multiple times: qemu-kvm: unable to start vhost net: 5: falling back on userspace virtio. And guest can not ping vdpa bridge.
Please provide the package NVR for which bug is seen:
qemu-kvm-8.2.0-1.el9.x86_64
kernel-5.14.0-404.el9.x86_64
iproute-6.2.0-5.el9.x86_64
flint -d 0000:0d:00.0 q
Image type: FS4
FW Version: 22.39.2048
FW Release Date: 29.11.2023
Product Version: 22.39.2048
Rom Info: type=UEFI version=14.32.17 cpu=AMD64,AARCH64
type=PXE version=3.7.300 cpu=AMD64
Description: UID GuidsNumber
Base GUID: b8cef603000a110c 4
Base MAC: b8cef60a110c 4
Image VSD: N/A
Device VSD: N/A
PSID: MT_0000000359
Security Attributes: N/A
How reproducible:
100%
Steps to reproduce
1. Create a multi queues vdpa device
vdpa dev add name vdpa0 mgmtdev pci/0000:0d:0.2 mac 00:11:22:33:44:00 max_vqp 8
done
2. Boot a guest with this vdpa device
-device '{"driver": "virtio-net-pci", "mac": "00:11:22:33:44:00", "id": "idqMOSNu", "mq": true, "vectors": 18, "netdev": "idQuYIba", "bus": "pcie-root-port-3", "addr": "0x0"}' \
-netdev '{"id": "idQuYIba", "type": "vhost-vdpa", "vhostdev": "/dev/vhost-vdpa-0", "queues": 8}' \
3. Reboot this guest multiple times(About 10 times), qemu output error messages:
There is no this error messages, ang guest can ping succeed to vdpa bridge.
Actual results
qemu output error messages and guest can not ping succeed to vdpa bridge
Additional Info:
1. It can test pass on the qemu-kvm-8.1.0-5.el9.x86_64, so it should be a regression bug.