You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Marcus Sorensen (JIRA)" <ji...@apache.org> on 2014/01/28 20:15:41 UTC

[jira] [Resolved] (CLOUDSTACK-5968) Allow disabling balloon for overcommit in KVM

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Sorensen resolved CLOUDSTACK-5968.
-----------------------------------------

    Resolution: Fixed

> Allow disabling balloon for overcommit in KVM
> ---------------------------------------------
>
>                 Key: CLOUDSTACK-5968
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5968
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.4.0
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: 4.4.0
>
>
> Current memory overcommit functionality doesn't allow overcommit without using virtio-balloon to dynamically squeeze vms. It also requires an admin-provided daemon to monitor and adjust currentMemory setting on vms. Without this, overcommit simply divides the service offering ram by overcommit value and that's all the VM sees. Allow for disabling virtio-balloon via agent.properties so that memory overcommit will show guests their full service offering RAM, if desired.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)