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 | ||
PVE host ran low on memory, and started reclaiming memory from ballooning drivers. | |||
See [https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_memory QM Memory]. | See [https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_memory QM Memory]. | ||
To prevent this, make sure to set 'Minimum memory' high enough. | |||
== a used vhost backend has no free memory slots left == | == a used vhost backend has no free memory slots left == | ||
Revision as of 12:00, 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
PVE host ran low on memory, and started reclaiming memory from ballooning drivers. See QM Memory. To prevent this, make sure to set 'Minimum memory' high enough.
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
