Bug 1743098
| Summary: | QEMU core dumped after unplug balloon device under q35 with Win2019 guest | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Yumei Huang <yuhuang> |
| Component: | qemu-kvm | Assignee: | Julia Suvorova <jusual> |
| qemu-kvm sub component: | PCI | QA Contact: | Yumei Huang <yuhuang> |
| Status: | CLOSED ERRATA | Docs Contact: | Jiri Herrmann <jherrman> |
| Severity: | high | ||
| Priority: | high | CC: | ailan, chayang, ddepaula, demeng, gfialova, jherrman, jsuvorov, jusual, juzhang, lijin, mdean, rbalakri, virt-maint, ybendito, yfu, yvugenfi |
| Version: | 8.1 | Keywords: | Reopened, Triaged |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-6.1.0-3.module+el8.6.0+12952+612d1b20 | Doc Type: | Bug Fix |
| Doc Text: |
.Hot-unplugging a balloon device from a Windows Server 2019 guest now works correctly
Previously, attempting to detach a memory balloon device from a running Q35 Windows Server 2019 guest operating system in some cases caused the guest to terminate unexpectedly. With this update, detaching balloon devices in the described circumstances works correctly.
|
Story Points: | --- |
| Clone Of: | 1690256 | Environment: | |
| Last Closed: | 2022-05-10 13:18:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1690256 | ||
| Bug Blocks: | 1744438, 1746622, 1771318, 1897024, 1948357 | ||
|
Description
Yumei Huang
2019-08-19 05:57:46 UTC
(gdb) bt
#0 0x000055b6c5bbdf0d in virtio_pci_notify_write
(opaque=0x55b6c6dff170, addr=0, val=<optimized out>, size=<optimized out>)
at hw/virtio/virtio-pci.c:1360
#1 0x000055b6c59fe596 in memory_region_write_accessor
(mr=<optimized out>, addr=<optimized out>, value=<optimized out>, size=<optimized out>, shift=<optimized out>, mask=<optimized out>, attrs=...)
at /usr/src/debug/qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447.x86_64/memory.c:530
#2 0x000055b6c59fc9e6 in access_with_adjusted_size
(addr=addr@entry=0, value=value@entry=0x7f1ad1d72628, size=size@entry=2, access_size_min=<optimized out>, access_size_max=<optimized out>, access_fn=access_fn@entry=
0x55b6c59fe550 <memory_region_write_accessor>, mr=0x55b6c6df7cd0, attrs=...)
at /usr/src/debug/qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447.x86_64/memory.c:597
#3 0x000055b6c5a0084a in memory_region_dispatch_write
(mr=0x55b6c6df7cd0, addr=0, data=<optimized out>, size=2, attrs=...)
at /usr/src/debug/qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447.x86_64/memory.c:1474
#4 0x000055b6c59aebbc in flatview_write
(fv=0x7f1abc0407c0, addr=<optimized out>, attrs=..., buf=<optimized out>, len=<optimized out>)
at /usr/src/debug/qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447.x86_64/exec.c:3099
#5 0x000055b6c59b3243 in address_space_write
(as=<optimized out>, addr=<optimized out>, attrs=..., buf=<optimized out>, len=<optimized out>) at /usr/src/debug/qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447.x86_64/exec.c:3265
#6 0x000055b6c5a0f878 in kvm_cpu_exec (cpu=<optimized out>)
at /usr/src/debug/qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447.x86_64/accel/kvm/kvm-all.c:2004
#7 0x000055b6c59ec21e in qemu_kvm_cpu_thread_fn (arg=0x55b6c6bdddd0)
at /usr/src/debug/qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447.x86_64/cpus.c:1215
#8 0x00007f1adb4732de in start_thread (arg=<optimized out>) at pthread_create.c:486
#9 0x00007f1adb1a4133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks Hi Julia, Recently I hit similar issues on win2019-64(q35) guest based on rhel9 host. but it not hit coredump after unplug balloon device, but no "DEVICE_DELETED" event. The thing we're planned is to file same driver issue on one bz as tracker, so I update it here. if you don't think they are the same issue ,please feel free to let me know, thanks in advance. oh right, one more question for you btw： when will we fix this issue? just need to plan our test progress. thanks. good day. BRs Dehan Meng (In reply to dehanmeng from comment #14) > Hi Julia, > Recently I hit similar issues on win2019-64(q35) guest based on rhel9 host. > but it not hit coredump after unplug balloon device, but no "DEVICE_DELETED" > event. If this is not qemu core dump this is different issue by definition (this BZ is for qemu core dump). Additionally if you reproduce the problem you described under avocado setup this might be completely different issue. Please open new BZ, mention avocado setup, provide qemu command line and refer the tracker BZ After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. The fix was merged to upstream https://github.com/qemu/qemu/commit/c3fd706165e9875a10606453ee2785dd51e987a5 Hi Is this fixed in current qemu in RHEL? Is it expected to be fixed automatically by the rebase on RHEL-8.6? Please clarify this. Then set ITR accordingly. (In reply to Danilo Cesar Lemes de Paula from comment #21) > Hi > > Is this fixed in current qemu in RHEL? > Is it expected to be fixed automatically by the rebase on RHEL-8.6? > > Please clarify this. Then set ITR accordingly. The fix is not in RHEL, but it's merged upstream. According to Amnon, it should be in RHEL 8.6 with rebase. Set 'Verified:Tested,SanityOnly' as gating test with qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac pass. Hi Julia, Danilo, I i understand correctly, the Fixed In Version 'qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac' is incorrect. From the errata, the qemu-kvm version should be qemu-kvm-15:6.1.0-3.module+el8.6.0+12952+612d1b20. Could you help confirm ? Thanks! Best regards Yanan Fu Correct a typo, from the errata, the qemu-kvm version should be qemu-kvm-6.1.0-3.module+el8.6.0+12952+612d1b20. Tested with qemu-kvm-6.1.0-3.module+el8.6.0+12952+612d1b20 / kernel-4.18.0-348.1.el8.x86_64, the issue is not reproduced, Win2019 & Win2022 guest works well after repeating hotplug/unplug balloon device. Thank you for spotting the issue Yanan. Corrected on our part. (In reply to Yanan Fu from comment #27) > Set 'Verified:Tested,SanityOnly' as gating test with > qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac pass. Gating test with the updated 'fixed in version': qemu-kvm-6.1.0-3.module+el8.6.0+12952+612d1b20 pass too. So, the 'Verified' filed remain valid, thanks. Pre verification pass. Moving to verified per comment 30&34. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:1759 |