[
https://issues.apache.org/jira/browse/CLOUDSTACK-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701945#comment-14701945
]
Daan Hoogland commented on CLOUDSTACK-8678:
-------------------------------------------
Josh, I have been thinking that having the agent report back available memory
in a way that takes into account dom0 is better. I would like this to be done
in a hypervisor agnostic or at least - transparent way. I think that making use
of the host.reserved.mem.mb on the agent to make sure the right amount is
reported, is the easiest. I see from your last post that you have an other
idea. Please formulate it to start a discuss thread on dev@ including a
proposal to solve it this (or my) way.
> 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
> Assignee: Daan Hoogland
> 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)
