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:
Hotplug a memory device, but the installed memory(RAM) is not changed.
Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1-215
kernel-5.14.0-5.el9.x86_64
qemu-kvm-6.1.0-8.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. boot up windows guest with balloon device, memory size is 4G
-m 4096,maxmem=64G,slots=4 \
2. install balloon driver.
3. hotplug a 1G memory device
{'execute': 'object-add', 'arguments': {'qom-type': 'memory-backend-ram', 'id': 'mem-plug', 'size': 1073741824}, 'id': 'rkYDy9sF'}
{"return": {}, "id": "rkYDy9sF"}
{"execute": "device_add", "arguments": {"driver": "pc-dimm", "id": "dimm-plug", "memdev": "mem-plug"}, "id": "c0Ag0e1B"}
{"return": {}, "id": "c0Ag0e1B"}
4. get physical memory via wmic cmd, the result is 5G.
wmic ComputerSystem get TotalPhysicalMemory
5. check installed memory in system
"Start" -> "System" -> "Installed memory(RAM)" ,the result is 4G.
Actual results:
The installed memory(RAM) doesn't change after hotplug a memory device.
Expected results:
The hotplug memory should be recognized by OS.
Additional info:
Test windows guest: win2012,win2016,win2019, all have this problem.
Comment 1Yvugenfi@redhat.com
2022-08-16 14:59:40 UTC
Not related to virtio-win drivers. Changing component.
From comment0 and comment4, I thought it was fixed in some qemu version. I prefer to close it as CURRENRELEASE.
Feel free to correct me if there is something not correct.
Thanks.
Description of problem: Hotplug a memory device, but the installed memory(RAM) is not changed. Version-Release number of selected component (if applicable): virtio-win-prewhql-0.1-215 kernel-5.14.0-5.el9.x86_64 qemu-kvm-6.1.0-8.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1. boot up windows guest with balloon device, memory size is 4G -m 4096,maxmem=64G,slots=4 \ 2. install balloon driver. 3. hotplug a 1G memory device {'execute': 'object-add', 'arguments': {'qom-type': 'memory-backend-ram', 'id': 'mem-plug', 'size': 1073741824}, 'id': 'rkYDy9sF'} {"return": {}, "id": "rkYDy9sF"} {"execute": "device_add", "arguments": {"driver": "pc-dimm", "id": "dimm-plug", "memdev": "mem-plug"}, "id": "c0Ag0e1B"} {"return": {}, "id": "c0Ag0e1B"} 4. get physical memory via wmic cmd, the result is 5G. wmic ComputerSystem get TotalPhysicalMemory 5. check installed memory in system "Start" -> "System" -> "Installed memory(RAM)" ,the result is 4G. Actual results: The installed memory(RAM) doesn't change after hotplug a memory device. Expected results: The hotplug memory should be recognized by OS. Additional info: Test windows guest: win2012,win2016,win2019, all have this problem.