Bug 2029126 - [virtio-win][balloon] The installed memory(RAM) doesn't change after hotplug a memory device
Summary: [virtio-win][balloon] The installed memory(RAM) doesn't change after hotplug ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.0
Hardware: x86_64
OS: Windows
medium
medium
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Mario Casquero
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-05 08:13 UTC by xiagao
Modified: 2023-06-27 07:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-27 06:27:31 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-104764 0 None None None 2021-12-05 08:20:20 UTC

Description xiagao 2021-12-05 08:13:14 UTC
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 1 Yvugenfi@redhat.com 2022-08-16 14:59:40 UTC
Not related to virtio-win drivers. Changing component.

Comment 7 Mario Casquero 2023-05-31 11:00:11 UTC
Hello Vadim,

Do you consider this bug to be closed?

Comment 8 Mario Casquero 2023-06-27 05:46:35 UTC
Kindly reminder, can this bug be closed?

Comment 9 Vadim Rozenfeld 2023-06-27 06:27:31 UTC
closing this bug based on comment https://bugzilla.redhat.com/show_bug.cgi?id=2029126#c4

Comment 10 xiagao 2023-06-27 07:06:46 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.