# Hardware or VM for one controller **URL:** \ **Category:** Product Support\ **Created:** [November 8, 2016, 8:19pm UTC](https://forum.opennebula.io/t/hardware-or-vm-for-one-controller/3249 "2016-11-08T20:19:23Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![feldsam](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/feldsam/32/4441_2.png) [@feldsam](https://forum.opennebula.io/u/feldsam)\ **Post date:** [November 9, 2016, 7:28am UTC](https://forum.opennebula.io/t/hardware-or-vm-for-one-controller/3249/2 "2016-11-09T07:28:45Z")
Hello, look at my replies in existing topic > [@Running opennebula as VM and import it afterwards in itself](https://forum.opennebula.io/t/running-opennebula-as-vm-and-import-it-afterwards-in-itself/1057/8): > > What is benefit of this? I have Opennebula in VM hsoted on cluster, but I manage that VM by pacemaker. I also plan to do HA with two VM and configure pacemaker placement to have each VM on another host. When I need migrate frontend to other host, I do it by pacemaker. Also, when I need to put some cluster node to standby, it automatically migrate running opennebula VM to other suitable host and only then it stops other resources like mouted storage, dlm etc… > [@Running opennebula as VM and import it afterwards in itself](https://forum.opennebula.io/t/running-opennebula-as-vm-and-import-it-afterwards-in-itself/1057/10): > > Hi, you are right. I don’t see any drawback, it is working good. Also you can manage resource inside VMs by pacemaker remote. In opennebula itself, I can see VMs on Wild tab in Host detail. Thats all. When I need to do maintanace, I just put node to standby like before. Pacemaker automatically migrate running VM to other node. I think that is better that self-managing openenbula VMs by opennebula. Actually, I have just one opennebula VM, but I planning to do MariaDB cluster from three VMs an… --- _[View the full topic](https://forum.opennebula.io/t/hardware-or-vm-for-one-controller/3249)._