Bug #5420

CPU Overcommitment on ESXi Hosts

Added by Jose Miguel Casado almost 4 years ago. Updated over 3 years ago.

Status:PendingStart date:09/29/2017
Priority:HighDue date:
Assignee:Jaime Melis% Done:


Target version:Release 5.4.4
Resolution: Pull request:
Affected Versions:OpenNebula 5.4


Real CPU (actuallyutilized) is usually much lower than Allocated CPU.

On previous OpenNebula versions we had configured via Sunstone CPU OverCommitment to allow the creation of more VMs than the Real amount of CPU could allow based on the calculations OpenNebula does.

On version 5.4.1, the maximum amount for CPU overcommitment via Sunstone is much lower than the amount we actually have, inherited from ONE 5.2.1 and we need to increase this CPU Reservation amount to allow the creation of more VMS (If you reach the alocated CPU limit, OpenNebula does not allow the creation of more VMs).

Please. don't limit CPU Overcommitment, I think is better that you suggest a limit but allow the admins and architects decide if their environment can support this overcommitment. For instance, in our environment, we have a Real CPU usage of 2% and 5% in both ESXi Clusters.


#1 Updated by Ruben S. Montero over 3 years ago

  • Target version changed from Release 5.4.2 to Release 5.4.3

#2 Updated by Tino Vázquez over 3 years ago

  • Target version changed from Release 5.4.3 to Release 5.4.4

Also available in: Atom PDF