Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 7 Nov 2013 13:09:18 +0000 (UTC)
From: "Bharat Kumar (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12677988.1383829709909.34339.1383829758709@arcas>
In-Reply-To: <JIRA.12677988.1383829709909@arcas>
References: <JIRA.12677988.1383829709909@arcas>
Subject: [jira] [Created] (CLOUDSTACK-5077) this should be the behavior even
 when overcommitting. in case of vmware.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Bharat Kumar created CLOUDSTACK-5077:
----------------------------------------

             Summary: 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.)
            Reporter: Bharat Kumar
            Assignee: Bharat Kumar


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)