Page History

...

xenserver
The DMC (Dynamic Memory Control)capability of the hypervisor should be enabled. only xenserver Advanced and above versions have this feature. In case of xenserver we cannot support an overcommit factor greater than 4. This is because of a hypervisor constraint.

VMware & KVM.
The memory ballooning is supported by default.

KVM
kvm dose not support automatic adjustment of the guest OS memory dynamically.

Behavior when overcommit is changed while there are VMs running in the cluster.
*In this case all the VMs prior to the overcomit change will continue to run with the same settings. Only the
newly deployed VMs will have the new setting based on the new overcommit value.
*On overcommit change we scale the used and reserved capacities based on the new overcommit values. This happens when
the capacity checker runs. The time interval between consequent runs can be changed by changing the global parameter capacity.check.period.

• The capacity as seen by the cloudstack will not be correct until the capacity recalculate happens.

As of now cloudstack dose not check for any perquisites. It is the admin's responsibility to provision accordingly.

Thing To do

• Trigger the capacity recalculate when the overcommit is changed. No need to wait until capacity checker runs.
• Create action event on overcommit change.
• Create action event when capacity recalculate is complete.