# VM in POWEROFF and releasing CPU/RAM hardware resources

**URL:** <https://forum.opennebula.io/t/vm-in-poweroff-and-releasing-cpu-ram-hardware-resources/2808>\
**Category:** Product Support\
**Created:** [August 23, 2016, 11:00am UTC](https://forum.opennebula.io/t/vm-in-poweroff-and-releasing-cpu-ram-hardware-resources/2808 "2016-08-23T11:00:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![valerio\_schiavoni](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/valerio_schiavoni/32/4175_2.png) [@valerio\_schiavoni](https://forum.opennebula.io/u/valerio_schiavoni)\
**Post date:** [August 23, 2016, 11:00am UTC](https://forum.opennebula.io/t/vm-in-poweroff-and-releasing-cpu-ram-hardware-resources/2808/1 "2016-08-23T11:00:44Z")

</div>

Hello,  
when a machine is in POWEROFF state, what happens to the CPU cores and RAM of the host where the VM was running ?  
Those do not seem to be released for new VMs (as I was expecting).  
What is the correct state that I should use so that those hardware resources are released ?

I’m using ON 4.14.2.

Thanks.

---

<div class="post-metadata">

**Author:** ![DaD](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/dad/32/8466_2.png) [@DaD](https://forum.opennebula.io/u/DaD)\
**Post date:** [August 23, 2016, 11:46am UTC](https://forum.opennebula.io/t/vm-in-poweroff-and-releasing-cpu-ram-hardware-resources/2808/2 "2016-08-23T11:46:33Z")

</div>

valerio\_schiavoni [opennebula@discoursemail.com](mailto:opennebula@discoursemail.com) writes:

> Hello,

Hello,

> when a machine is in POWEROFF state, what happens to the CPU cores and RAM of the host where the VM was running ?  
> Those do not seem to be released for new VMs (as I was expecting).  
> What is the correct state that I should use so that those hardware resources are released ?
> 
> I’m using ON 4.14.2.

I thought resource management was better described in the  
documentation[1][2].

Some actions let the images on the hypervisor and keep resources  
allocated on it.

This means that the KVM process is stopped, the CPU and RAM are  
physically freed from the hypervisor but OpenNebula keeps them allocated  
for the “resume”, that’s the reason about the difference between “USED  
MEM (REAL)”/“USED MEM (ALLOCATED)” and “USED CPU (REAL)”/“USED CPU (ALLOCATED)”.

If you want to unallocate the resources from the hypervisor, you can  
“stop” or “undeploy” the VM.

Regards.

Footnotes:  
[1] [Managing Virtual Machines Instances — OpenNebula 5.0.2 documentation](http://docs.opennebula.org/5.0/operation/vm_management/vm_instances.html)

[2] [onevm(1) - manages OpenNebula virtual machines](http://docs.opennebula.org/doc/4.14/cli/onevm.1.html)

Daniel Dehennin  
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF  
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF