# Resize memory, cpu on the fly

**URL:** <https://forum.opennebula.io/t/resize-memory-cpu-on-the-fly/5528>\
**Category:** Product Support\
**Created:** [January 7, 2018, 9:53pm UTC](https://forum.opennebula.io/t/resize-memory-cpu-on-the-fly/5528 "2018-01-07T21:53:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amit\_Kumar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/amit_kumar/32/7867_2.png) [@Amit\_Kumar](https://forum.opennebula.io/u/Amit_Kumar)\
**Post date:** [January 7, 2018, 9:53pm UTC](https://forum.opennebula.io/t/resize-memory-cpu-on-the-fly/5528/1 "2018-01-07T21:53:07Z")

</div>

Please, describe the problem here and provide additional information below (if applicable) …

— How can we modify cpu, memory size on the fly and automate it, in case of any threshhold breach.

**Versions of the related components and OS (frontend, hypervisors, VMs):** OpenNebula 5.4, KVM

**Steps to reproduce:**

**Current results:**

In current version 5.4, It seems not possible, while VM is running. while KVM native and VMware support this feature

**Expected results:**

memory, cpu and disck resize can be done on fly