minishift: Minishift unable to start Hyper-V on Windows 10 when PowerShell not on PATH (missing pre-flight)
General information
- Minishift version: minishift v1.31.0+cfc599c
- OS: Linux / macOS / Windows : Windows 10
- Hypervisor: KVM / xhyve / Hyper-V / VirtualBox : Hyper-V
Everything being run as administrator and user is a part of HYPERV Admins and Administrator group both.
Steps to reproduce
- minishift config set hyperv-virtual-switch hypervext
Expected
Should work
Actual
[Virtual Switch not found]
Also Minishift Starts gives below
c:\minishift>minishift start – Starting profile ‘minishift’ – Check if deprecated options are used … OK – Checking if https://github.com is reachable … OK – Checking if requested OpenShift version ‘v3.11.0’ is valid … OK – Checking if requested OpenShift version ‘v3.11.0’ is supported … OK – Checking if requested hypervisor ‘hyperv’ is supported on this platform … OK – Checking if Hyper-V driver is installed … FAIL See the ‘Setting Up the Virtualization Environment’ topic (https://docs.okd.io/latest/minishift/getting-started/setting-up-virtualization-environment.html) for more information
Power Shell Output PS C:\minishift> (Hyper-V\Get-VMSwitch).Name hypervext DockerNAT Default Switch
Logs
You can start Minishift with minishift start --show-libmachine-logs -v5 to collect logs.
Please consider posting this on http://gist.github.com/ and post the link in the issue.
** Logs are not seen in the current minishift folder when running above command. Where can this be located ?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 30 (16 by maintainers)
Commits related to this issue
- Issue #3170 Add preflight check for powershell and fix vmms check — committed to anjannath/minishift by anjannath 5 years ago
- Issue #3170 Add preflight check for powershell and fix vmms check — committed to minishift/minishift by anjannath 5 years ago
Administrator and being part of the Hyper-V Admins is not the same thing. This is an explicit setting that needs to be made. Can you run the
setupcommand with admin rights?