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

[jwgain0]

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.

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.

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

[jwgain0]

Posting My Virtual Switch Settings just to ensure they are correct:

[jwgain0]

I have figured out that it is something to do with the ps command:
C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Hyper-V\Get-VM minikube ).networkadapters[0]).ipaddresses[0]

If I remove the array index identifier from ipaddresses, it will successfully return the array object
C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Hyper-V\Get-VM minikube ).networkadapters[0]).ipaddresses
Result
IP address
Mac address

If I tell it to give me the item at index 1 it will give the mac address:
C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Hyper-V\Get-VM minikube ).networkadapters[0]).ipaddresses[1]
Result: Mac Address

But giving it the index at 0 the result is an empty string. Very bizarre.

[jwgain0]

I have a potential solution. If you pass the -Command flag and wrap the command in the quotes you get the expected output

C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive -Command "(( Hyper-V\Get-VM minikube ).networkadapters[0]).ipaddresses[0]"

I could clone the project and change the command and if it works make a pull request. However I haven't seen any instructions on how to build the windows executable.

Would anyone be able to help me with what steps I should take to do this? @gbraad I have seen that you are a collaborator and commented on several issues. What do you think about this issue?

FYI Powershell Version 5.1.16299.251

[jwgain0]

I cloned the repo and changed the following code in on line 28 of /vendors/docker/machine/drivers/hyperv/powershell.go

Orig:
'args = append([]string{"-NoProfile", "-NonInteractive"}, args...)'

New:
'args = append([]string{"-NoProfile","-NonInteractive", "-Command"}, "\"", args..., "\""
)'

I try to make on a Ubuntu VM and the make fails because it can't find the package "context" referenced in /vendor/k8s.io/apimachinery/pkg/util/wait/wait.go

[jwgain0]

Just wanted to Bump this up. I am still experiencing this issue and haven't got any response.

[robbie-demuth]

I haven't dug as deep as jwgain0, but I seem to be experiencing the same issue. Whenever I run minikube start ... the console cycles through the following output, but the command never completes successfully:

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

[stderr =====>] :

[beingamarnath]

+1, even i'm stuck with the same error

[cwroble]

+1 same issue. I am using this cmd:
minikube start --vm-driver=”hyperv” –-hyperv-virtual-switch=”MiniKubeNAT” --cpus=3 --memory=10240

[dejandb]

@jwgain0 @beingamarnath @cwroble - I had issues with 0.27 (have yet to try 0.28 or 0.28.1) so ended up downgrading to 0.26.2 and after the initial VM creation I let the script run for a while, stop the script, VM and then change the virtual switch back to a local switch.

Then again run "minikube start" with no arguments and everything works correctly.

Ideally the switch will not be required and just optional as mentioned in the documentation but it is a required argument and the script checks that it is external at VM creation time.

[bartvanhoutte]

+1