Proxmox and memory: Difference between revisions
From DWIKI
| Line 29: | Line 29: | ||
Out of memory: Kill process 10429 (java) score 126 or sacrifice child | Out of memory: Kill process 10429 (java) score 126 or sacrifice child | ||
When pve hosts runs low on memory (80% used) it starts reclaiming memory from guests using ballooning. | |||
See [https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_memory QM Memory]. | |||
Make sure to set 'Minimum memory' to a value high enough to prevent processes getting shot by OOM killer. | |||
== a used vhost backend has no free memory slots left == | == a used vhost backend has no free memory slots left == | ||
Revision as of 09:50, 24 August 2023
Docs
Clues
pvesh
pvesh get /cluster/resources
Get current configuration of VM 105
pvesh get /nodes/nuc/qemu/105/status/current
Now to get maxmem given to VM 105
pvesh get /nodes/nuc/qemu/105/status/current --output-format json | jq '.maxmem'
Get memory usage
pvesh get /cluster/resources --output-format json |jq '.[] | select(.id=="qemu/105") | .mem'
FAQ
virtio_balloon virtio0: Out of puff! Can't get 1 pages
Out of memory: Kill process 10429 (java) score 126 or sacrifice child
When pve hosts runs low on memory (80% used) it starts reclaiming memory from guests using ballooning. See QM Memory. Make sure to set 'Minimum memory' to a value high enough to prevent processes getting shot by OOM killer.
a used vhost backend has no free memory slots left
https://forum.proxmox.com/threads/hotplug-memory-limits-total-memory-to-44gb.30991/#post-154914
echo "options vhost max_mem_regions=509" >> /etc/modprobe.d/vhost.conf
