[
https://issues.apache.org/jira/browse/CLOUDSTACK-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727580#comment-14727580
]
ASF GitHub Bot commented on CLOUDSTACK-8678:
--------------------------------------------
Github user kmccormick commented on the pull request:
https://github.com/apache/cloudstack/pull/766#issuecomment-137155599
Regarding the upgrade scenario, I believe that this would not affect any
running VMs. Can anyone confirm? Besides just running VMs, it is still a
potential problem for an installation that is already near capacity, as the
upgrade would remove a little bit of capacity. For both issues, I think a
mention in the release notes would be sufficient. To keep the old behavior,
admins just need to add host.reserved.ram.mb=0 to their agent.properties file.
CPU I don't think is an issue, as memory is typically the limiting factor
in virtualization. If the CPU gets overly taxed, things slow down, where if all
the memory gets used up, VMs or other processes get killed.
> 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)
