[ https://issues.apache.org/jira/browse/CLOUDSTACK-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662882#comment-14662882 ]
Daan Hoogland commented on CLOUDSTACK-8678: ------------------------------------------- If the host.reserved.mem.mb is there and ignored I would call that a half implemented feature, also known as bug. By your description it sound like this is exactly the functionality we'd want, as you said. The host capacity calculation would have to take this setting into account. I see no added value of it being sent by the agent to the management server unless it can somehow dynamically change on a per host basis. If this is the case it must be stored as well. agreed? > 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)