minishift: invalid argument: could not find capabilities for domaintype=kvm

Hi All, I am following these links, to install minishift in my Fedora 26, https://fedoramagazine.org/run-openshift-locally-minishift/ https://docs.openshift.org/latest/minishift/getting-started/installing.html https://docs.openshift.org/latest/minishift/getting-started/setting-up-driver-plugin.html

I have restarted my system twice following the steps, yet when i execute, minishift start, i see,

-- Checking if KVM driver is installed ... 
   Driver is available at /usr/local/bin/docker-machine-driver-kvm ... 
   Checking driver binary is executable ... OK
-- Checking if Libvirt is installed ... OK
-- Checking if Libvirt default network is present and active ... OK
-- Starting local OpenShift cluster using 'kvm' hypervisor ...
-- Minishift VM will be configured with ...
   Memory:    2 GB
   vCPUs :    2
   Disk size: 20 GB
-- Starting Minishift VM ..... FAIL E1027 20:14:14.223484    7738 start.go:355] Error starting the VM: Error creating the VM. Error creating machine: Error in driver during machine creation: [Code-8] [Domain-44] invalid argument: could not find capabilities for domaintype=kvm . Retrying.
Error starting the VM: Error creating the VM. Error creating machine: Error in driver during machine creation: [Code-8] [Domain-44] invalid argument: could not find capabilities for domaintype=kvm

Is this a common issue with F26 ?

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 19 (10 by maintainers)

Most upvoted comments

For me, this was fixed by installing qemu-kvm package on CentOS 7. I had only done yum install libvirt and expected things to work. Obviously I was wrong.

dharmit on Mar 6, 2018

Please, enable Virtualization Technology in your BIOS.

Closing issue

gbraad on Nov 1, 2017

@dharmit install qemu-kvm in Ubuntu 16.04 works for me. Thanks.

dangtrinhnt on Jul 26, 2018

Can you run:

$ egrep '(vmx|svm)' /proc/cpuinfo

to verify support? To check if the correct modules loaded:

$  lsmod | egrep 'kvm'

gbraad on Nov 1, 2017

After giving the same command dmesg | grep kvm i get this `[root@dsakoce100 apps]# dmesg | grep kvm [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000000] kvm-clock: cpu 0, msr 4:27f7c001, primary cpu clock [ 0.000000] kvm-clock: using sched offset of 515536202834 cycles [ 0.000000] kvm-stealtime: cpu 0, msr 427c0f3c0 [ 0.461944] kvm-clock: cpu 1, msr 4:27f7c041, secondary cpu clock [ 0.484366] kvm-stealtime: cpu 1, msr 427c8f3c0 [ 0.735519] kvm-clock: cpu 2, msr 4:27f7c081, secondary cpu clock [ 0.757708] kvm-stealtime: cpu 2, msr 427d0f3c0 [ 1.008844] kvm-clock: cpu 3, msr 4:27f7c0c1, secondary cpu clock [ 1.031070] kvm-stealtime: cpu 3, msr 427d8f3c0 [ 1.400008] Switched to clocksource kvm-clock [ 2.119060] systemd[1]: Detected virtualization kvm. Do I need to enable KVM nested virtualization? as my Os is running on top of KVM

mupi2015 on Nov 7, 2017

Okay, now i don’t understand this:

[root@dhcp193-200 ~]# dmesg | grep kvm [ 5.584599] kvm: disabled by bios [ 5.621061] kvm: disabled by bios [ 5.687280] kvm: disabled by bios [ 5.726867] kvm: disabled by bios [ 5.754379] kvm: disabled by bios [67953.001692] kvm: disabled by bios

vrlgohel on Nov 1, 2017

@gbraad, I don’t think my system bios do not support virtual machines. Here’s the output i can see, https://gist.github.com/vrlgohel/1339727aed390ed9818168cd4f60df23

vrlgohel on Nov 1, 2017