D
Deleted member 116138
Guest
Aloha!
I think that sooner or later everybody dealt with Windows 10/11 VMs eating up their RAM, especially when ballooning has been activated.
I came across this problem again when I installed two new PVE (7.1) and set up 8 different Windows VMs (4x10 & 4x11 - 2 of each OS on each server). The server hardware differs in chipsets and CPUs (one Xeon and one Epyc system). VM setups are identical. Q35 v6.0 „chipset“, TPM for 11, VirtIO drivers 208, etc. Only differences are in amount of cores and maximum RAM allocation.
Long story short: every Windows VM started to eat up it‘s RAM after they were setup completely. Funny thing: as soon as I disabled the option
„Use my sign-in info to automatically finish setting up my device“ (settings -> accounts -> sign-in options)
and rebooted each VM the RAM usage dropped back to normal on every VM.
I think that sooner or later everybody dealt with Windows 10/11 VMs eating up their RAM, especially when ballooning has been activated.
I came across this problem again when I installed two new PVE (7.1) and set up 8 different Windows VMs (4x10 & 4x11 - 2 of each OS on each server). The server hardware differs in chipsets and CPUs (one Xeon and one Epyc system). VM setups are identical. Q35 v6.0 „chipset“, TPM for 11, VirtIO drivers 208, etc. Only differences are in amount of cores and maximum RAM allocation.
Long story short: every Windows VM started to eat up it‘s RAM after they were setup completely. Funny thing: as soon as I disabled the option
„Use my sign-in info to automatically finish setting up my device“ (settings -> accounts -> sign-in options)
and rebooted each VM the RAM usage dropped back to normal on every VM.
Last edited by a moderator: