Perhaps memory overcommit is set to greater than 1? What is your cut off
threshold? it usually set to 85%, which means you always leave 15% of
memory in reserve.
Also, is your mem baloon driver in guest VMs disabled?
As a test, create some VMs that are slightly under your cut off
threshold, i.e. if you total is 256GB of RAM on the host and usable is
217GB (assumed 85%), create 4 VMs with 50GB RAM.
Next, install mprime or another memory load generator to allocate all of
its memory and see if OOM re-occurs on hypervisor.
Regards
ilya
On 7/7/15 12:53 PM, Tony Fica wrote:
We have several KVM nodes running Cloudstack 4.4.2. Sometimes an
instance with X amount of RAM provisioned will be started on a host
that has X+a small amount of RAM free. The kernel OOM killer will
eventually kill off the instance. Has anyone else seen this behavior,
is there a way to reserve RAM for use by the host instead of by
Cloudstack? Looking at the numbers in the database and the logs,
Cloudstack is trying to use 100% of the RAM on the host.
Any thoughts would be appreciated.
Thanks,
Tony Fica
