# Running opennebula as VM and import it afterwards in itself

**URL:** <https://forum.opennebula.io/t/running-opennebula-as-vm-and-import-it-afterwards-in-itself/1057>\
**Category:** Product Support\
**Created:** [July 31, 2015, 1:13pm UTC](https://forum.opennebula.io/t/running-opennebula-as-vm-and-import-it-afterwards-in-itself/1057 "2015-07-31T13:13:28Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![gandalf](https://avatars.discourse-cdn.com/v4/letter/g/59ef9b/32.png) [@gandalf](https://forum.opennebula.io/u/gandalf)\
**Post date:** [September 21, 2016, 7:10am UTC](https://forum.opennebula.io/t/running-opennebula-as-vm-and-import-it-afterwards-in-itself/1057/9 "2016-09-21T07:10:28Z")

</div>

I would like to do something similiar  
What i would like to achieve is a fully virtualized cloud infrastructure

If i understood properly, you manually created two VM for opennebula-frontend on you “compute” nodes.  
These two vm are managed by pacemaker for scheduling and migrations

After that, from the newly installed opennebula you added the same “compute” node as hosts to be managed by opennebula

In this case you share the same hosts between the opennebula VM and VMs created/managed by opennebula itself

Right?  
Any drawbacks? I would like to avoid using dedicated hosts only for opennebula frontend

---

_[View the full topic](https://forum.opennebula.io/t/running-opennebula-as-vm-and-import-it-afterwards-in-itself/1057)._