# CPU usage over "overcommitment" value

**URL:** <https://forum.opennebula.io/t/cpu-usage-over-overcommitment-value/13444>\
**Category:** Product Support\
**Created:** [January 8, 2025, 11:52am UTC](https://forum.opennebula.io/t/cpu-usage-over-overcommitment-value/13444 "2025-01-08T11:52:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Ruiz\_Molina](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@Daniel\_Ruiz\_Molina](https://forum.opennebula.io/u/Daniel_Ruiz_Molina)\
**Post date:** [January 8, 2025, 11:52am UTC](https://forum.opennebula.io/t/cpu-usage-over-overcommitment-value/13444/1 "2025-01-08T11:52:18Z")

</div>

Hello,

Some days ago, one of my three OpenNebula servers exceeded the value of “overcommitment” in host configuration. As you could see in these two screenshots, my host was at 106% of assigned CPUs, but host was at configured to share its 104 cores, but not more than them:

 ![over CPU usage](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/2/278c8948c1676a8cd716b530888d397566bcf375.png)

 ![host details](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/4/4f012913267341a5ee1fe248f330983fecd89b2c.png)

So my question is if it is a normal behavior of “overcommitment” parameter. My OpenNebula version is 6.8.0-1 and my servers are running Ubuntu Server 22.04.3.

Thanks.

---

<div class="post-metadata">

**Author:** ![atodorov\_storpool](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/atodorov_storpool/32/5327_2.png) [@atodorov\_storpool](https://forum.opennebula.io/u/atodorov_storpool)\
**Post date:** [January 8, 2025, 1:28pm UTC](https://forum.opennebula.io/t/cpu-usage-over-overcommitment-value/13444/2 "2025-01-08T13:28:43Z")

</div>

Hi,

Are all VMs deployed to the host via the OpenNebula scheduler? Wondering because a VM instantiated or migrated to the host by an Administrator could override the limits (oneadmin for example has no limits…)

BR,  
Anton Todorov

---

<div class="post-metadata">

**Author:** ![Daniel\_Ruiz\_Molina](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@Daniel\_Ruiz\_Molina](https://forum.opennebula.io/u/Daniel_Ruiz_Molina)\
**Post date:** [January 8, 2025, 1:48pm UTC](https://forum.opennebula.io/t/cpu-usage-over-overcommitment-value/13444/3 "2025-01-08T13:48:22Z")

</div>

Hi @atodorov_storpool

Possibly, in that moment of 106%, some VMs were created using API as a “normal” users (not oneadmin) and not from Sunstone.

Could be that the problem? API? In that case (waiting for your confirmation), is there any way to disable that behavior? How could I force to avoid overcommitment?

Thanks.