In my case, I required KVM2; since it's native to linux. The process of doing this was: * Ensure you have libvirt/qemu installed. * Make sure you're a member of the libvirt group * Get https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-kvm2 * make it executable and put it in path: `chmod 700 docker-machine-driver-kvm2 && mv docker-machine-driver-kvm2 ~/bin` in my case. It'd be good to have these drivers made available by flags, IMHO. Reference: https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#kvm2-driver
Ah! Just found out that docker-machine-kvm exists in portage; just not docker-machine-kvm2. Maybe it's just a matter of updating that one and adding a soft dependency?
(In reply to Renich Bon Ciric from comment #1) > Ah! Just found out that docker-machine-kvm exists in portage; just not > docker-machine-kvm2. Maybe it's just a matter of updating that one and > adding a soft dependency? I struggled with the same problems and came up with bug #660304 - please contribute if you know how to make the kvm thingy work, I'd love to stop using vbox!
(In reply to Holger Hoffstätte from comment #2) > I struggled with the same problems and came up with bug #660304 - > please contribute if you know how to make the kvm thingy work, > I'd love to stop using vbox! I think you just need to set it to use kvm2, no? I have these settings. They might help: $ cat .minikube/config/config.json { "WantReportError": true, "coredns": true, "cpus": 8, "heapster": true, "ingress": true, "memory": 16000, "metrics-server": true, "vm-driver": "kvm2" }
Please check with recent version of minikube and report back if this issue still exists.
