search

kubernetes / minikube

Run Kubernetes locally
https://minikube.sigs.k8s.io/
Apache License 2.0
28.78k stars 4.81k forks source link

Improve error message for nested KVM issue: could not find capabilities for domaintype=kvm #2991

Closed Fak3 closed 5 years ago

Fak3 commented 5 years ago

minikube version: v0.27.0 OS: opensuse Tumbleweed 20180331 vm driver: kvm2 or kvm "Boot2DockerURL": "file:///home/u1/.minikube/cache/iso/minikube-v0.26.0.iso", "ISO": "/home/u1/.minikube/machines/minikube/boot2docker.iso",

minikube installed from officail repo:

> rpm -qi minikube
Name        : minikube
Version     : 0.27.0
Release     : 1.1
Architecture: x86_64
Install Date: Пн 16 июл 2018 17:59:10
Group       : System/Management
Size        : 43331879
License     : Apache-2.0
Signature   : RSA/SHA256, Пт 22 июн 2018 15:33:56, Key ID b88b2fd43dbdc284
Source RPM  : minikube-0.27.0-1.1.src.rpm
Build Date  : Пт 22 июн 2018 15:32:58
Build Host  : cloud116
Relocations : (not relocatable)
Packager    : https://bugs.opensuse.org
Vendor      : openSUSE
URL         : http://kubernetes.io
Summary     : Tool to run Kubernetes locally
Distribution: openSUSE Tumbleweed

kvm module loaded:

> lsmod | grep kvm
kvm_intel             229376  0
kvm                   700416  1 kvm_intel
irqbypass              16384  1 kvm

user groups:

> groups
kvm wheel users libvirt docker

When i launch minikube start with kvm or kvm2 driver as regular user, it does not start, and i see error invalid argument: could not find capabilities for domaintype=kvm:

> minikube start --vm-driver=kvm2
There is a newer version of minikube available (v0.28.0).  Download it here:
https://github.com/kubernetes/minikube/releases/tag/v0.28.0

To disable this notification, run the following:
minikube config set WantUpdateNotification false
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Downloading Minikube ISO
 150.53 MB / 150.53 MB [============================================] 100.00% 0s
E0716 18:30:16.599687   20347 start.go:159] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: creating domain: Error defining domain xml: 
<domain type='kvm'>
  <name>minikube</name> 
  <memory unit='MB'>2048</memory>
  <vcpu>2</vcpu>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <cpu mode='host-passthrough'/>
  <os>
    <type>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
    <bootmenu enable='no'/>
  </os>
  <devices>
    <disk type='file' device='cdrom'>
      <source file='/home/u1/.minikube/machines/minikube/boot2docker.iso'/>
      <target dev='hdc' bus='scsi'/>
      <readonly/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='default' io='threads' />
      <source file='/home/u1/.minikube/machines/minikube/minikube.rawdisk'/>
      <target dev='hda' bus='virtio'/>
    </disk>
    <interface type='network'>
      <source network='default'/>
      <mac address='ac:11:1f:f4:0d:75'/>
      <model type='virtio'/>
    </interface>
    <interface type='network'>
      <source network='minikube-net'/>
      <mac address='ac:11:1f:f4:0d:75'/>
      <model type='virtio'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <rng model='virtio'>
      <backend model='random'>/dev/random</backend>
    </rng>
  </devices>
</domain>
: virError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for domaintype=kvm ').
Fak3 commented 5 years ago

tried to do minikube delete and rm minikube dir with the same results afterwards

bw2 commented 5 years ago

seeing the same issue on a vanilla CentOS7 VM created on google cloud.
Removing ~/.minikube doesn't help, and I get the same error whether running as a regular user or as root.

Edit: Most likely this was due to nested virtualization not being enabled the google VM

tstromberg commented 5 years ago

This appears to be due to the hosts lack of virtualization abilities, but we should have pre-flight checks to detect this issue.

Fak3 commented 5 years ago

This appears to be due to the hosts lack of virtualization abilities, but we should have pre-flight checks to detect this issue.

What virtualization abilities? I ran previous version of minikube on the same host as root just fine

tstromberg commented 5 years ago

@Fak3 that's a great question. Do you mind sharing the output of these 3 commands?

virt-host-validate 
dmesg | grep kvm
lscpu | grep -q Virtualization || echo "No Virtualization"

Here's a related issue in minishift, which shares some of the same code base with minikube: https://github.com/minishift/minishift/issues/1630

Fak3 commented 5 years ago

@tstromberg 

u1@linux-1zpk:~> virt-host-validate
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller mount-point                  : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpu' controller mount-point                     : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'cpuset' controller mount-point                  : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'devices' controller mount-point                 : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for cgroup 'blkio' controller mount-point                   : PASS
  QEMU: Checking for device assignment IOMMU support                         : WARN (No ACPI DMAR table found, IOMMU either disabled in BIOS or not supported by this hardware platform)
   LXC: Checking for Linux >= 2.6.26                                         : PASS
   LXC: Checking for namespace ipc                                           : PASS
   LXC: Checking for namespace mnt                                           : PASS
   LXC: Checking for namespace pid                                           : PASS
   LXC: Checking for namespace uts                                           : PASS
   LXC: Checking for namespace net                                           : PASS
   LXC: Checking for namespace user                                          : PASS
   LXC: Checking for cgroup 'memory' controller support                      : PASS
   LXC: Checking for cgroup 'memory' controller mount-point                  : PASS
   LXC: Checking for cgroup 'cpu' controller support                         : PASS
   LXC: Checking for cgroup 'cpu' controller mount-point                     : PASS
   LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
   LXC: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
   LXC: Checking for cgroup 'cpuset' controller support                      : PASS
   LXC: Checking for cgroup 'cpuset' controller mount-point                  : PASS
   LXC: Checking for cgroup 'devices' controller support                     : PASS
   LXC: Checking for cgroup 'devices' controller mount-point                 : PASS
   LXC: Checking for cgroup 'blkio' controller support                       : PASS
   LXC: Checking for cgroup 'blkio' controller mount-point                   : PASS
   LXC: Checking if device /sys/fs/fuse/connections exists                   : PASS
u1@linux-1zpk:~> 
u1@linux-1zpk:~> dmesg | grep kvm
u1@linux-1zpk:~> lscpu | grep -q Virtualization || echo "No Virtualization"
u1@linux-1zpk:~> sudo lsmod | grep kvm
[sudo] password for root: 
kvm_intel             237568  0
kvm                   729088  1 kvm_intel
irqbypass              16384  1 kvm
richardsith commented 5 years ago

I've the same problem but in my case when I create a new instance on Openstack

"Last exception: invalid argument: could not find capabilities for domaintype=kvm"

Juancarlosmartin10 commented 5 years ago

I have the shame problem to in CentOS 7 but...

QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available, performance will be significantly limited) QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) LXC: Checking for Linux >= 2.6.26 : PASS LXC: Checking for namespace ipc : PASS LXC: Checking for namespace mnt : PASS LXC: Checking for namespace pid : PASS LXC: Checking for namespace uts : PASS LXC: Checking for namespace net : PASS LXC: Checking for namespace user : PASS LXC: Checking for cgroup 'memory' controller support : PASS LXC: Checking for cgroup 'memory' controller mount-point : PASS LXC: Checking for cgroup 'cpu' controller support : PASS LXC: Checking for cgroup 'cpu' controller mount-point : PASS LXC: Checking for cgroup 'cpuacct' controller support : PASS LXC: Checking for cgroup 'cpuacct' controller mount-point : PASS LXC: Checking for cgroup 'cpuset' controller support : PASS LXC: Checking for cgroup 'cpuset' controller mount-point : PASS LXC: Checking for cgroup 'devices' controller support : PASS LXC: Checking for cgroup 'devices' controller mount-point : PASS LXC: Checking for cgroup 'blkio' controller support : PASS LXC: Checking for cgroup 'blkio' controller mount-point : PASS LXC: Checking if device /sys/fs/fuse/connections exists : FAIL (Load the 'fuse' modu

Fak3 commented 5 years ago

Just tried minikube 0.29 - got the same error

Fak3 commented 5 years ago

The problem is resolved with installation of additional packages. On openSUSE Tumbleweed i have installed following:

kubernetes-kubeadm-1.11.1-5.1.x86_64          Чәрш 17 Окт 2018 13:58:47
cri-o-kubeadm-criconfig-1.11.2-2.1.x86_64     Чәрш 17 Окт 2018 13:58:47
kubernetes-kubelet-1.11.1-5.1.x86_64          Чәрш 17 Окт 2018 13:58:44
cri-o-1.11.2-2.1.x86_64                       Чәрш 17 Окт 2018 13:58:43
cni-plugins-0.6.0-3.2.x86_64                  Чәрш 17 Окт 2018 13:58:39
runc-1.0.0~rc5-3.1.x86_64                     Чәрш 17 Окт 2018 13:58:36
libcontainers-common-0.0.1-4.1.noarch         Чәрш 17 Окт 2018 13:58:36
kubernetes-common-1.11.1-5.1.x86_64           Чәрш 17 Окт 2018 13:58:36
cri-tools-1.11.1-2.2.x86_64                   Чәрш 17 Окт 2018 13:58:27
cni-0.6.0-5.1.x86_64                          Чәрш 17 Окт 2018 13:58:24
patterns-server-kvm_tools-20180718-1.1.x86_64 Чәрш 17 Окт 2018 13:00:22
patterns-server-kvm_server-20180718-1.1.x86_64 Чәрш 17 Окт 2018 13:00:22
virt-manager-common-1.5.1-3.1.noarch          Чәрш 17 Окт 2018 13:00:21
virt-manager-1.5.1-3.1.noarch                 Чәрш 17 Окт 2018 13:00:21
virt-install-1.5.1-3.1.noarch                 Чәрш 17 Окт 2018 13:00:21
vm-install-0.10.04-1.1.x86_64                 Чәрш 17 Окт 2018 13:00:20
libosinfo-1_0-0-1.2.0-1.1.x86_64              Чәрш 17 Окт 2018 13:00:20
qemu-kvm-3.0.0-2.1.x86_64                     Чәрш 17 Окт 2018 13:00:20

I think one of the above packages provided some required libvirt configuration files. Not sure which one.

rogerlee6411 commented 5 years ago

Hi Fak3: could you show me how to resolve this issue ?
I have got same msg as 'Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: creating domain: Error defining domain xml:'

vehsakul commented 5 years ago

@Juancarlosmartin10 it you are inside vbox as I am, this is it https://www.virtualbox.org/ticket/4032 . It does not support virtualization inside VM. The ticket is 9 years old but they plan to release it soon though.

lth2015 commented 5 years ago

I have the shame problem to in CentOS 7 but...

QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available, performance will be significantly limited) QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) LXC: Checking for Linux >= 2.6.26 : PASS LXC: Checking for namespace ipc : PASS LXC: Checking for namespace mnt : PASS LXC: Checking for namespace pid : PASS LXC: Checking for namespace uts : PASS LXC: Checking for namespace net : PASS LXC: Checking for namespace user : PASS LXC: Checking for cgroup 'memory' controller support : PASS LXC: Checking for cgroup 'memory' controller mount-point : PASS LXC: Checking for cgroup 'cpu' controller support : PASS LXC: Checking for cgroup 'cpu' controller mount-point : PASS LXC: Checking for cgroup 'cpuacct' controller support : PASS LXC: Checking for cgroup 'cpuacct' controller mount-point : PASS LXC: Checking for cgroup 'cpuset' controller support : PASS LXC: Checking for cgroup 'cpuset' controller mount-point : PASS LXC: Checking for cgroup 'devices' controller support : PASS LXC: Checking for cgroup 'devices' controller mount-point : PASS LXC: Checking for cgroup 'blkio' controller support : PASS LXC: Checking for cgroup 'blkio' controller mount-point : PASS LXC: Checking if device /sys/fs/fuse/connections exists : FAIL (Load the 'fuse' modu

same problem, Is there a solution?

hemani19 commented 5 years ago

Same issue. Any workaround?

ehohenstein-imvu commented 5 years ago

I had this issue. I am using minikube in a VM under VMWare and I did not enable the option "Virtualize Intel VT-x/EPT or AMD-V/RVI" when I created the VM. I had enabled it after reading this thread but still got the same error. Apparently actually applying the option requires a reboot of the VM and VMWare didn't tell me that so I didn't know. Trying to use the virtualbox driver told me that option was disabled when I thought it was enabled so I tried rebooting and now I no longer get this error.

valtoni commented 5 years ago

Same issue here.

gejiwei commented 5 years ago

QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available, performance will be significantly limited) QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) LXC: Checking for Linux >= 2.6.26 : PASS LXC: Checking for namespace ipc : PASS LXC: Checking for namespace mnt : PASS LXC: Checking for namespace pid : PASS LXC: Checking for namespace uts : PASS LXC: Checking for namespace net : PASS LXC: Checking for namespace user : PASS LXC: Checking for cgroup 'memory' controller support : PASS LXC: Checking for cgroup 'memory' controller mount-point : PASS LXC: Checking for cgroup 'cpu' controller support : PASS LXC: Checking for cgroup 'cpu' controller mount-point : PASS LXC: Checking for cgroup 'cpuacct' controller support : PASS LXC: Checking for cgroup 'cpuacct' controller mount-point : PASS LXC: Checking for cgroup 'cpuset' controller support : PASS LXC: Checking for cgroup 'cpuset' controller mount-point : PASS LXC: Checking for cgroup 'devices' controller support : PASS LXC: Checking for cgroup 'devices' controller mount-point : PASS LXC: Checking for cgroup 'blkio' controller support : PASS LXC: Checking for cgroup 'blkio' controller mount-point : PASS LXC: Checking if device /sys/fs/fuse/connections exists : FAIL (Load the 'fuse' module to enable /proc/ overrides) Has anyone solved it? Thank you

anshu1106 commented 5 years ago

I am running minikube in an aws instance and getting the same error

minikube start --vm-driver kvm2 😄 minikube v0.35.0 on linux (amd64) 🔥 Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ... 💣 Unable to start VM: create: Error creating machine: Error in driver during machine creation: creating domain: Error defining domain xml:

> <domain type='kvm'>
>   <name>minikube</name>
>   <memory unit='MB'>2048</memory>
>   <vcpu>2</vcpu>
>   <features>
>     <acpi/>
>     <apic/>
>     <pae/>
>     <kvm>
>       <hidden state='on'/>
>     </kvm>
>   </features>
>   <cpu mode='host-passthrough'/>
>   <os>
>     <type>hvm</type>
>     <boot dev='cdrom'/>
>     <boot dev='hd'/>
>     <bootmenu enable='no'/>
>   </os>
>   <devices>
>     <disk type='file' device='cdrom'>
>       <source file='/root/.minikube/machines/minikube/boot2docker.iso'/>
>       <target dev='hdc' bus='scsi'/>
>       <readonly/>
>     </disk>
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='raw' cache='default' io='threads' />
>       <source file='/root/.minikube/machines/minikube/minikube.rawdisk'/>
>       <target dev='hda' bus='virtio'/>
>     </disk>
>     <interface type='network'>
>       <source network='default'/>
>       <mac address='c0:b2:08:60:f7:8f'/>
>       <model type='virtio'/>
>     </interface>
>     <interface type='network'>
>       <source network='minikube-net'/>
>       <mac address='94:d8:2b:b1:68:ba'/>
>       <model type='virtio'/>
>     </interface>
>     <serial type='pty'>
>       <target port='0'/>
>     </serial>
>     <console type='pty'>
>       <target type='serial' port='0'/>
>     </console>
>     <rng model='virtio'>
>       <backend model='random'>/dev/random</backend>
>     </rng>
> 
>   </devices>
> </domain>

