Proxmox 4.4.5 kernel: Out of memory: Kill process 8543 (kvm) score or sacrifice child

whitewater

Member
Nov 26, 2012
107
0
16
france
It must not be for nothing that they return back ;)
For me, no problem with the kernel test 4.4.35-2-pve and the 4.4.21-71 since more than one day.
So it was that.
 

reetp

Active Member
Aug 19, 2013
49
3
28
Backup with new settings as above with same kernel worked for me last night
 

Marcus Dewald

Member
Jan 6, 2017
3
0
21
31
Thanks for the Feedback Jorge! I've just installed the test kernel too. Crossing fingers that Proxmox now stops to (blood)sacrifice my Windows VM.
 

fireon

Famous Member
Oct 25, 2010
3,850
314
103
40
Austria/Graz
iteas.at
Upgraded 2 Cluster last night. Same problem, 4 VMs crashed. I test the new kernel too. Must i set the settings in systctl too?
 

ozgurerdogan

Active Member
May 2, 2010
518
4
38
Bursa, Turkey, Turkey
I have edited sysctlt and it has been fine for 5-6 days. But some other new nodes started same issue. I will probably need to edit all of nodes. But note sure if it is good fix.
 

Marcus Dewald

Member
Jan 6, 2017
3
0
21
31
Thanks for the Feedback Jorge! I've just installed the test kernel too. Crossing fingers that Proxmox now stops to (blood)sacrifice my Windows VM.
In reply of myself and all whom may be concerned. The Test Kernel fixed my issue, VM is running since then.
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,251
1,330
164

maxprox

Well-Known Member
Aug 23, 2011
401
32
48
Germany - Nordhessen
www.fair-comp.de
  • Like
Reactions: Dan Nicolae

c0urier

Member
Aug 29, 2011
20
1
23
Sweden
I had the same issue with kernel : 4.4.35-1-pve and it was resolved by upgrading to : 4.4.35-2-pve

Tried with a quite large backup afterwards:
INFO: transferred 3543348 MB in 17702 seconds (200 MB/s)
INFO: archive file size: 2836.98GB
INFO: Finished Backup of VM 100 (04:55:06)
INFO: Backup job finished successfully
TASK OK
 

Dan Nicolae

Active Member
Apr 27, 2016
77
3
28
42
Problem on our side was with the CEPH nodes. From time to time, OSD daemons where killed and CEPH marked them down. In one morning, half of our OSD was down, cluster was rebuilding, most of the VM partitions where corupted, some of them impossible to recover, data loss, absolutely horror. After the kernel update everything looks ok. Update took place on 3 january, from that time (7 days), a lot of pain... What a mess.
 
Last edited:

snpz

Active Member
Mar 18, 2013
33
4
28
Hi there!

We have the same issue on our server cluster.
Fabian - is this bug fixed in pve-kernel-4.4.35-2-pve that is available using dist-upgrade or it is better to install the version you built?
Thanks in advance!
 

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 your own in 60 seconds.

Buy now!