cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-5968) Allow disabling balloon for overcommit in KVM
Date Tue, 28 Jan 2014 17:45:40 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884357#comment-13884357
] 

ASF subversion and git services commented on CLOUDSTACK-5968:
-------------------------------------------------------------

Commit 1530c162e58abd8e572a89d2a2706de00bd49e26 in branch refs/heads/master from [~mlsorensen]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1530c16 ]

CLOUDSTACK-5968 create vm.memballoon.disable agent parameter


> 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)

Mime
View raw message