[
https://issues.apache.org/jira/browse/CLOUDSTACK-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884898#comment-13884898
]
ASF subversion and git services commented on CLOUDSTACK-5968:
-------------------------------------------------------------
Commit 7ca27f6cc69d07772f77b0ff53906894f6ba527b in branch refs/heads/4.3 from
[~mlsorensen]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7ca27f6 ]
CLOUDSTACK-5968 create vm.memballoon.disable agent parameter
(cherry picked from commit e624632dfd532ba2885a8e7dffcb40d1436d02c1)
Signed-off-by: Animesh Chaturvedi <[email protected]>
> 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)
