-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.3.0
-
None
-
Moderate
-
CustomerScenariosInitiative
-
rhel-sst-virtualization-windows
-
ssg_virtualization
-
5
-
False
-
-
None
-
None
-
None
-
Automated
-
Known Issue
-
-
Done
-
-
x86_64
-
None
Description of problem:
Boot up win10-64 guest with 30G memory, try to evict guest memory to a minimum value and then try to enlarge it to the maximum one, and then evict it to half of the maximum one, and then reboot guest os, after the system booted up and watch the balloon value, it was not ballooned to the expected value(15G), so seems that balloon doesn't work after os reboot.
Here is the qmp log before and after the system reboot.
```
2023-04-26 02:40:56:
2023-04-26 02:40:56: {"return":
{"actual": 18107858944}, "id": "lRp6Y5LN"}
2023-04-26 02:41:11: {"timestamp":
, "event": "BALLOON_CHANGE", "data": {"actual": 32212254720}}
2023-04-26 02:41:43: {"timestamp":
, "event": "RESET", "data": {"guest": true, "reason": "guest-reset"}}
2023-04-26 02:41:43: {"timestamp":
, "event": "RESET", "data": {"guest": true, "reason": "guest-reset"}}
2023-04-26 02:43:45: {"timestamp":
, "event": "BALLOON_CHANGE", "data": {"actual": 32210157568}}
2023-04-26 02:43:45: {"timestamp":
, "event": "BALLOON_CHANGE", "data": {"actual": 32208060416}}
2023-04-26 02:43:45:
2023-04-26 02:43:45: {"return":
{"actual": 32208060416}, "id": "11PU1Cgr"}
2023-04-26 02:43:55:
2023-04-26 02:43:55: {"return":
{"actual": 32208060416}, "id": "FUSSA9YL"}
2023-04-26 02:44:03:
2023-04-26 02:44:03: {"return":
{"actual": 32208060416}, "id": "VwuFkLts"}
2023-04-26 02:44:12:
2023-04-26 02:44:12: {"return":
{"actual": 32208060416}, "id": "TNPdjEFX"}
2023-04-26 02:44:20:
2023-04-26 02:44:20: {"return":
{"actual": 32208060416}, "id": "CUF3X1hU"}
2023-04-26 02:44:28:
2023-04-26 02:44:28: {"return":
{"actual": 32208060416}, "id": "CDDg0jXH"}
2023-04-26 02:44:37:
2023-04-26 02:44:37: {"return":
{"actual": 32208060416}, "id": "i7zjcSx5"}
2023-04-26 02:44:45:
2023-04-26 02:44:45: {"return":
{"actual": 32208060416}, "id": "Pkd82nf3"}
2023-04-26 02:44:53:
2023-04-26 02:44:53: {"return":
{"actual": 32208060416}, "id": "agkGOKzR"}
2023-04-26 02:45:02:
2023-04-26 02:45:02: {"return":
{"actual": 32208060416}, "id": "yEjAWK7X"}
2023-04-26 02:45:10:
2023-04-26 02:45:10: {"return":
{"actual": 32208060416}, "id": "xihgQ1Wg"}
2023-04-26 02:45:18:
2023-04-26 02:45:18: {"return":
{"actual": 32208060416}, "id": "bBPNk1gV"}
```
Note:
The guest rebooted successfully and quickly.
Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1-236
kernel-5.14.0-302.el9.x86_64
qemu-kvm-8.0.0-1.el9.x86_64
seabios-bin-1.16.1-1.el9.noarch
How reproducible:
I tried on two hosts:
dell-per750-14: 4/10 (all logs: http://virtqetools.lab.eng.pek2.redhat.com/kvm_autotest_job_log/?jobid=7787589)
dell-per750-13: 1/10
Steps to Reproduce:
1. boot up win10-64 guest with balloon device(q35 + seabios)
-m 30720 \
-device virtio-balloon-pci,id=balloon0,bus=pcie-root-port-4,addr=0x0 \
2. in guest, install balloon driver
3. Run evict test to get the minimum memory of guests.
2023-04-26 02:39:13: {"execute": "balloon", "arguments":
, "id": "DHbP7HBM"}
2023-04-26 02:39:13: {"return": {}, "id": "DHbP7HBM"}
....
2023-04-26 02:40:00: {"timestamp":
, "event": "BALLOON_CHANGE", "data": {"actual": 2919235584}}
2023-04-26 02:40:00:
2023-04-26 02:40:00: {"return":
{"actual": 2919235584}, "id": "FBLeXsgq"}
4. balloon memory back to the maximum one
2023-04-26 02:40:00: {"execute": "balloon", "arguments":
, "id": "kfT5rtMt"}
2023-04-26 02:40:38:
2023-04-26 02:40:38: {"return":
{"actual": 32212254720}, "id": "RTgEDUyN"}
5. balloon memory to about half the size of the maximum one.
2023-04-26 02:40:45: {"execute": "balloon", "arguments":
, "id": "lm8svpko"}
...
2023-04-26 02:40:56:
2023-04-26 02:40:56: {"return":
{"actual": 18107858944}, "id": "SGIc3MC5"}
6. reboot the guest.
023-04-26 02:41:11: {"timestamp":
, "event": "BALLOON_CHANGE", "data": {"actual": 32212254720}}
2023-04-26 02:41:43: {"timestamp":
, "event": "RESET", "data": {"guest": true, "reason": "guest-reset"}}
2023-04-26 02:41:43: {"timestamp":
, "event": "RESET", "data": {"guest": true, "reason": "guest-reset"}}
2023-04-26 02:43:45: {"timestamp":
, "event": "BALLOON_CHANGE", "data": {"actual": 32210157568}}
2023-04-26 02:43:45: {"timestamp":
, "event": "BALLOON_CHANGE", "data": {"actual": 32208060416}}
2023-04-26 02:43:45:
2023-04-26 02:43:45: {"return":
{"actual": 32208060416}, "id": "11PU1Cgr"}
2023-04-26 02:43:55:
2023-04-26 02:43:55: {"return":
{"actual": 32208060416}, "id": "FUSSA9YL"}
2023-04-26 02:44:03:
2023-04-26 02:44:03: {"return":
{"actual": 32208060416}, "id": "VwuFkLts"}
2023-04-26 02:44:12:
2023-04-26 02:44:12: {"return":
{"actual": 32208060416}, "id": "TNPdjEFX"}
Actual results:
The memory value came back to the maximum one.
Expected results:
After rebooting os, the memory keeps the value like before.
Additional info: