minikube: hyperv-virtual-switch; startup hangs indefinitely trying to get ip address

Minikube Version: 0.26.1 OS: Windows 10 - 1709 VM Driver: hyperv ISO: minikube-v0.26.0.iso

I am having a similar problem #2425. I am searching through open issues to see if anyone has a work around for my problem. Attempting to use Windows 10/Hyper-v. I have setup a Virtual Switch (external network with Ethernet network adapter). I am using release 0.25.2 to get around #2634. (Update: This morning I updated to 0.26.1)

I run the following command in powershell: minikube start --vm-driver="hyperv" --memory=4096 --hyperv-virtual-switch="My Virtual Switch" --v=7 --alsologtostderr

The script goes along for while. It successfully creates the minikube VM. But then it gets to a point where it continually polls for the vm’s state and ip address. It appears the command to get the network adapter IP address returns nothing. But command to retrieve the state returns “Running”. It does this several times until it just hangs indefinitely.

minikubcreateps

If I then open another powershell instance and do kubectl cluster-info, it initially says Kubernetes master is running at http://localhost:8080 but then receives an error stating it couldn’t connect to target machine because connection has been actively refused.

kubectlclusterinfo

Update: Minikube ssh does not work. But if I connect to the VM via Hyper-V Manager, I can execute curl command and get a webpage, so it does have network connectivity with my Virtual Switch

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 3
  • Comments: 21 (4 by maintainers)

Most upvoted comments

Be sure you can be assigned an IP address on an internal or private virtual switch. hyper-v does not provide a dhcp server on these networks, unless you run one yourself, with the exception of the Default Switch(but this has other shortcomings). The external switch bridges a network adapter. So when on Wireless, use the wirless adapter as bridge, and vice versa. The network you attach to has to provide the DHCP server for assigning an address. Be aware, using a VPN can cause issues as they tend to route all, which means the DHCP request will not be received.