minikube on Fedora 28 / kvm2 inside VMware Workstation trouble

[stefan.ho...@gmail.com]

Trying to use minikube on Fedora 28 inside VMware Workstation is giving me trouble (i.e. I am trying to run a local kubernetes cluster inside a virtualized Linux guest, within a type 2 hypervisor).

Being totally new to kubernetes, I am looking for guidance on getting two problems fixed in minikube - bug reports / log inspection / setting parameters properly:
a) KVM CPU setup seems to be inappropriate (see steps below)
b) cannot use kubeadm bootstrapper, but am forced to use deprecated localkube

Symptoms:
* minikube config set bootstrapper kubeadm
* minikube start

--> hangs at "Starting cluster components"

This does not happen with localkube - all appears to be well there.

Steps to reproduce:

a) get hypervisor ready
* VMware Workstation 12
* install Fedora 28 Workstation from scratch into fresh .vmx
** .vmx = apic.xapic.enabled = "FALSE"
** .vmx = vhv.enable = "TRUE"

b) install plenty of kvm / libvirt etc from scratch / Fedora repo

c) from minikube 0.28.0 (current) release, download
- minikube-linux-amd64
- docker-machine-driver-kvm2

d) enable nested KVM suppprt

/etc/modprobe.d/kvm.conf
--> options kvm_intel nested=1

d) basic configuration

minikube delete
minikube config set vm-driver kvm2
minikube config set bootstrapper localkube

e)
minikube start

--> dies with

kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

** Problem: minikube dropped in a "bad" CPU.

f) fix the virtual machine created by minikube

virt-manager (minicube VM details)
--> CPU: Copy host CPU configuration
--> save

Hypervisor default CPU may work as well, it seems. Note that I am on Kaby Lake (Intel i7-7500U), and virt-manager does not show that CPU architecture.

g)

minikube start

... success, but with localkube