cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-856) [DOC] Document CPU and memory overcommit functionality.
Date Thu, 01 Aug 2013 10:27:51 GMT

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

Bharat Kumar commented on CLOUDSTACK-856:
-----------------------------------------

please  add the following to the doc as a Note.

Unlike Xenserver and VMware, KVM dose not have the capability to mange the memory allocation
to VMs dynamically.

Cloudstack sets the min and max values of memory that a vm can use. The hypervisor  adjusts
the memory within the set limits based on the memory contention. 

                
> [DOC] Document CPU and memory overcommit functionality. 
> --------------------------------------------------------
>
>                 Key: CLOUDSTACK-856
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-856
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>            Reporter: David Nalley
>            Assignee: Jessica Tomechak
>             Fix For: 4.2.0
>
>
> Document CPU and memory overcommit functionality 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message