[
https://issues.apache.org/jira/browse/CLOUDSTACK-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823134#comment-13823134
]
Nitin Mehta commented on CLOUDSTACK-5077:
-----------------------------------------
Bharat - I am assuming that this is resolved. I changed the fix version as
4.2.1 as well. Please also provide a better description as well. It sounds very
confusing to me.
> 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)
