Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
commit aa8580cd "pc: memhp: force gaps between DIMM's GPA"
regressed memory hot-unplug for linux guests triggering
following BUGON
=====
kernel BUG at mm/memory_hotplug.c:703!
...
[<ffffffff81385fa7>] acpi_memory_device_remove+0x79/0xa5
[<ffffffff81357818>] acpi_bus_trim+0x5a/0x8d
[<ffffffff81359026>] acpi_device_hotplug+0x1b7/0x418
===
BUG_ON(phys_start_pfn & ~PAGE_SECTION_MASK);
===
reson for it is that x86-64 linux guest supports memory
hotplug in chunks of 128Mb and memory section also should
be 128Mb aligned.
However gaps forced between 128Mb DIMMs with backend's
natural alignment of 2Mb make the 2nd and following
DIMMs not being aligned on 128Mb boundary as it was
originally.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.3.0-31
How reproducible:
100%
Steps to Reproduce:
1. start RHEL72 guest liek this:
/usr/libexec/qemu-kvm -enable-kvm -m 4G,slots=8,maxmem=32G rhel72.img -object memory-backend-ram,id=m0,size=1G -device pc-dimm,id=dimm0,memdev=m0 -snapshot -numa node -object memory-backend-ram,id=m1,size=1G -device pc-dimm,id=dimm1,memdev=m1 -monitor unix:/tmp/u,server,nowait -nographic
2. execute following command twice:
echo "device_del dimm1" | nc -U /tmp/u
Actual results:
guest crash
Expected results:
no guest crash
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-2016-2673.html
Description of problem: commit aa8580cd "pc: memhp: force gaps between DIMM's GPA" regressed memory hot-unplug for linux guests triggering following BUGON ===== kernel BUG at mm/memory_hotplug.c:703! ... [<ffffffff81385fa7>] acpi_memory_device_remove+0x79/0xa5 [<ffffffff81357818>] acpi_bus_trim+0x5a/0x8d [<ffffffff81359026>] acpi_device_hotplug+0x1b7/0x418 === BUG_ON(phys_start_pfn & ~PAGE_SECTION_MASK); === reson for it is that x86-64 linux guest supports memory hotplug in chunks of 128Mb and memory section also should be 128Mb aligned. However gaps forced between 128Mb DIMMs with backend's natural alignment of 2Mb make the 2nd and following DIMMs not being aligned on 128Mb boundary as it was originally. Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.3.0-31 How reproducible: 100% Steps to Reproduce: 1. start RHEL72 guest liek this: /usr/libexec/qemu-kvm -enable-kvm -m 4G,slots=8,maxmem=32G rhel72.img -object memory-backend-ram,id=m0,size=1G -device pc-dimm,id=dimm0,memdev=m0 -snapshot -numa node -object memory-backend-ram,id=m1,size=1G -device pc-dimm,id=dimm1,memdev=m1 -monitor unix:/tmp/u,server,nowait -nographic 2. execute following command twice: echo "device_del dimm1" | nc -U /tmp/u Actual results: guest crash Expected results: no guest crash