Hyper-V modules need to be invoked with correct case

[gbraad]

minikube/vendor/github.com/docker/machine/drivers/hyperv/hyperv.go

Line 131 in a000c35

stdout, err := cmdOut("(", "hyper-v\\Get-VM", d.MachineName, ").state")

and others

this needed to be fixed with:

-	stdout, err := cmdOut("(", "hyper-v\\Get-VM", d.MachineName, ").state")
+	stdout, err := cmdOut("(", "Hyper-V\\Get-VM", d.MachineName, ").state")

else issues occured on the pre-create check

Full change can be seen in docker/machine#4426

[gbraad]

It is hard to track which version you actually have merged, but it seems it is somewhere after 0.14.0 ?

AFAIR this is only used in Docker for Windows/Mac edge releases. /cc: @dlorenc

[saitho]

The bugfix in docker-machine is currently only in the master branch and has not been released in a version yet... I'm currently getting the error "Hyper-V PowerShell Module is not available" when I'm trying to start Minikube (for the first time) on my Windows computer with Hyper-V enabled.

I compiled docker-machine from the master branch, but still can't start up Minikube. ^^ (The issue described on the docker-machine project works fine now).

[saitho]

I solved the issue locally and recompiled minikube. Seems to work fine now.
However I did not decide to open a PR for that as I'm pretty new to Go and I have no idea about how dependency management exactly works... For now I just adjusted the files in the vendor/ directory. ^^

I can confirm that the problem described in #2634 is solved with that. I was able to start Minikube successfully on my Windows computer with Hyper-V enabled.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close