Hi, I wanted to check and see if this is normal behavior.
I have two Windows Server 2019 VM's running on this node, each set to have a maximum of 16gb of memory with a 2gb minimum. The virtio balloon drivers are installed and the balloon service is running. Proxmox seems to show one of the VM's (Its random, usually the one who boots up last), as using 75%-85% of it's total allocated ram(Windows only reports 1gb used), while the other seems to only use the amount of ram that windows reports. The qemu-agent is also running and reporting to proxmox. These vm's are clones, so there shouldn't be any difference in configuration
https://i.imgur.com/jkSFwgI.png
https://i.imgur.com/QuHWKRF.png
Seems like that just randomly, it'll appear as if the Balloon driver on the guest just isn't working. Usually rebooting the host or guests a few times fixes this for a few minutes, or will switch which VM is effected by this issue.
The Proxmox host has a total of 64gb of memory, and the host seems to be sitting at just over 50% memory utilization: https://i.imgur.com/L6ndRiZ.png
I've also tuned my zfs to not use as much memory as the default configuration: https://i.imgur.com/dE1Hci3.png
I've accounted for ZFS caching as well as Proxmox overhead. The KVM processes seem to report 25% usage for the problem VM:
https://i.imgur.com/SsjB3si.png
Anyone know why the KVM process for each of these vm's hogs so much memory? I assume it's because of Windows behavior with memory. Will the balloon driver free/reduce memory for these KVM processes as it's needed elseware? I don't intend to have these machines use the full 16gb, however I would like to overcommit since these are development machines. Not sure how this would effect that.
I have two Windows Server 2019 VM's running on this node, each set to have a maximum of 16gb of memory with a 2gb minimum. The virtio balloon drivers are installed and the balloon service is running. Proxmox seems to show one of the VM's (Its random, usually the one who boots up last), as using 75%-85% of it's total allocated ram(Windows only reports 1gb used), while the other seems to only use the amount of ram that windows reports. The qemu-agent is also running and reporting to proxmox. These vm's are clones, so there shouldn't be any difference in configuration
https://i.imgur.com/jkSFwgI.png
https://i.imgur.com/QuHWKRF.png
Seems like that just randomly, it'll appear as if the Balloon driver on the guest just isn't working. Usually rebooting the host or guests a few times fixes this for a few minutes, or will switch which VM is effected by this issue.
The Proxmox host has a total of 64gb of memory, and the host seems to be sitting at just over 50% memory utilization: https://i.imgur.com/L6ndRiZ.png
I've also tuned my zfs to not use as much memory as the default configuration: https://i.imgur.com/dE1Hci3.png
I've accounted for ZFS caching as well as Proxmox overhead. The KVM processes seem to report 25% usage for the problem VM:
https://i.imgur.com/SsjB3si.png
Anyone know why the KVM process for each of these vm's hogs so much memory? I assume it's because of Windows behavior with memory. Will the balloon driver free/reduce memory for these KVM processes as it's needed elseware? I don't intend to have these machines use the full 16gb, however I would like to overcommit since these are development machines. Not sure how this would effect that.
Last edited:
