[
https://issues.apache.org/jira/browse/CLOUDSTACK-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825043#comment-13825043
]
Nitin Mehta commented on CLOUDSTACK-5077:
-----------------------------------------
The behavior is now restored to as it was in 3.0.x
If vmware.mem.reserve = true
Reserve memory = (service_offering / memory over provisioning factor)
Else
Reserve memory = don’t reserve
Same for cpu
> this should be the behavior even when overcommitting. in case of vmware.
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5077
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5077
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Reporter: Bharat Kumar
> Assignee: Bharat Kumar
> Fix For: 4.2.1
>
>
> do not reserve memory on overcommit if vmware.reserve.cpu and
> vmware.reserve.mem are set to false.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