: virError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for domaintype=kvm ')

Please help in resolving this.

loupipalien commented 5 years ago

running minikube in a centos7 vm and getting the same error.

[root@localhost ~]# minikube start --vm-driver kvm2
o   minikube v1.0.0 on linux (amd64)
$   Downloading Kubernetes v1.14.0 images in the background ...
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
>   Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
@   Downloading Minikube ISO ...
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
2019/04/22 12:49:17 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/22 12:49:17 No matching credentials were found, falling back on anonymous
 142.88 MB / 142.88 MB [============================================] 100.00% 0s

!   Unable to start VM: create: Error creating machine: Error in driver during machine creation: creating domain: Error defining domain xml: 
<domain type='kvm'>
  <name>minikube</name> 
  <memory unit='MB'>2048</memory>
  <vcpu>2</vcpu>
  <features>
    <acpi/>
    <apic/>
    <pae/>

  </features>
  <cpu mode='host-passthrough'/>
  <os>
    <type>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
    <bootmenu enable='no'/>
  </os>
  <devices>
    <disk type='file' device='cdrom'>
      <source file='/root/.minikube/machines/minikube/boot2docker.iso'/>
      <target dev='hdc' bus='scsi'/>
      <readonly/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='default' io='threads' />
      <source file='/root/.minikube/machines/minikube/minikube.rawdisk'/>
      <target dev='hda' bus='virtio'/>
    </disk>
    <interface type='network'>
      <source network='default'/>
      <mac address='a4:73:42:33:ef:cc'/>
      <model type='virtio'/>
    </interface>
    <interface type='network'>
      <source network='minikube-net'/>
      <mac address='ac:83:2e:1c:15:ea'/>
      <model type='virtio'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <rng model='virtio'>
      <backend model='random'>/dev/random</backend>
    </rng>

  </devices>
</domain>
: virError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for domaintype=kvm ')

*   Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
-   https://github.com/kubernetes/minikube/issues/new
[root@localhost ~]# groups
root libvirt
[root@localhost ~]# virt-host-validate 
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller mount-point                  : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpu' controller mount-point                     : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'cpuset' controller mount-point                  : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'devices' controller mount-point                 : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for cgroup 'blkio' controller mount-point                   : PASS
  QEMU: Checking for device assignment IOMMU support                         : WARN (No ACPI DMAR table found, IOMMU either disabled in BIOS or not supported by this hardware platform)
   LXC: Checking for Linux >= 2.6.26                                         : PASS
   LXC: Checking for namespace ipc                                           : PASS
   LXC: Checking for namespace mnt                                           : PASS
   LXC: Checking for namespace pid                                           : PASS
   LXC: Checking for namespace uts                                           : PASS
   LXC: Checking for namespace net                                           : PASS
   LXC: Checking for namespace user                                          : PASS
   LXC: Checking for cgroup 'memory' controller support                      : PASS
   LXC: Checking for cgroup 'memory' controller mount-point                  : PASS
   LXC: Checking for cgroup 'cpu' controller support                         : PASS
   LXC: Checking for cgroup 'cpu' controller mount-point                     : PASS
   LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
   LXC: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
   LXC: Checking for cgroup 'cpuset' controller support                      : PASS
   LXC: Checking for cgroup 'cpuset' controller mount-point                  : PASS
   LXC: Checking for cgroup 'devices' controller support                     : PASS
   LXC: Checking for cgroup 'devices' controller mount-point                 : PASS
   LXC: Checking for cgroup 'blkio' controller support                       : PASS
   LXC: Checking for cgroup 'blkio' controller mount-point                   : PASS
   LXC: Checking if device /sys/fs/fuse/connections exists                   : PASS
[root@localhost ~]# dmesg | grep kvm
[root@localhost ~]# lscpu | grep -q Virtualization || echo "No Virtualization"
[root@localhost ~]# lsmod | grep kvm
kvm_intel             162153  0 
kvm                   525259  1 kvm_intel
tstromberg commented 5 years ago

I believe this issue was resolved in the v1.1.0 release. Please try upgrading to the latest release of minikube, and if the same issue occurs, please re-open this bug. Thank you opening this bug report, and for your patience!

charlescasemiro commented 5 years ago

[root@kube ~]# minikube version minikube version: v1.1.1 [root@kube ~]# virt-host-validate QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available, performance will be significantly limited) QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) LXC: Checking for Linux >= 2.6.26 : PASS LXC: Checking for namespace ipc : PASS LXC: Checking for namespace mnt : PASS LXC: Checking for namespace pid : PASS LXC: Checking for namespace uts : PASS LXC: Checking for namespace net : PASS LXC: Checking for namespace user : PASS LXC: Checking for cgroup 'memory' controller support : PASS LXC: Checking for cgroup 'memory' controller mount-point : PASS LXC: Checking for cgroup 'cpu' controller support : PASS LXC: Checking for cgroup 'cpu' controller mount-point : PASS LXC: Checking for cgroup 'cpuacct' controller support : PASS LXC: Checking for cgroup 'cpuacct' controller mount-point : PASS LXC: Checking for cgroup 'cpuset' controller support : PASS LXC: Checking for cgroup 'cpuset' controller mount-point : PASS LXC: Checking for cgroup 'devices' controller support : PASS LXC: Checking for cgroup 'devices' controller mount-point : PASS LXC: Checking for cgroup 'blkio' controller support : PASS LXC: Checking for cgroup 'blkio' controller mount-point : PASS LXC: Checking if device /sys/fs/fuse/connections exists : FAIL (Load the 'fuse' module to enable /proc/ overrides) [root@kube ~]#

Still error with the 1.1 version

qqzeng commented 5 years ago

[root@kube ~]# minikube version minikube version: v1.1.1 [root@kube ~]# virt-host-validate QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available, performance will be significantly limited) QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) LXC: Checking for Linux >= 2.6.26 : PASS LXC: Checking for namespace ipc : PASS LXC: Checking for namespace mnt : PASS LXC: Checking for namespace pid : PASS LXC: Checking for namespace uts : PASS LXC: Checking for namespace net : PASS LXC: Checking for namespace user : PASS LXC: Checking for cgroup 'memory' controller support : PASS LXC: Checking for cgroup 'memory' controller mount-point : PASS LXC: Checking for cgroup 'cpu' controller support : PASS LXC: Checking for cgroup 'cpu' controller mount-point : PASS LXC: Checking for cgroup 'cpuacct' controller support : PASS LXC: Checking for cgroup 'cpuacct' controller mount-point : PASS LXC: Checking for cgroup 'cpuset' controller support : PASS LXC: Checking for cgroup 'cpuset' controller mount-point : PASS LXC: Checking for cgroup 'devices' controller support : PASS LXC: Checking for cgroup 'devices' controller mount-point : PASS LXC: Checking for cgroup 'blkio' controller support : PASS LXC: Checking for cgroup 'blkio' controller mount-point : PASS LXC: Checking if device /sys/fs/fuse/connections exists : FAIL (Load the 'fuse' module to enable /proc/ overrides) [root@kube ~]#

Still error with the 1.1 version

Refer: https://www.virtualbox.org/ticket/4032. VirtualBox doesn't support "Nested Virtualization: VT-in-VT". Try VMware WorkStation Pro. It works in my case.

yuchengwu commented 4 years ago

Tried with minikube 1.6.2 but with no luck

minikube version:

$ ./out/minikube-linux-amd64 version 
minikube version: v1.6.2
commit: 54f28ac5d3a815d1196cd5d57d707439ee4bb392

some checks :

$ virt-host-validate 
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for device assignment IOMMU support                         : PASS
  QEMU: Checking if IOMMU is enabled by kernel                               : PASS
   LXC: Checking for Linux >= 2.6.26                                         : PASS
   LXC: Checking for namespace ipc                                           : PASS
   LXC: Checking for namespace mnt                                           : PASS
   LXC: Checking for namespace pid                                           : PASS
   LXC: Checking for namespace uts                                           : PASS
   LXC: Checking for namespace net                                           : PASS
   LXC: Checking for namespace user                                          : PASS
   LXC: Checking for cgroup 'cpu' controller support                         : PASS
   LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
   LXC: Checking for cgroup 'cpuset' controller support                      : PASS
   LXC: Checking for cgroup 'memory' controller support                      : PASS
   LXC: Checking for cgroup 'devices' controller support                     : PASS
   LXC: Checking for cgroup 'freezer' controller support                     : PASS
   LXC: Checking for cgroup 'blkio' controller support                       : PASS
   LXC: Checking if device /sys/fs/fuse/connections exists                   : PASS

$ dmesg | grep kvm
[    9.866344] kvm: Nested Virtualization enabled
[    9.866350] kvm: Nested Paging enabled
[  326.546446] kvm: enabling virtualization on CPU6 failed
[  326.546448] kvm: enabling virtualization on CPU2 failed
[  326.546449] kvm: enabling virtualization on CPU3 failed
[  326.546451] kvm: enabling virtualization on CPU9 failed
[  326.546452] kvm: enabling virtualization on CPU11 failed
[  326.546453] kvm: enabling virtualization on CPU5 failed
[  326.546455] kvm: enabling virtualization on CPU4 failed
[  326.546456] kvm: enabling virtualization on CPU8 failed
[  326.546457] kvm: enabling virtualization on CPU10 failed
[  326.546461] kvm: enabling virtualization on CPU1 failed
[  326.546462] kvm: enabling virtualization on CPU7 failed
[  326.546468] kvm: enabling virtualization on CPU0 failed
[  326.695999] kvm: enabling virtualization on CPU2 failed
[  326.696001] kvm: enabling virtualization on CPU0 failed
[  326.696002] kvm: enabling virtualization on CPU8 failed
[  326.696003] kvm: enabling virtualization on CPU9 failed
[  326.696005] kvm: enabling virtualization on CPU3 failed
[  326.696006] kvm: enabling virtualization on CPU10 failed
[  326.696007] kvm: enabling virtualization on CPU5 failed
[  326.696009] kvm: enabling virtualization on CPU4 failed
[  326.696010] kvm: enabling virtualization on CPU11 failed
[  326.696011] kvm: enabling virtualization on CPU7 failed
[  326.696013] kvm: enabling virtualization on CPU1 failed
[  326.696016] kvm: enabling virtualization on CPU6 failed
[  394.275472] kvm: enabling virtualization on CPU3 failed
[  394.275474] kvm: enabling virtualization on CPU9 failed
[  394.275475] kvm: enabling virtualization on CPU4 failed
[  394.275477] kvm: enabling virtualization on CPU0 failed
[  394.275478] kvm: enabling virtualization on CPU11 failed
[  394.275480] kvm: enabling virtualization on CPU7 failed
[  394.275481] kvm: enabling virtualization on CPU1 failed
[  394.275481] kvm: enabling virtualization on CPU6 failed
[  394.275483] kvm: enabling virtualization on CPU10 failed
[  394.275485] kvm: enabling virtualization on CPU2 failed
[  394.275486] kvm: enabling virtualization on CPU8 failed
[  394.275490] kvm: enabling virtualization on CPU5 failed
[  403.300566] kvm: enabling virtualization on CPU4 failed
[  403.300568] kvm: enabling virtualization on CPU5 failed
[  403.300569] kvm: enabling virtualization on CPU10 failed
[  403.300570] kvm: enabling virtualization on CPU11 failed
[  403.300572] kvm: enabling virtualization on CPU0 failed
[  403.300574] kvm: enabling virtualization on CPU1 failed
[  403.300575] kvm: enabling virtualization on CPU3 failed
[  403.300576] kvm: enabling virtualization on CPU6 failed
[  403.300577] kvm: enabling virtualization on CPU7 failed
[  403.300580] kvm: enabling virtualization on CPU2 failed
[  403.300582] kvm: enabling virtualization on CPU8 failed
[  403.300585] kvm: enabling virtualization on CPU9 failed
[  676.884294] kvm: enabling virtualization on CPU1 failed
[  676.884296] kvm: enabling virtualization on CPU0 failed
[  676.884298] kvm: enabling virtualization on CPU4 failed
[  676.884299] kvm: enabling virtualization on CPU11 failed
[  676.884301] kvm: enabling virtualization on CPU5 failed
[  676.884303] kvm: enabling virtualization on CPU9 failed
[  676.884304] kvm: enabling virtualization on CPU3 failed
[  676.884305] kvm: enabling virtualization on CPU10 failed
[  676.884306] kvm: enabling virtualization on CPU6 failed
[  676.884310] kvm: enabling virtualization on CPU2 failed
[  676.884311] kvm: enabling virtualization on CPU8 failed
[  676.884315] kvm: enabling virtualization on CPU7 failed
[  786.124394] kvm: enabling virtualization on CPU1 failed
[  786.124395] kvm: enabling virtualization on CPU0 failed
[  786.124396] kvm: enabling virtualization on CPU6 failed
[  786.124397] kvm: enabling virtualization on CPU8 failed
[  786.124400] kvm: enabling virtualization on CPU3 failed
[  786.124401] kvm: enabling virtualization on CPU7 failed
[  786.124403] kvm: enabling virtualization on CPU4 failed
[  786.124404] kvm: enabling virtualization on CPU10 failed
[  786.124406] kvm: enabling virtualization on CPU9 failed
[  786.124410] kvm: enabling virtualization on CPU5 failed
[  786.124412] kvm: enabling virtualization on CPU11 failed
[  786.124415] kvm: enabling virtualization on CPU2 failed
[  786.222086] kvm: enabling virtualization on CPU3 failed
[  786.222088] kvm: enabling virtualization on CPU8 failed
[  786.222089] kvm: enabling virtualization on CPU1 failed
[  786.222090] kvm: enabling virtualization on CPU2 failed
[  786.222091] kvm: enabling virtualization on CPU6 failed
[  786.222092] kvm: enabling virtualization on CPU0 failed
[  786.222094] kvm: enabling virtualization on CPU7 failed
[  786.222096] kvm: enabling virtualization on CPU5 failed
[  786.222097] kvm: enabling virtualization on CPU9 failed
[  786.222101] kvm: enabling virtualization on CPU4 failed
[  786.222103] kvm: enabling virtualization on CPU10 failed
[  786.222107] kvm: enabling virtualization on CPU11 failed
[ 2324.020799] kvm: enabling virtualization on CPU4 failed
[ 2324.020800] kvm: enabling virtualization on CPU3 failed
[ 2324.020802] kvm: enabling virtualization on CPU0 failed
[ 2324.020803] kvm: enabling virtualization on CPU1 failed
[ 2324.020805] kvm: enabling virtualization on CPU11 failed
[ 2324.020807] kvm: enabling virtualization on CPU5 failed
[ 2324.020808] kvm: enabling virtualization on CPU9 failed
[ 2324.020809] kvm: enabling virtualization on CPU10 failed
[ 2324.020811] kvm: enabling virtualization on CPU7 failed
[ 2324.020813] kvm: enabling virtualization on CPU8 failed
[ 2324.020816] kvm: enabling virtualization on CPU2 failed
[ 2324.020819] kvm: enabling virtualization on CPU6 failed
[ 2386.335821] kvm: enabling virtualization on CPU5 failed
[ 2386.335822] kvm: enabling virtualization on CPU3 failed
[ 2386.335823] kvm: enabling virtualization on CPU4 failed
[ 2386.335824] kvm: enabling virtualization on CPU10 failed
[ 2386.335826] kvm: enabling virtualization on CPU0 failed
[ 2386.335828] kvm: enabling virtualization on CPU1 failed
[ 2386.335829] kvm: enabling virtualization on CPU8 failed
[ 2386.335830] kvm: enabling virtualization on CPU9 failed
[ 2386.335831] kvm: enabling virtualization on CPU11 failed
[ 2386.335832] kvm: enabling virtualization on CPU6 failed
[ 2386.335834] kvm: enabling virtualization on CPU7 failed
[ 2386.335836] kvm: enabling virtualization on CPU2 failed
[ 2408.427496] kvm: enabling virtualization on CPU3 failed
[ 2408.427497] kvm: enabling virtualization on CPU5 failed
[ 2408.427498] kvm: enabling virtualization on CPU9 failed
[ 2408.427500] kvm: enabling virtualization on CPU4 failed
[ 2408.427501] kvm: enabling virtualization on CPU10 failed
[ 2408.427502] kvm: enabling virtualization on CPU8 failed
[ 2408.427504] kvm: enabling virtualization on CPU11 failed
[ 2408.427508] kvm: enabling virtualization on CPU0 failed
[ 2408.427509] kvm: enabling virtualization on CPU6 failed
[ 2408.427512] kvm: enabling virtualization on CPU7 failed
[ 2408.427516] kvm: enabling virtualization on CPU1 failed
[ 2408.427519] kvm: enabling virtualization on CPU2 failed
[ 3435.920426] kvm: enabling virtualization on CPU7 failed
[ 3435.920427] kvm: enabling virtualization on CPU1 failed
[ 3435.920428] kvm: enabling virtualization on CPU2 failed
[ 3435.920429] kvm: enabling virtualization on CPU8 failed
[ 3435.920431] kvm: enabling virtualization on CPU4 failed
[ 3435.920432] kvm: enabling virtualization on CPU3 failed
[ 3435.920434] kvm: enabling virtualization on CPU5 failed
[ 3435.920436] kvm: enabling virtualization on CPU6 failed
[ 3435.920437] kvm: enabling virtualization on CPU9 failed
[ 3435.920439] kvm: enabling virtualization on CPU10 failed
[ 3435.920440] kvm: enabling virtualization on CPU11 failed
[ 3435.920444] kvm: enabling virtualization on CPU0 failed
[ 3436.074156] kvm: enabling virtualization on CPU4 failed
[ 3436.074156] kvm: enabling virtualization on CPU10 failed
[ 3436.074158] kvm: enabling virtualization on CPU5 failed
[ 3436.074159] kvm: enabling virtualization on CPU9 failed
[ 3436.074161] kvm: enabling virtualization on CPU0 failed
[ 3436.074162] kvm: enabling virtualization on CPU1 failed
[ 3436.074164] kvm: enabling virtualization on CPU8 failed
[ 3436.074165] kvm: enabling virtualization on CPU2 failed
[ 3436.074166] kvm: enabling virtualization on CPU6 failed
[ 3436.074168] kvm: enabling virtualization on CPU7 failed
[ 3436.074170] kvm: enabling virtualization on CPU11 failed
[ 3436.074175] kvm: enabling virtualization on CPU3 failed
[ 3630.362243] kvm: enabling virtualization on CPU0 failed
[ 3630.362244] kvm: enabling virtualization on CPU1 failed
[ 3630.362246] kvm: enabling virtualization on CPU4 failed
[ 3630.362247] kvm: enabling virtualization on CPU2 failed
[ 3630.362249] kvm: enabling virtualization on CPU7 failed
[ 3630.362250] kvm: enabling virtualization on CPU6 failed
[ 3630.362251] kvm: enabling virtualization on CPU10 failed
[ 3630.362253] kvm: enabling virtualization on CPU11 failed
[ 3630.362255] kvm: enabling virtualization on CPU8 failed
[ 3630.362257] kvm: enabling virtualization on CPU3 failed
[ 3630.362259] kvm: enabling virtualization on CPU9 failed
[ 3630.362261] kvm: enabling virtualization on CPU5 failed
[ 3630.514604] kvm: enabling virtualization on CPU5 failed
[ 3630.514605] kvm: enabling virtualization on CPU0 failed
[ 3630.514607] kvm: enabling virtualization on CPU1 failed
[ 3630.514609] kvm: enabling virtualization on CPU2 failed
[ 3630.514610] kvm: enabling virtualization on CPU3 failed
[ 3630.514612] kvm: enabling virtualization on CPU9 failed
[ 3630.514614] kvm: enabling virtualization on CPU7 failed
[ 3630.514614] kvm: enabling virtualization on CPU6 failed
[ 3630.514616] kvm: enabling virtualization on CPU11 failed
[ 3630.514618] kvm: enabling virtualization on CPU8 failed
[ 3630.514620] kvm: enabling virtualization on CPU10 failed
[ 3630.514622] kvm: enabling virtualization on CPU4 failed
[ 3828.086693] kvm: enabling virtualization on CPU1 failed
[ 3828.086693] kvm: enabling virtualization on CPU2 failed
[ 3828.086694] kvm: enabling virtualization on CPU8 failed
[ 3828.086695] kvm: enabling virtualization on CPU7 failed
[ 3828.086696] kvm: enabling virtualization on CPU6 failed
[ 3828.086698] kvm: enabling virtualization on CPU3 failed
[ 3828.086699] kvm: enabling virtualization on CPU5 failed
[ 3828.086700] kvm: enabling virtualization on CPU4 failed
[ 3828.086703] kvm: enabling virtualization on CPU9 failed
[ 3828.086704] kvm: enabling virtualization on CPU10 failed
[ 3828.086705] kvm: enabling virtualization on CPU11 failed
[ 3828.086710] kvm: enabling virtualization on CPU0 failed
[ 3833.369978] kvm: enabling virtualization on CPU6 failed
[ 3833.369979] kvm: enabling virtualization on CPU0 failed
[ 3833.369981] kvm: enabling virtualization on CPU7 failed
[ 3833.369981] kvm: enabling virtualization on CPU8 failed
[ 3833.369982] kvm: enabling virtualization on CPU1 failed
[ 3833.369984] kvm: enabling virtualization on CPU4 failed
[ 3833.369986] kvm: enabling virtualization on CPU10 failed
[ 3833.369993] kvm: enabling virtualization on CPU3 failed
[ 3833.369994] kvm: enabling virtualization on CPU9 failed
[ 3833.369997] kvm: enabling virtualization on CPU5 failed
[ 3833.369998] kvm: enabling virtualization on CPU11 failed
[ 3833.370000] kvm: enabling virtualization on CPU2 failed
[ 3833.465995] kvm: enabling virtualization on CPU1 failed
[ 3833.465997] kvm: enabling virtualization on CPU2 failed
[ 3833.465998] kvm: enabling virtualization on CPU8 failed
[ 3833.466000] kvm: enabling virtualization on CPU0 failed
[ 3833.466001] kvm: enabling virtualization on CPU7 failed
[ 3833.466002] kvm: enabling virtualization on CPU3 failed
[ 3833.466004] kvm: enabling virtualization on CPU5 failed
[ 3833.466005] kvm: enabling virtualization on CPU4 failed
[ 3833.466007] kvm: enabling virtualization on CPU9 failed
[ 3833.466008] kvm: enabling virtualization on CPU10 failed
[ 3833.466009] kvm: enabling virtualization on CPU11 failed
[ 3833.466013] kvm: enabling virtualization on CPU6 failed
[ 3852.039891] kvm: enabling virtualization on CPU3 failed
[ 3852.039892] kvm: enabling virtualization on CPU9 failed
[ 3852.039893] kvm: enabling virtualization on CPU5 failed
[ 3852.039895] kvm: enabling virtualization on CPU10 failed
[ 3852.039896] kvm: enabling virtualization on CPU11 failed
[ 3852.039898] kvm: enabling virtualization on CPU0 failed
[ 3852.039899] kvm: enabling virtualization on CPU6 failed
[ 3852.039906] kvm: enabling virtualization on CPU1 failed
[ 3852.039909] kvm: enabling virtualization on CPU7 failed
[ 3852.039911] kvm: enabling virtualization on CPU8 failed
[ 3852.039916] kvm: enabling virtualization on CPU2 failed
[ 3852.039922] kvm: enabling virtualization on CPU4 failed
[ 3855.127363] kvm: enabling virtualization on CPU1 failed
[ 3855.127364] kvm: enabling virtualization on CPU7 failed
[ 3855.127365] kvm: enabling virtualization on CPU6 failed
[ 3855.127366] kvm: enabling virtualization on CPU8 failed
[ 3855.127367] kvm: enabling virtualization on CPU2 failed
[ 3855.127368] kvm: enabling virtualization on CPU3 failed
[ 3855.127368] kvm: enabling virtualization on CPU9 failed
[ 3855.127374] kvm: enabling virtualization on CPU4 failed
[ 3855.127375] kvm: enabling virtualization on CPU10 failed
[ 3855.127378] kvm: enabling virtualization on CPU11 failed
[ 3855.127379] kvm: enabling virtualization on CPU5 failed
[ 3855.127383] kvm: enabling virtualization on CPU0 failed
[ 3856.183202] kvm: enabling virtualization on CPU1 failed
[ 3856.183203] kvm: enabling virtualization on CPU6 failed
[ 3856.183205] kvm: enabling virtualization on CPU0 failed
[ 3856.183206] kvm: enabling virtualization on CPU7 failed
[ 3856.183207] kvm: enabling virtualization on CPU2 failed
[ 3856.183209] kvm: enabling virtualization on CPU11 failed
[ 3856.183210] kvm: enabling virtualization on CPU5 failed
[ 3856.183217] kvm: enabling virtualization on CPU3 failed
[ 3856.183219] kvm: enabling virtualization on CPU9 failed
[ 3856.183220] kvm: enabling virtualization on CPU4 failed
[ 3856.183222] kvm: enabling virtualization on CPU10 failed
[ 3856.183224] kvm: enabling virtualization on CPU8 failed
$ lscpu | grep -q Virtualization || echo "No Virtualization"
// no output
$ kvm --version 
QEMU emulator version 3.1.0 (Debian 1:3.1+dfsg-2ubuntu3.7)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
$ /usr/bin/qemu-system-x86_64 --version 
QEMU emulator version 3.1.0 (Debian 1:3.1+dfsg-2ubuntu3.7)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
$ cat /proc/cpuinfo | grep -e  svm -e vmx -c 
12
$  apt search qemu-kvm
qemu-kvm/disco-updates,now 1:3.1+dfsg-2ubuntu3.7 amd64 [installed]
$ docker-machine-driver-kvm2 version
version: v1.6.2
commit: 54f28ac5d3a815d1196cd5d57d707439ee4bb392

