Kvm stops with this?

[ozgurerdogan]

Feb 09 00:24:42 s5 kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/qemu.slice/124.scope,task=kvm,pid=15247,uid=0
Feb 09 00:24:42 s5 kernel: Out of memory: Killed process 15247 (kvm) total-vm:9604984kB, anon-rss:8819368kB, file-rss:1964kB, shmem-rss:0kB
Feb 09 00:24:43 s5 kernel: oom_reaper: reaped process 15247 (kvm), now anon-rss:0kB, file-rss:36kB, shmem-rss:0kB
Feb 09 00:24:47 s5 kernel: vmbr0: port 7(tap124i0) entered disabled state
Feb 09 00:24:47 s5 kernel: vmbr0: port 7(tap124i0) entered disabled state
Feb 09 00:24:47 s5 systemd[1]: 124.scope: Succeeded.
Feb 09 00:24:50 s5 qmeventd[1861]: Starting cleanup for 124
Feb 09 00:24:50 s5 qmeventd[1861]: Finished cleanup for 124

Then kvm is in stopped state. Any idea?

 

[spirit]

too much memory usage on your proxmox host, then linux kernel have killed a kvm process to free memory space.

 

[ozgurerdogan]

This happened again. But there nearly %30 40 free memory on node. I need to disable oomkiller. Is it somehow possible? Also this is not happening on same hardware of other nodes even with heavier load.

 

[Amin Vakil]

Does it happen when the vm is booting?

You may wanna check this: https://bugs.archlinux.org/task/66688

 

[BobhWasatch]

There may be 30 or 40% free before and after the event. But OOM-killer doesn't fire without a reason.