prashant kumar mishra created CLOUDSTACK-3415:
-------------------------------------------------
Summary: Guest os memory is not getting dynamically adjusted
incase of overcommit
Key: CLOUDSTACK-3415
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3415
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: master stable branch ;vmware esxi-5.1
Reporter: prashant kumar mishra
Priority: Critical
Fix For: 4.2.0
In case of contention existing vms memory should automatically get reduced
(should be between reserved and max) so that new vms can accommodate on
host.But i did not see this behavior on vmware.
Guest OS always shows max memory even in case of contention .
Steps to reproduce
---------------------------
1-Preapre a CS setup with vmware esxi5.1
1-Set memory overcommit to 2
3-Create a service offering of1 (cpu=500MGZ,Memory=4096MB)
4-Deploy vms using service offering of1 till no memory left on hypervisor
5-run cat /proc/meminfo on each guest
Actual
----------
1-Step 5 shows each guest is having 4096MB
2-Total guest os memory(at guest OS level) >what physically available on host
Expected
--------------
1-VMs memory should dynamically get adjusted (<4096) in order to accommodate
new vms on host
2-Total guest os memory (at guest OS level) <=what physically available on host
--
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
