After upgrade from PVE 8.x to 9.0 - the Windows guest machine shows memory usage about 100,47%. I have installed latest virtio drivers, dosabled balooning and checked many other parameters... Nothing helps. Is that a PVE bug? I have never had similar problem with this VM before upgrade to PVE 9.0.x
Windows Guest memory utilization problem on PVE 9.0.x
- Thread starter rzirzi
- Start date
See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher
Is the Ballooning Device enabled and is the BallooningService running?
Is the Ballooning Device enabled and is the BallooningService running?
pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve)
one of the windows VMs shows 100.xx% memory usage in PVE VM summary.
windows 11 guest, memory 16384MB, ballooning enabled, minimum memory 16384MB.
virtio 0.1.271 (updated from 0.1.240 to 0.1.266 and 0.1.271 due that issue), taskmanager shows 3.2GB ram usage.
BalloonService / blnsvr.exe up and running.
everything works fine so far, so it is cosmetic issue for me.
one of the windows VMs shows 100.xx% memory usage in PVE VM summary.
windows 11 guest, memory 16384MB, ballooning enabled, minimum memory 16384MB.
virtio 0.1.271 (updated from 0.1.240 to 0.1.266 and 0.1.271 due that issue), taskmanager shows 3.2GB ram usage.
BalloonService / blnsvr.exe up and running.
everything works fine so far, so it is cosmetic issue for me.
Last edited:
following output:
balloon: actual=8192 max_mem=8192 last_update=1756638096
interesting, last update August 31. 01:51 oclock. about that time i did a minor PVE update + reboot + updated virtio drivers to 0.1.271
checked on different VM where memory is shown correctly:
balloon: actual=4096 max_mem=4096 total_mem=4095 free_mem=2355 mem_swapped_in=10480902144 mem_swapped_out=297967616 major_page_faults=383769 minor_page_faults=96456984 last_update=1756784004
both VMs are nearly identical, both on same node, both got same virtio driver in the night.
another affected vm, guest is server 2012r2 with some old virtio drivers:
balloon: actual=8192 max_mem=8192 last_update=1756605071
balloon: actual=8192 max_mem=8192 last_update=1756638096
interesting, last update August 31. 01:51 oclock. about that time i did a minor PVE update + reboot + updated virtio drivers to 0.1.271
checked on different VM where memory is shown correctly:
balloon: actual=4096 max_mem=4096 total_mem=4095 free_mem=2355 mem_swapped_in=10480902144 mem_swapped_out=297967616 major_page_faults=383769 minor_page_faults=96456984 last_update=1756784004
both VMs are nearly identical, both on same node, both got same virtio driver in the night.
another affected vm, guest is server 2012r2 with some old virtio drivers:
balloon: actual=8192 max_mem=8192 last_update=1756605071
Last edited: