I could install the frontend without any issues. But during installation in the node (step 2.2 in the link above), I encounter following issue. Looks like there is an issue with messagebus and nfs service. See error below.
root@localhost# systemctl enable messagebus.service Failed to issue method call: No such file or directory
root@localhost# systemctl enable libvirtd.service
root@localhost# systemctl start libvirtd.service
root@localhost# systemctl enable nfs.service Failed to issue method call: No such file or directory
Please let me know has anyone faced this problem and solved it. Is the combination of CentOS and Opennebula 4.12.1 causing the issue. Please advice.
My initial idea was to create 2 VMs (one frontend and one node) but I wanted to do that after single host installation.
Enabling dbus also failed as shown below. I am basic linux user. I download centos 7 DVD from official website and using it to install opennebula. I am tempted to tru openSuse.
[admin@oneserver ~]$ sudo systemctl enable dbus.service
[sudo] password for admin:
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
A unit may be statically enabled by being symlinked from another unit’s
.wants/ or .requires/ directory.
A unit’s purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, …).
Inspite of the errors thrown when enabling messagebus.service and nfs.service, I could setup Opennebula frontend and host node. My setup is as follows:
On my windows laptop, I installed virtualbox and created 2 VMs. One VM for Frontend, second VM for Node. I managed to setup a virtual network and created image, templates. I am facing problem in the last step of the tutorial, which is instantiating a VM from the template.
I am getting the following error: Domain requires KVM, but it is not available. Check that virtualisation is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
do you have enable the virtualization support in your VM? I don’t use Virtualbox but you have to enable vmx/svm flags inside your VM. To check if you have this flags, cat /proc/cpuinfo
Thanks for your comments which led to the following conclusions.
Virtual box doesn’t support nested virtualization (VM within VM) and I cannot set vmx/svm flag in a VM running in VirtualBox even f the host supports it. See these threads