the output of minikube start command(with debug info):

$ ./out/minikube-linux-amd64 start --alsologtostderr -v=7 --vm-driver=kvm2 --iso-url=https://kubernetes.oss-cn-hangzhou.aliyuncs.com/minikube/iso/minikube-v1.6.0.iso --image-mirror-country='cn' --image-repository='registry.cn-hangzhou.aliyuncs.com/google_containers' --registry-mirror=https://registry.docker-cn.com
I1229 22:35:06.881334   12060 notify.go:125] Checking for updates...
I1229 22:35:08.102999   12060 start.go:255] hostinfo: {"hostname":"3600","uptime":3630,"bootTime":1577626478,"procs":475,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"19.04","kernelVersion":"5.0.0-37-generic","virtualizationSystem":"kvm","virtualizationRole":"host","hostid":"e124648c-1671-4f43-8a72-9804d20188e4"}
I1229 22:35:08.103690   12060 start.go:265] virtualization: kvm host
😄  minikube v1.6.2 on Ubuntu 19.04
I1229 22:35:08.103769   12060 start.go:555] selectDriver: flag="kvm2", old=<nil>
I1229 22:35:08.103785   12060 global.go:60] Querying for installed drivers using PATH=/home/wyc/.minikube/bin:/usr/local/go/bin:/home/wyc/go/bin:/home/wyc/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
I1229 22:35:08.103824   12060 global.go:68] vmware priority: 5, state: {Installed:false Healthy:false Error:exec: "docker-machine-driver-vmware": executable file not found in $PATH Fix:Install docker-machine-driver-vmware Doc:https://minikube.sigs.k8s.io/docs/reference/drivers/vmware/}
I1229 22:35:08.217918   12060 global.go:68] kvm2 priority: 6, state: {Installed:true Healthy:false Error:/usr/bin/virsh domcapabilities --virttype kvm failed:
error: failed to get emulator capabilities
error: invalid argument: KVM is not supported by '/usr/bin/qemu-system-x86_64' on this host Fix:Follow your Linux distribution instructions for configuring KVM Doc:https://minikube.sigs.k8s.io/docs/reference/drivers/kvm2/}
I1229 22:35:08.217993   12060 global.go:68] none priority: 2, state: {Installed:true Healthy:true Error:<nil> Fix: Doc:}
I1229 22:35:08.257946   12060 global.go:68] virtualbox priority: 4, state: {Installed:true Healthy:true Error:<nil> Fix: Doc:}
I1229 22:35:08.257985   12060 driver.go:109] requested: "kvm2"
I1229 22:35:08.257998   12060 driver.go:132] "virtualbox" has a higher priority (4) than "" (0)
I1229 22:35:08.258009   12060 driver.go:128] not recommending "none" due to priority: 2
I1229 22:35:08.258019   12060 driver.go:113] choosing "kvm2" because it was requested
I1229 22:35:08.258028   12060 driver.go:146] Picked: kvm2
I1229 22:35:08.258039   12060 driver.go:147] Alternatives: [virtualbox none]
✨  Selecting 'kvm2' driver from user configuration (alternates: [virtualbox none])
I1229 22:35:08.258114   12060 start.go:297] selected driver: kvm2
I1229 22:35:08.258122   12060 start.go:585] validating driver "kvm2" against <nil>
I1229 22:35:08.371508   12060 start.go:591] status for kvm2: {Installed:true Healthy:false Error:/usr/bin/virsh domcapabilities --virttype kvm failed:
error: failed to get emulator capabilities
error: invalid argument: KVM is not supported by '/usr/bin/qemu-system-x86_64' on this host Fix:Follow your Linux distribution instructions for configuring KVM Doc:https://minikube.sigs.k8s.io/docs/reference/drivers/kvm2/}

⚠️  'kvm2' driver reported an issue: /usr/bin/virsh domcapabilities --virttype kvm failed:
error: failed to get emulator capabilities
error: invalid argument: KVM is not supported by '/usr/bin/qemu-system-x86_64' on this host
💡  Suggestion: Follow your Linux distribution instructions for configuring KVM
📘  Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/kvm2/

I1229 22:35:08.371712   12060 install.go:102] Validating docker-machine-driver-kvm2, PATH=/home/wyc/.minikube/bin:/usr/local/go/bin:/home/wyc/go/bin:/home/wyc/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
I1229 22:35:08.384888   12060 start.go:650] selecting image repository for country cn ...
✅  Using image repository registry.cn-hangzhou.aliyuncs.com/google_containers
I1229 22:35:08.544610   12060 downloader.go:60] Not caching ISO, using https://kubernetes.oss-cn-hangzhou.aliyuncs.com/minikube/iso/minikube-v1.6.0.iso
I1229 22:35:08.544824   12060 profile.go:89] Saving config to /home/wyc/.minikube/profiles/minikube/config.json ...
I1229 22:35:08.544825   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.6.5 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/coredns_1.6.5
I1229 22:35:08.544851   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.3-0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/etcd_3.4.3-0
I1229 22:35:08.544863   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/coredns_1.6.5 exists
I1229 22:35:08.544883   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.6.5 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/coredns_1.6.5 completed in 74.211µs
I1229 22:35:08.545061   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver_v1.17.0
I1229 22:35:08.545118   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver_v1.17.0 exists
I1229 22:35:08.545098   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/etcd_3.4.3-0 exists
I1229 22:35:08.544825   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-scraper:v1.0.2 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-scraper_v1.0.2
I1229 22:35:08.545136   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.6.5 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/coredns_1.6.5 succeeded
I1229 22:35:08.545214   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/pause_3.1
I1229 22:35:08.544860   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler_v1.17.0
I1229 22:35:08.545253   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/storage-provisioner:v1.8.1 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/storage-provisioner_v1.8.1
I1229 22:35:08.545331   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/storage-provisioner_v1.8.1 exists
I1229 22:35:08.545319   12060 lock.go:35] WriteFile acquiring /home/wyc/.minikube/profiles/minikube/config.json: {Name:mkbd64491712af7accb77961d0d4b5df4102cc8c Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I1229 22:35:08.545354   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/storage-provisioner:v1.8.1 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/storage-provisioner_v1.8.1 completed in 112.062µs
I1229 22:35:08.545401   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/storage-provisioner:v1.8.1 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/storage-provisioner_v1.8.1 succeeded
I1229 22:35:08.544863   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager_v1.17.0
I1229 22:35:08.545458   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager_v1.17.0 exists
I1229 22:35:08.545472   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager_v1.17.0 completed in 625.579µs
I1229 22:35:08.545503   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager_v1.17.0 succeeded
I1229 22:35:08.545163   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.3-0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/etcd_3.4.3-0 completed in 327.255µs
I1229 22:35:08.545541   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.3-0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/etcd_3.4.3-0 succeeded
I1229 22:35:08.545135   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver_v1.17.0 completed in 255.754µs
I1229 22:35:08.545606   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver_v1.17.0 succeeded
I1229 22:35:08.545091   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy_v1.17.0
I1229 22:35:08.545247   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/pause_3.1 exists
I1229 22:35:08.545684   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/pause_3.1 completed in 477.817µs
I1229 22:35:08.545699   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/pause_3.1 succeeded
I1229 22:35:08.545257   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/dashboard:v2.0.0-beta8 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/dashboard_v2.0.0-beta8
I1229 22:35:08.545690   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy_v1.17.0 exists
I1229 22:35:08.545653   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler_v1.17.0 exists
I1229 22:35:08.545780   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy_v1.17.0 completed in 690.32µs
I1229 22:35:08.545792   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler_v1.17.0 completed in 935.543µs
I1229 22:35:08.545804   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy_v1.17.0 succeeded
I1229 22:35:08.545749   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/dashboard_v2.0.0-beta8 exists
I1229 22:35:08.545265   12060 cache_images.go:347] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-addon-manager:v9.0.2 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-addon-manager_v9.0.2
I1229 22:35:08.545813   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.17.0 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler_v1.17.0 succeeded
I1229 22:35:08.545717   12060 cluster.go:97] Machine does not exist... provisioning new machine
I1229 22:35:08.545874   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-addon-manager_v9.0.2 exists
I1229 22:35:08.545888   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-addon-manager:v9.0.2 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-addon-manager_v9.0.2 completed in 624.429µs
I1229 22:35:08.545901   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/kube-addon-manager:v9.0.2 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/kube-addon-manager_v9.0.2 succeeded
I1229 22:35:08.545890   12060 cluster.go:98] Provisioning machine with config: {Name:minikube KeepContext:false EmbedCerts:false MinikubeISO:https://kubernetes.oss-cn-hangzhou.aliyuncs.com/minikube/iso/minikube-v1.6.0.iso Memory:2000 CPUs:2 DiskSize:20000 VMDriver:kvm2 ContainerRuntime:docker HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] InsecureRegistry:[] RegistryMirror:[https://registry.docker-cn.com] HostOnlyCIDR:192.168.99.1/24 HypervVirtualSwitch: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false Downloader:{} DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true KubernetesConfig:{KubernetesVersion:v1.17.0 NodeIP: NodePort:8443 NodeName:minikube APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository:registry.cn-hangzhou.aliyuncs.com/google_containers ExtraOptions:[] ShouldLoadCachedImages:true EnableDefaultCNI:false} HostOnlyNicType:virtio NatNicType:virtio}
I1229 22:35:08.545297   12060 cache_images.go:353] /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-scraper_v1.0.2 exists
I1229 22:35:08.546197   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-scraper:v1.0.2 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-scraper_v1.0.2 completed in 1.37903ms
I1229 22:35:08.546214   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-scraper:v1.0.2 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-scraper_v1.0.2 succeeded
I1229 22:35:08.545848   12060 cache_images.go:349] CacheImage: registry.cn-hangzhou.aliyuncs.com/google_containers/dashboard:v2.0.0-beta8 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/dashboard_v2.0.0-beta8 completed in 599.889µs
I1229 22:35:08.546228   12060 cache_images.go:89] CacheImage registry.cn-hangzhou.aliyuncs.com/google_containers/dashboard:v2.0.0-beta8 -> /home/wyc/.minikube/cache/images/registry.cn-hangzhou.aliyuncs.com/google_containers/dashboard_v2.0.0-beta8 succeeded
I1229 22:35:08.546239   12060 cache_images.go:96] Successfully cached all images.
🔥  Creating kvm2 VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
I1229 22:35:08.546406   12060 main.go:110] libmachine: Found binary path at /usr/local/bin/docker-machine-driver-kvm2
I1229 22:35:08.546449   12060 main.go:110] libmachine: Launching plugin server for driver kvm2
I1229 22:35:08.560667   12060 main.go:110] libmachine: Plugin server listening at address 127.0.0.1:40699
I1229 22:35:08.561034   12060 main.go:110] libmachine: () Calling .GetVersion
I1229 22:35:08.561648   12060 main.go:110] libmachine: Using API Version  1
I1229 22:35:08.561670   12060 main.go:110] libmachine: () Calling .SetConfigRaw
I1229 22:35:08.561949   12060 main.go:110] libmachine: () Calling .GetMachineName
I1229 22:35:08.562118   12060 main.go:110] libmachine: (minikube) Calling .GetMachineName
I1229 22:35:08.562218   12060 main.go:110] libmachine: (minikube) Calling .DriverName
I1229 22:35:08.562360   12060 main.go:110] libmachine: Reading certificate data from /home/wyc/.minikube/certs/ca.pem
I1229 22:35:08.562390   12060 main.go:110] libmachine: Decoding PEM data...
I1229 22:35:08.562409   12060 main.go:110] libmachine: Parsing certificate...
I1229 22:35:08.562498   12060 main.go:110] libmachine: Reading certificate data from /home/wyc/.minikube/certs/cert.pem
I1229 22:35:08.562517   12060 main.go:110] libmachine: Decoding PEM data...
I1229 22:35:08.562534   12060 main.go:110] libmachine: Parsing certificate...
I1229 22:35:08.562599   12060 main.go:110] libmachine: Running pre-create checks...
I1229 22:35:08.562612   12060 main.go:110] libmachine: (minikube) Calling .PreCreateCheck
I1229 22:35:08.562871   12060 main.go:110] libmachine: (minikube) Calling .GetConfigRaw
I1229 22:35:08.563179   12060 main.go:110] libmachine: Creating machine...
I1229 22:35:08.563194   12060 main.go:110] libmachine: (minikube) Calling .Create
I1229 22:35:08.563274   12060 main.go:110] libmachine: (minikube) Creating KVM machine...
I1229 22:35:08.563950   12060 main.go:110] libmachine: (minikube) Setting up store path in /home/wyc/.minikube/machines/minikube ...
I1229 22:35:08.563972   12060 main.go:110] libmachine: (minikube) Building disk image from file:///home/wyc/.minikube/cache/iso/minikube-v1.6.0.iso
I1229 22:35:08.564060   12060 main.go:110] libmachine: (minikube) DBG | ERROR: logging before flag.Parse: I1229 22:35:08.563939   12116 common.go:99] Making disk image using store path: /home/wyc/.minikube
I1229 22:35:08.564127   12060 main.go:110] libmachine: (minikube) Downloading /home/wyc/.minikube/cache/boot2docker.iso from file:///home/wyc/.minikube/cache/iso/minikube-v1.6.0.iso...
I1229 22:35:08.629835   12060 main.go:110] libmachine: (minikube) DBG | ERROR: logging before flag.Parse: I1229 22:35:08.629759   12116 common.go:106] Creating ssh key: /home/wyc/.minikube/machines/minikube/id_rsa...
I1229 22:35:08.702123   12060 main.go:110] libmachine: (minikube) DBG | ERROR: logging before flag.Parse: I1229 22:35:08.702058   12116 common.go:112] Creating raw disk image: /home/wyc/.minikube/machines/minikube/minikube.rawdisk...
I1229 22:35:08.702151   12060 main.go:110] libmachine: (minikube) DBG | Writing magic tar header
I1229 22:35:08.702205   12060 main.go:110] libmachine: (minikube) DBG | Writing SSH key tar header
I1229 22:35:08.702240   12060 main.go:110] libmachine: (minikube) Setting executable bit set on /home/wyc/.minikube/machines/minikube (perms=drwx------)
I1229 22:35:08.702262   12060 main.go:110] libmachine: (minikube) DBG | ERROR: logging before flag.Parse: I1229 22:35:08.702131   12116 common.go:126] Fixing permissions on /home/wyc/.minikube/machines/minikube ...
I1229 22:35:08.702276   12060 main.go:110] libmachine: (minikube) Setting executable bit set on /home/wyc/.minikube/machines (perms=drwxr-xr-x)
I1229 22:35:08.702292   12060 main.go:110] libmachine: (minikube) DBG | Checking permissions on dir: /home/wyc/.minikube/machines/minikube
I1229 22:35:08.702306   12060 main.go:110] libmachine: (minikube) Setting executable bit set on /home/wyc/.minikube (perms=drwxr-xr-x)
I1229 22:35:08.702322   12060 main.go:110] libmachine: (minikube) Setting executable bit set on /home/wyc (perms=drwxr-xr-x)
I1229 22:35:08.702332   12060 main.go:110] libmachine: (minikube) Creating domain...
I1229 22:35:08.702346   12060 main.go:110] libmachine: (minikube) DBG | Checking permissions on dir: /home/wyc/.minikube/machines
I1229 22:35:08.702360   12060 main.go:110] libmachine: (minikube) DBG | Checking permissions on dir: /home/wyc/.minikube
I1229 22:35:08.702370   12060 main.go:110] libmachine: (minikube) DBG | Checking permissions on dir: /home/wyc
I1229 22:35:08.702383   12060 main.go:110] libmachine: (minikube) DBG | Checking permissions on dir: /home
I1229 22:35:08.702394   12060 main.go:110] libmachine: (minikube) DBG | Skipping /home - not owner
I1229 22:35:08.703238   12060 main.go:110] libmachine: (minikube) KVM machine creation complete!

