Problem
For a virtual machine (VM) running Windows Server as the guest operating system (OS):
- the platform's web interface incorrectly displays the used RAM value;
- the system generates low-memory warnings and sends corresponding email notifications, while actual memory usage inside the VM remains low.
This issue occurs because the guest OS lacks the balloon service, which is required for correct dynamic memory management in KVM. For Windows Server, this service is not installed automatically alongside the main virtio drivers and QEMU Guest Agent.
Note
For guaranteed correct operation of all features, it is recommended to use an OS from the Supported guest OS.
Diagnosis
To confirm the cause of the issue:
- Check the guest OS version:
- Navigate to Virtual Machines → select the VM → OS field.
- Ensure the OS is listed as Windows Server.
- Compare RAM metrics:
- Check real RAM usage inside the VM:
- On the target VM, open Task Manager → Performance tab → Physical Memory section.
- Note the value.
- Check the RAM value in VMmanager:
- Navigate to Virtual Machines → select the VM → Parameters → Information → RAM tab.
- Compare the values. Expected result: The values differ significantly.
- Check real RAM usage inside the VM:
- Check for the balloon service in the guest OS:
- On the target VM, open Task Manager → Services tab.
- Ensure the balloon service is absent or not running.
Solution
To resolve the issue, manually install the balloon service in the guest OS:
- Download the virtio-win-0.1.137.iso image.
- Mount the downloaded image to the guest OS.
- From the mounted image, install QEMU Guest Agent and the virtio drivers.
ImportantFor compatibility, all virtio-win components and guest additions must be installed from the same virtio-win image. - Copy the Balloon/2k8R2/amd64 directory from the mounted virtio-win image to the VM, for example, to C:\virtio\Balloon.
- Launch Command Prompt as Administrator.
- Navigate to the balloon service directory in the command prompt and install the service:
cd C:\virtio\Balloon\amd64 .\blnsvr.exe -i - Restart the VM. In the VMmanager web interface, go to Virtual Machines → select the VM → menu
→ Restart. - Verify that the RAM metrics for the VM in the platform now match the real values.
Useful tips
Related topics:
En
Es