“Ttylinux - KVM”-VM deployment fails after first installation

Community Support
1

Hello,

i just finished installing my OpenNebula Frontend plus a KVM-Hypervisor. Now im trying to deploy my first VM by using the “Ttylinux - KVM” as described in the documentation but i ran into an error. I tried to research the error but most people are having this issue in connection with nfs-datastores which i don’t explicitly use. I just use what was given as the default which would be ssh i guess? I’m fairly new to OpenNebula and would appreciate any help :slight_smile:

More details down below. I will gladly provide any additional information.

Versions of the related components and OS (frontend, hypervisors, VMs):

Frontend: Ubuntu 18.04.3 LTS with OpenNebula 5.8.5
Hypervisor: Ubuntu 18.04.3 LTS with KVM (just one node atm)
VM: None right now. Trying to deploy the “Ttylinux - KVM”-VM after first installation

Steps to reproduce:

Trying to start my first VM with the “Verify your Installation” documentation.

Current results:

I run into an error trying to deploy the VM. This is the output of the log:

Sat Nov 2 09:51:23 2019 [Z0][VM][I]: New state is ACTIVE
Sat Nov 2 09:51:23 2019 [Z0][VM][I]: New LCM state is PROLOG
Sat Nov 2 09:51:26 2019 [Z0][VM][I]: New LCM state is BOOT
Sat Nov 2 09:51:26 2019 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/4/deployment.0
Sat Nov 2 09:51:28 2019 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Sat Nov 2 09:51:28 2019 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Sat Nov 2 09:51:29 2019 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy ‘/var/lib/one//datastores/0/4/deployment.0’ ‘192.168.0.39’ 4 192.168.0.39
Sat Nov 2 09:51:29 2019 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/0/4/deployment.0
Sat Nov 2 09:51:29 2019 [Z0][VMM][I]: error: invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm
Sat Nov 2 09:51:29 2019 [Z0][VMM][E]: Could not create domain from /var/lib/one//datastores/0/4/deployment.0
Sat Nov 2 09:51:29 2019 [Z0][VMM][I]: ExitCode: 255
Sat Nov 2 09:51:29 2019 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Sat Nov 2 09:51:29 2019 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/0/4/deployment.0
Sat Nov 2 09:51:29 2019 [Z0][VM][I]: New LCM state is BOOT_FAILURE

Expected results: The VM gets deployed as described in the documentation.

2

Hello @Vasilles,

Did you follow all the steps described in http://docs.opennebula.org/5.8/deployment/node_installation/kvm_node_installation.html for configuring your KVM host?

3

Hey @cgonzalez ,

from my history in the shell i can tell that i did at least the following on the KVM-Node:

echo "deb https://downloads.opennebula.org/repo/5.8/Ubuntu/18.04 stable opennebula" > /etc/apt/sources.list.d/
wget -q -O- https://downloads.opennebula.org/repo/repo.key | apt-key add -
sudo apt-get update
sudo apt-get install opennebula-node
sudo service libvirt-bin restart

I also went through the passwordless SSH setup on the OpenNebula Frontend. Which worked for me:

ssh-keyscan 192.168.0.234 192.168.0.39 >> /var/lib/one/.ssh/known_hosts
ssh-keyscan opennebula >> /var/lib/one/.ssh/known_hosts
scp -rp /var/lib/one/.ssh 192.168.0.39:/var/lib/one/

I didn’t make changes to my network configuration tho:

root@kvm1:/home/vasili# brctl show
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.525400c44ce0       yes             virbr0-nic

root@kvm1:/home/vasili# ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.39  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::a00:27ff:fe6f:95f4  prefixlen 64  scopeid 0x20<link>
        inet6 2a02:908:f64:fda0:a00:27ff:fe6f:95f4  prefixlen 64  scopeid 0x0<global>
        ether 08:00:27:6f:95:f4  txqueuelen 1000  (Ethernet)
        RX packets 3638  bytes 4516111 (4.5 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 776  bytes 93944 (93.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 118  bytes 9546 (9.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 118  bytes 9546 (9.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:c4:4c:e0  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Since i just wanted to get things up and running as quickly as possible i skipped the storage part and went to “Verify your Installation”. I could add the host to OpenNebula without any problems. I thought because the “Verify your Installation” documentation mentions that the VM will not have any network connectivity at this point my missing network configuration wouldn’t be an issue.

Thanks for the help!

4

Hi @Vasilles,

Just to confirm, are you able to connect to the hypervisor node as oneadmin user via paswordless SSH?

5

Hey @cgonzalez,

yes i am able to ssh between the nodes as oneadmin but i think i found the issue with my installation. I used VirtualBox for a test enviroment which doesn’t seem to give the VMs the features to virtualize properly. I used a virtual ESXi Server to verfiy this. I couldn’t start up any vms. I now switched to ESXi on dedicated hardware. Reinstalled everything and now it works just fine.

Thank you for your time :slight_smile: