minikube: minikube not starting on Windows 10 with Hyper-V

Quick summary for those seeing similar issues:

First create a vSwitch in Hyper-V

• type: external
• name: Minikube (or anything you like)
• make sure to associate the vSwitch with the correct NIC
• reboot after creating the vSwitch just in case (routing tables, …)
• go take a look at the network devices on your Windows host to make sure that you have a Virtual Ethernet Adapter configured and actually connected to your network
  • Control Panel\Network and Internet\Network Connections. In my case i have: “vEthernet (Minikube)”

Once done make sure to start clean, remove ~/.minikube and remove any VM you tried to create before.

Once you’re ready, make it happen:

minikube start --vm-driver "hyperv" --hyperv-virtual-switch "Minikube" --disk-size 10g --memory 4096 --v 9999 --alsologtostderr

I had the same behavior, but due to 2 reasons:

1. First, I did not have enough disk space on drive C: for the HyperV machine (<1.75GB left). Even if my HyperV is set to store the VMs on D:, the minikube scripts are still using drive C: regardless of that setting. Didn’t dig too much into this, just freed some space.
2. The HyperV virtual switch was set to Internal. After I set it to external, everything worked. So, please create a virtual switch in HyperV, set it to External, name it “minikube-switch” or whatever else, and use “minikube start --vm-driver=hyperv --hyperv-virtual-switch=minikube-switch”

Now I am experiencing some CPU overusage by minikube, but that’s a different topic 😃 So it’s still fun 😃 I hope this helps.

Had the same issue, fixed by selecting the correct NIC, purging all caches (basically rm ~/.minikube/) and then running minikube start again, with the correct flags. Thank you @dsebastien !

Had the same issue, fixed by not setting the virtual switch.

Here, the cluster will not get external IP, because the DHCP server only provides addresses to registered devices. So the external switch is actually guaranteed to break everything.

I have tried @dsebastien suggestions but did not work on my case. I’m still running into issues with “crio”.

Using SSH client type: native &{{{<nil> 0 [] [] []} docker [0x83feb0] 0x83fe60 [] 0s} fe80::215:5dff:fec8:6412 22 <nil> <nil>} About to run SSH command: sudo systemctl -f restart crio SSH cmd err, output: Process exited with status 1: Job for crio.service failed because the control process exited with e rror code. See “systemctl status crio.service” and “journalctl -xe” for details.

Error setting container-runtime options during provisioning ssh command error: command : sudo systemctl -f restart crio err : Process exited with status 1 output : Job for crio.service failed because the control process exited with error code. See “systemctl status crio.service” and “journalctl -xe” for details.

E1211 15:33:45.206964 6120 start.go:150] Error starting host: Error creating host: Error executing step: Provisioning VM. : ssh command error: command : sudo systemctl -f restart crio err : Process exited with status 1 output : Job for crio.service failed because the control process exited with error code. See “systemctl status crio.service” and “journalctl -xe” for details. .

Retrying. E1211 15:33:45.227177 6120 start.go:156] Error starting host: Error creating host: Error executing step: Provisionin g VM. : ssh command error: command : sudo systemctl -f restart crio err : Process exited with status 1 output : Job for crio.service failed because the control process exited with error code. See “systemctl status crio.service” and “journalctl -xe” for details.

minikube version: v0.24.1

Any other suggestions? I have tried almost everything I could find on the net.

Thank you

@dsebastien Thanks the detailed fix -I was able to get mine running after reading the post above. Clearing out the ./minikube was the kicker for me.