💣  Unable to start VM. Please investigate and run 'minikube delete' if possible
❌  Error: [KVM_UNAVAILABLE] create: Error creating machine: Error in driver during machine creation: creating domain: error defining domain xml: 

<domain type='kvm'>
  <name>minikube</name> 
  <memory unit='MB'>2000</memory>
  <vcpu>2</vcpu>
  <features>
    <acpi/>
    <apic/>
    <pae/>

  </features>
  <cpu mode='host-passthrough'/>
  <os>
    <type>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
    <bootmenu enable='no'/>
  </os>
  <devices>
    <disk type='file' device='cdrom'>
      <source file='/home/wyc/.minikube/machines/minikube/boot2docker.iso'/>
      <target dev='hdc' bus='scsi'/>
      <readonly/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='default' io='threads' />
      <source file='/home/wyc/.minikube/machines/minikube/minikube.rawdisk'/>
      <target dev='hda' bus='virtio'/>
    </disk>
    <interface type='network'>
      <source network='default'/>
      <mac address='34:39:33:1e:08:ac'/>
      <model type='virtio'/>
    </interface>
    <interface type='network'>
      <source network='minikube-net'/>
      <mac address='a4:e7:9a:69:df:f7'/>
      <model type='virtio'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <rng model='virtio'>
      <backend model='random'>/dev/random</backend>
    </rng>

  </devices>
