Bug 1283072
Summary: | cold-plugged DIMM can't be unplugged on the first unplug request | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
Component: | qemu-kvm-rhev | Assignee: | Igor Mammedov <imammedo> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | CC: | hhuang, huding, imammedo, jen, juzhang, mrezanin, sherold, virt-maint, xfu, yuhuang |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.3.0-31.el7_2.2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1278894 | Environment: | |
Last Closed: | 2015-12-07 21:43:28 UTC | Type: | --- |
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: | 1278894 | ||
Bug Blocks: |
Description
Jan Kurik
2015-11-18 07:40:09 UTC
Reproduce: kernel: 3.10.0-329.el7.x86_64 qemu: qemu-kvm-rhev-2.3.0-29.el7 steps: 1. start a guest: /usr/libexec/qemu-kvm -m 4G,slots=8,maxmem=32G rhel72.img -object memory-backend-ram,id=m0,size=128M -device pc-dimm,id=dimm0,memdev=m0 -monitor stdio 2. after guest booted do unplug in monitor: (qemu)device_del dimm0 Guest print on console: -- ACPI: \_SB_.MP00: ACPI_NOTIFY_DEVICE_CHECK event acpi PNP0C80:00: Already enumerated -- and DIMM isn't unplugged. So the bug is reproduced on above environment. Reverify: kernel: 3.10.0-331.el7.x86_64 qemu-kvm: qemu-kvm-rhev-2.3.0-31.el7_2.2 With same steps as above, the DIMM is unplugged. So the bug is fixed. Reverify: kernel: 3.10.0-327.3.1.el7.x86_64 qemu-kvm: qemu-kvm-rhev-2.3.0-31.el7_2.3 QE test on above environment with same steps as comment 3, the DIMM is unplugged. So the bug is fixed. 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, 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://rhn.redhat.com/errata/RHBA-2015-2555.html |