-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.2.0
-
kernel-5.14.0-583.el9
-
None
-
Important
-
2
-
rhel-virt-hwe-arm-1
-
ssg_virtualization
-
12
-
14
-
3
-
-
False
-
False
-
None
-
Virt ARM 25-4, Virt ARM 25-5
-
Undefined
-
-
Unspecified
-
Unspecified
-
None
-
Merge Request passes all submitter checks, Merge Request finished CI testing, Merge Request passed CI testing, Merge Request approved by peer review
Description of problem:
Baoquan He said:
Yes, definitely, please add a shutdown(). That is a known issue already.
The device not being shutdown explicitly could have on-flight DMA when
you trigger kexec jumping into 2nd kernel. Before initializing the
virtio-devces and irte tables, the on-flight DMA may continue sending
irq to go through the old irte table if it's not overwriten, or get
wrong error message if have been overwriten.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- blocks
-
RHEL-85800 [virtio shutdown] qemu reports "virtio: zero sized buffers are not allowed" in "virsh reboot vm" for vm protected by smmuv3
-
- Release Pending
-
-
RHEL-7334 [viommu/vhost] [virtio shutdown] qemu-kvm: Fail to lookup the translated address
-
- Closed
-
-
RHEL-70845 [RHEL9.6] [virtio shutdown] virtio: bogus descriptor or out of resources, qemu Assertion
-
- Closed
-
- is related to
-
RHEL-85800 [virtio shutdown] qemu reports "virtio: zero sized buffers are not allowed" in "virsh reboot vm" for vm protected by smmuv3
-
- Release Pending
-
-
RHEL-26264 qemu reports "virtio: zero sized buffers are not allowed" during guest reboot which protected by smmuv3
-
- Closed
-
- links to
-
RHSA-2025:146839 kernel bug fix and enhancement update