VM killed

Loic92

New Member
Oct 23, 2022
8
1
3
Paris
Hello,
one of my VM has been killed by the proxmox kernel.
Enclosed the log I found.
Is it an hardware issue?
Thanks.
CPU(s) 12 x Intel(R) Xeon(R) CPU D-1531 @ 2.20GHz (1 Socket)
Kernel Version Linux 5.15.60-2-pve #1 SMP PVE 5.15.60-2 (Tue, 04 Oct 2022 16:52:28 +0200)
PVE Manager Version pve-manager/7.2-11/b76d3178
 

Attachments

  • proxmox-kernel.log
    18.1 KB · Views: 13
Search your log for "OOM" or "oom". PVE is killing your VMs because it is running out of memory (=oom) and need to kill some processes to not crash, so it usually kills the biggest or least important processes which are the kvm processes that run your VMs.
Don't try to allocate more RAM your server actually got. RAM overprovisioning is always risky, even when using ballooning.

PVE needs some RAM, ZFS needs RAM, filesystem caching of PVE needs RAM, all VM cache modes like "writeback" will need RAM, all VMs might need more RAM than you actually assigned them because KVM also got overhead. Then there is RAM fragmentation. So buy more RAM or assign less RAM to your VMs.
 
Last edited:
Oct 23 02:03:53 proxmox03 kernel: [526080.349971] CPU 2/KVM invoked oom-killer: gfp_mask=0x1100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0

To me this reads as if the system ran out of memory.
Have you limited ZFS arc usage?
How much memory is in the system and how much memory is assigned to VMs?
 
  • Like
Reactions: Loic92

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!