[
https://issues.apache.org/jira/browse/CLOUDSTACK-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643612#comment-14643612
]
Josh Harshman commented on CLOUDSTACK-8678:
-------------------------------------------
Daan,
Thanks for the quick reply. It does kinda sound like a user question :P. But I
wouldn't have submitted an issue unless I had already explored other avenues.
Cloudstack doesn't appear to like setting the overprovisioning factor to any
value less than one (at least through the GUI). Unless you can force it
through the cli?
Error Message: "mem.overprovisioning.factor should be greater than or equal to
1"
> OOM Kills Guests
> ----------------
>
> Key: CLOUDSTACK-8678
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8678
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, KVM
> Affects Versions: 4.4.2
> Environment: Intel Xeon Quad Core CPU L5520 @ 2.27GHz
> 98 GB RAM
> Ubuntu 14.04
> Running Cloustack 4.4.2
> Reporter: Josh Harshman
> Priority: Critical
>
> 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.
> Thank you,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
