Hello,
I was using my proxmox node and found my pfsense VM to be suspiciously slow / unresponsive, when I decided to look in PVE's syslog and saw these:
Jun 3 22:58:08 proxmox pvestatd[3603]: VM 100 qmp command failed - VM 100 qmp command 'balloon' failed - got timeout
Jun 3 22:58:08 proxmox pvestatd[3603]: WARNING: VM 100 qmp command 'balloon' failed - got timeout
Jun 3 22:58:08 proxmox pvestatd[3603]: status update time (6.036 seconds)
Jun 3 22:58:25 proxmox pvestatd[3603]: WARNING: unable to connect to VM 101 socket - timeout after 31 retries
Jun 3 22:58:28 proxmox pvestatd[3603]: WARNING: unable to connect to VM 100 socket - timeout after 31 retries
Jun 3 22:58:28 proxmox pvestatd[3603]: status update time (6.049 seconds)
Jun 3 22:58:35 proxmox pvestatd[3603]: WARNING: unable to connect to VM 102 socket - timeout after 31 retries
I recently activated memory ballooning on VM 100 as per instructions of pfsense wiki:
Add VirtIO Memory Ballooning
Memory ballooning allows you to have your guest dynamically change it's memory usage by evicting unused memory during runtime. Most useful for environments with large memory over-commit requirements.
Edit /boot/loader.conf.local (see above) and add:
virtio_balloon_load="YES"
Should I be worried??
I was using my proxmox node and found my pfsense VM to be suspiciously slow / unresponsive, when I decided to look in PVE's syslog and saw these:
Jun 3 22:58:08 proxmox pvestatd[3603]: VM 100 qmp command failed - VM 100 qmp command 'balloon' failed - got timeout
Jun 3 22:58:08 proxmox pvestatd[3603]: WARNING: VM 100 qmp command 'balloon' failed - got timeout
Jun 3 22:58:08 proxmox pvestatd[3603]: status update time (6.036 seconds)
Jun 3 22:58:25 proxmox pvestatd[3603]: WARNING: unable to connect to VM 101 socket - timeout after 31 retries
Jun 3 22:58:28 proxmox pvestatd[3603]: WARNING: unable to connect to VM 100 socket - timeout after 31 retries
Jun 3 22:58:28 proxmox pvestatd[3603]: status update time (6.049 seconds)
Jun 3 22:58:35 proxmox pvestatd[3603]: WARNING: unable to connect to VM 102 socket - timeout after 31 retries
I recently activated memory ballooning on VM 100 as per instructions of pfsense wiki:
Quote:
Add VirtIO Memory Ballooning
Memory ballooning allows you to have your guest dynamically change it's memory usage by evicting unused memory during runtime. Most useful for environments with large memory over-commit requirements.
Edit /boot/loader.conf.local (see above) and add:
virtio_balloon_load="YES"
