I setup a windows 10 VM with ballooning of 512mb/2048mb
PVE is up to date, windows is up to date and I used the newest virtio ballooning drivers 0.1.185
The VM is taking more memory then has been allocated to it. It should not exceed 2048mb = 2GB.
The VM starts with ~1.5GB, after some hours the kvm process uses 4GB, then after a while it drops down to 3,2GB and seems to stay there.
This is what the server memory summary looks like, before the VM boot memory was at 21.4GB, the peak was 26.4GB and then it settled at 24.6GB:
VM summary:
Given that the VM summary shows a memory usage of 1,43GB why does it use 3,2GB memory.
That's actual used memory and not buffers/cache as soon as I stop the VM the Server Summary as well as "free -m" and "htop" show 3,2GB less memory usage.
PVE is up to date, windows is up to date and I used the newest virtio ballooning drivers 0.1.185
The VM is taking more memory then has been allocated to it. It should not exceed 2048mb = 2GB.
The VM starts with ~1.5GB, after some hours the kvm process uses 4GB, then after a while it drops down to 3,2GB and seems to stay there.
This is what the server memory summary looks like, before the VM boot memory was at 21.4GB, the peak was 26.4GB and then it settled at 24.6GB:
VM summary:
Given that the VM summary shows a memory usage of 1,43GB why does it use 3,2GB memory.
That's actual used memory and not buffers/cache as soon as I stop the VM the Server Summary as well as "free -m" and "htop" show 3,2GB less memory usage.
Last edited: