Windows 2016 RAM Still Incorrect

[kotakomputer]

Even I already installed latest version of virtio-win iso (virtio-win-0.1.141.iso then virtio-win-0.1.171.iso) Proxmox still report RAM usage is 90%, even inside Windows only use 1GB.

Here is my settings:

1. Proxmox 5.3.8 dan guest Win 2016
   
2. RAM Ballon=0
3. HDD and NIC using VirtIO
4. Ballon Service and Qemu-Agent were running

Any idea why Proxmox still report 90% of RAM usage?

 

[sb-jw]

I thought PVE Reports not the RAM usage from inside the VM, so that's not possible everytime, for this it makes more sense to report the usage of the KVM Process itself. Could you check how many RAM the KVM process currently use?

 

[kotakomputer]

KVM must reports RAM inside VM, this behavior works fine on WinXP, Win 2003, Win7 and Win2008.

Abnormal RAM report only happen on Win 2012 and Win 2016 (maybe Win 10 also), even I have installed Balloon Service & Qemu-Agent.

 

[kotakomputer]

Here is my config:

# cat 2016.conf
agent: 1
balloon: 0
bootdisk: virtio0
cores: 2
memory: 4096
name: win2016
net0: virtio=D6:6C:AF:A7:96:4D,bridge=vmbr2
numa: 0
onboot: 1
ostype: win10
sata0: local-data:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
scsihw: virtio-scsi-pci
smbios1: uuid=08bb21b5-aeac-49de-a9c2-aa7d91c0f872
sockets: 1
virtio0: local-data:2016/vm-2016-disk-0.qcow2,cache=writeback,size=30G
vmgenid: 64b0efdc-5c7f-4f4f-9bca-05d411efb475
#

 

[wolfgang]

Hi,
Is the ballooning service running in the VM?
You have to install the ballooning driver and the service.

 

[kotakomputer]

Yes ... Balloon Service already ran in Windows.
Below is the screenshot of Proxmox Summary and VM inside.

 

[tom]

balloon: 0

you disabled balloon device. enable it again and it will start working.

 

[kotakomputer]

you disabled balloon device. enable it again and it will start working.

I have try Balloon with 5.000/10.000 RAM then stop/start VM but still overload displayed on Proxmox, ram starting 0.5 % then increase near to 92%.

Also has been trying with balloon min/max 10.000/10.000 but no luck.