[
https://issues.apache.org/jira/browse/CLOUDSTACK-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884419#comment-13884419
]
ASF subversion and git services commented on CLOUDSTACK-5968:
-------------------------------------------------------------
Commit 05189361b79e9ebd33486cf8d564a5e85a6747d8 in branch refs/heads/master
from [~mlsorensen]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0518936 ]
CLOUDSTACK-5968 last patch fixes setting low currentMemory during
overprovision, this one explicitly tells libvirt we dont want a
balloon device (won't use it anyway, and will just suck up a percent
of vm memory)
> 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)
