minikube start with hyper-v won't resolve guest ip-address

[a3nick]

BUG REPORT

Executing minikube start --vm-driver="hyperv" --hyperv-virtual-switch="ext1", where ext1 is my external virtual switch on hyper-v, the system hangs on "Starting VM" message.
Checking the log it seems that the powershell command used to retireve the ip address of the guest machine don't returns any value (i tested running the command on a separate powershell with the same result).
I obtained the same result on two different machines.

Environment:

Minikube version: v0.22.0

• OS: Windows 10x64 - 1703
• VM Driver: hyper-v
• ISO version: -v0.23.3
• Install tools: kubectl & minikube installed using chocolatey packages

Output of minikube logs:

[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM minikube ).networkadapters[0]).ipaddresses[0]
[stdout =====>] :
[stderr =====>] :

[mikemcgo]

It looks like hv_kvp_daemon isn't running by default in the vm. This is the daemon that allows the guest os to communicate with the host. If you start it manually (/usr/sbin/hv_kvp_daemon), the ip shows up in hyperv manager. I think its a bug that it isn't starting by default.

[richardjharding]

I can confirm this with 0.22.1 and hyperv on windows 10

Tried starting hv_kvp_daemon as suggested but the vm still doesn't seem to get an ip

any suggestions?

[a3nick]

I obtained the same result running the daemon, the ip address isn't returned

[richardjharding]

Does anyone know if this is a new bug - is there an earlier version that works?

[vcx]

Same issue here. minikube vm starts, external virtual switch configured OK, and I have an IP address that I can verify from inside the VM. From outside, I got the powershell command that minikube is trying to execute via procmon, and it matches the same posted in the first message of this issue.

Also, kvp service failed to start (as verified with systemctl status hv_kvp_daemon.service). The output says that KVP service started and one second later process exited, status=1/FAILURE. Unit entered failed state.

I've studied how systemctl works, found the command line, ran it and it worked. Tried to start the hv-kvp manually using systemctl and it worked too. After some seconds, I could see the IP address in the powershell command... but minikube still hangs on the "Waiting for SSH to be available".

with Procmon, I found that minikube is looping trying to connect to port 22 on my own address. As a test, tried to run again using a new, different switch. Added an Internal switch (in hyper-v world, this means no internet, vm and physical machine can communicate) and set static IPs from my physical machine and the VM (192.168.20.1 an 2, respectively). Then, ran the minikube start command again. Crossed that point, but now got looping while configuring the VM... looks like docker service doesn't start.

Now it looks like I have a different problem, and will open a different issue later. But I hope this troubleshooting info helps your case too.

[richardjharding]

thanks I get something similar after starting the hv_kvp daemon using systemctl as you suggest

This is the output I see in powershell admin session

[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM minikube
 ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM minikub
e ).networkadapters[0]).ipaddresses[0]
[stdout =====>] : 192.168.1.244

[stderr =====>] :
SSH binary not found, using native Go implementation
&{{{<nil> 0 [] [] []} docker [0x8526f0] <nil>  [] 0s} 192.168.1.244 22 <nil> <nil>}
About to run SSH command:
sudo systemctl -f restart docker
SSH cmd err, output: Process exited with status 1: Job for docker.service failed because the control process exited with
 error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

[a3nick]

It works with minikube version v0.22.2 and ISO v0.23.4

[vcx]

Confirmed working. Thank you very much, guys!

[ryegrass2003]

seems I have the same issue with v0.24.1
windows 10 pro hyperv

Error starting host: Error starting stopped host: exit status 1