I had the same problems regarding KVMs not running and I thought that they were gone, but I had again some problems.
Yesterday I rebooted after an upgrade and now I am running VE 4.4-12 / kernel 4.4.35-2-pve, hoping that no stopped KVMs will occure again. I am using the following cronscript every minute to check if all KVMs are running. If not, the script starts the KVM. Safed me some customers calling. #!/bin/bash ### #If KVM machines are stopped, they will be started ### for VM in `/usr/sbin/qm list | grep stopped | awk '{print $1}'`; do echo `date`" VM $VM is offline, starting..." >> /var/log/check-kvm.log /usr/sbin/qm start $VM done Am 04.02.2017 um 10:44 schrieb Michele Bonera: > Hi. > > I have an issue with OOM Killer (Proxmox 4.4-5 - Kernel 4.4.35-1-pve) > on my infrastructure: even if there is a lot of free memory (15GB used > over 32GB available), OOM Killer is still killing my VM processes. > > This morning I had 3 over 6 VM powered down because OOM Killer decided > to kill the related processes even if there were a lot of free memory. > > total used free shared buffers cached > Mem: 32725572 32286280 439292 196428 3772084 18648708 > -/+: 9865488 22860084 > Swap: 1499124 33736 1465388 > > This problem is related to all the server I have in the infrastructure > (some are Supermicro, some are Dell) and occur randomly after some > days the host is rebooted. > > I already instruct OOM Killer not to kill VM Processes, but I'm afraid > it could kill processes related to the infrastructure. > > Is there someone with the same issue? > > Bye, -- Datenfalke - Dipl. Inf. Falco Kleinschmidt Adresse: Dinnendahlstr. 8 - 45136 Essen Steuer-Nr: DE248267798 Telefon: +49-(0)201-6124650 Fax: +49-(0)201-6124651 Email: f...@datenfalke.de WWW: http://www.datenfalke.de _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user