sandervanvugt / ckad Goto Github PK

Hi Sander,
I hit an issue which may not be a new one (seems like it is was also present in version 18.04). I did not find a solution to it, but there is a workaround easy to implement.

For the record, I did enabled the nested virtualization.

Here is some details:

I have tested this on ESXi 6.7U2 and Workstation 15.5.6. On both cases I have the following error while starting the minikube:

🤦 StartHost failed, but will try again: driver start: error creating VM: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2020-11-02T23:50:21.143363Z qemu-system-x86_64: error: failed to set MSR 0xe1 to 0x0
qemu-system-x86_64: /build/qemu-w04YJX/qemu-4.2/target/i386/kvm.c:2691: kvm_buf_set_msrs: Assertion ret == cpu->kvm_msr_buf->nmsrs' failed.') 🔄 Restarting existing kvm2 VM for "minikube" ... 😿 Failed to start kvm2 VM. Running "minikube delete" may fix it: driver start: error creating VM: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2020-11-02T23:50:28.595167Z qemu-system-x86_64: error: failed to set MSR 0xe1 to 0x0 qemu-system-x86_64: /build/qemu-w04YJX/qemu-4.2/target/i386/kvm.c:2691: kvm_buf_set_msrs: Assertion ret == cpu->kvm_msr_buf->nmsrs' failed.')

❌ Exiting due to PR_KVM_MSR: Failed to start host: driver start: error creating VM: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2020-11-02T23:50:28.595167Z qemu-system-x86_64: error: failed to set MSR 0xe1 to 0x0
qemu-system-x86_64: /build/qemu-w04YJX/qemu-4.2/target/i386/kvm.c:2691: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.')
💡 Suggestion: Upgrade to QEMU v3.1.0+, run 'virt-host-validate', or ensure that you are not running in a nested VM environment.
🍿 Related issue: kubernetes/minikube#4277

After trying to fix it for few hours, turns out either there is no solution, or I was unable to find it.

I decided to follow a solution which propose to use the virtualbox driver instead:

nandonov@ckad:/repos/ckad$ sudo apt install virtualbox virtualbox-ext-pack
nandonov@ckad:/repos/ckad$ minikube delete
nandonov@ckad:/repos/ckad$ minikube config unset vm-driver
nandonov@ckad:/repos/ckad$ minikube config set driver virtualbox
nandonov@ckad:/repos/ckad$ minikube start

Source: https://stackoverflow.com/a/52662398/7227497

It worked right the way, the virtual machine creation took some time but eventually it get up and running after few minutes.

I hope this information will help other people save some time!
Have a great day!

Nikolay Andonov

Hi,

I am getting the following error message when I try to execute the following command "kubectl create -f traefik-in.yaml", would you please advise

resource mapping not found for name: "traefik-web-ui" namespace: "kube-system" from "traefik-in.yaml": no matches for kind "Ingress" in version "extensions/v1beta1"
ensure CRDs are installed first

Greetings Sander! Please potentially have a message before the (reboot) message in the fedora Kube setup script to have the user
usermod -a -G libvirt USERIDrunningMinikube