</domain>

: virError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for domaintype=kvm ')
💡  Suggestion: Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem
📘  Documentation: http://mikko.repolainen.fi/documents/virtualization-with-kvm
⁉️   Related issues:
    ▪ https://github.com/kubernetes/minikube/issues/2991

😿  If the above advice does not help, please let us know: 
👉  https://github.com/kubernetes/minikube/issues/new/choose

it seems that the root cause is 

I1229 22:35:08.371508   12060 start.go:591] status for kvm2: {Installed:true Healthy:false Error:/usr/bin/virsh domcapabilities --virttype kvm failed:
error: failed to get emulator capabilities
error: invalid argument: KVM is not supported by '/usr/bin/qemu-system-x86_64' on this host Fix:Follow your Linux distribution instructions for configuring KVM Doc:https://minikube.sigs.k8s.io/docs/reference/drivers/kvm2/}

⚠️  'kvm2' driver reported an issue: /usr/bin/virsh domcapabilities --virttype kvm failed:
error: failed to get emulator capabilities
error: invalid argument: KVM is not supported by '/usr/bin/qemu-system-x86_64' on this host
kloudd commented 3 years ago

This worked for me. Enabling IOMMU in your GRUB boot parameters. for AMD : GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amd_iommu=on"

for INTEL: GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on"

zioalex commented 3 years ago

I had the same problem and I solved simply restarting libvirtd service.