-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-9.4, rhel-9.5, rhel-9.6, rhel-10.0
-
qemu-kvm-9.1.0-10.el10
-
No
-
Low
-
rhel-sst-virtualization
-
ssg_virtualization
-
3
-
False
-
-
None
-
None
-
Pass
-
None
-
-
x86_64
-
None
What were you trying to do that didn't work?
While trying to reproduce Postcopy live migration issue RHEL-27832, qemu-kvm logged an error saying:
2024-09-05T20:38:41.124872Z qemu-kvm: Fail to update device iotlb 2024-09-05T20:38:41.137950Z qemu-kvm: Fail to update device iotlb
What is the impact of this issue to you?
- It keeps vhost device from starting properly. Which may leads to guest restart via libvirtd(8).
Please provide the package NVR for which the bug is seen:
kernel-5.14.0-426.el9.x86_64
qemu-kvm-8.2.0-6.el9.x86_64
libvirt-10.0.0-4.el9.x86_64
How reproducible is this bug?:
- It requires vhost-user device setup used in the test-case of RHEL-27832.
Expected results
- Handle vhost device start errors properly.
Actual results
- vhost device error is not handled currently.
- clones
-
RHEL-72945 qemu-kvm: vhost: reports error while updating IOTLB entries
- Release Pending
- is depended on by
-
RHEL-27832 The post-copy migration of RT-VM leads to race while accessing vhost-user device and hung/stalled target VM
- In Progress
- links to
-
RHBA-2024:139510 qemu-kvm bug fix and enhancement update