no External vswitch found. A valid vswitch must be available for this command to run

[jpthirumalai]

The exact command to reproduce the issue:
minikube start --vm-driver=hyperv

The full output of the command that failed:

C:\WINDOWS\system32>minikube start --vm-driver=hyperv

• minikube v1.3.1 on Microsoft Windows 10 Pro 10.0.17763 Build 17763
• Creating hyperv VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
  E0821 10:53:20.324513 108332 start.go:723] StartHost: create: precreate: no External vswitch found. A valid vswitch must be available for this command to run. Check https://docs.docker.com/machine/drivers/hyper-v/

X Unable to start VM

• Error: [HYPERV_NO_VSWITCH] create: precreate: no External vswitch found. A valid vswitch must be available for this command to run. Check https://docs.docker.com/machine/drivers/hyper-v/
• Suggestion: Configure an external network switch following the official documentation, then add --hyperv-virtual-switch=<switch-name> to minikube start
• Documentation: https://docs.docker.com/machine/drivers/hyper-v/
• If the above advice does not help, please let us know:
  • https://github.com/kubernetes/minikube/issues/new/choose

C:\WINDOWS\system32>

The output of the minikube logs command:

The operating system version:
Microsoft Windows [Version 10.0.17763.678]

[nascarj]

Did you create the external switch in hyperv?
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/create-a-virtual-switch-for-hyper-v-virtual-machines

[sharifelgamal]

Yes, you need to create an external switch in Hyper-V as specified in the documentation in @speedysocks30 comment, and then specify the name of the switch in minikube start with the --hyperv-virtual-switch parameter.

[jpthirumalai]

Yes I did, created an External switch through HyperV Manager, after seeing few resolved posts. Even then it was not working.

…

On Wed, Aug 21, 2019, 11:23 PM Sharif Elgamal ***@***.***> wrote: Yes, you need to create an external switch in Hyper-V as specified in the documentation in @speedysocks30 <https://github.com/speedysocks30> comment, and then specify the name of the switch in minikube start with the --hyperv-virtual-switch parameter. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5154?email_source=notifications&email_token=AF6MIIOLUZGETRV64BXWWVLQFV6IRA5CNFSM4IOBXEPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD42SJSI#issuecomment-523576521>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF6MIIORC4NAFZMF5SRSKYTQFV6IRANCNFSM4IOBXEPA> .

[tstromberg]

@jpthirumalai - Do you mind sharing the output of this PowerShell command:

Get-VMSwitch -SwitchType External

I would also like to see the command-line you use that includes --hyperv-virtual-switch, as well as the output of it. Thanks!

[jpthirumalai]

Get-VMSwitch -SwitchType External

Name        SwitchType NetAdapterInterfaceDescription
----        ---------- ------------------------------
switch4kube External   Intel(R) Ethernet Connection (4) I219-LM

Command used to start

minikube start --vm-driver=hyperv --hyperv-virtual-switch=switch4kue

And the output is

minikube v1.3.1 on Microsoft Windows 10 Pro 10.0.17763 Build 17763
Creating hyperv VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
E0821 10:53:20.324513 108332 start.go:723] StartHost: create: precreate: no External vswitch found. A valid vswitch must be available for this command to run. Check https://docs.docker.com/machine/drivers/hyper-v/

[jpthirumalai]

Tried steps from resolved issue #1221
Also highlighted in One other Site
Summary:
1, Open "Window Security"
2, Open "App & Browser control"
3, Click "Exploit protection settings" at the bottom
4, Switch to "Program settings" tab
5, Locate "C:\WINDOWS\System32\vmcompute.exe" in the list and expand it
6, Click "Edit"
7, Scroll down to "Code flow guard (CFG)" and uncheck "Override system settings"
8, Start vmcompute from powershell "net start vmcompute"


But not working for me

[tstromberg]

@jpthirumalai - Is it possible that there is a typo in your minikube command? I noticed it says switch4kue, whereas the name appears to be switch4kube?

[tstromberg]

@author: I believe this issue is now addressed by minikube v1.4, as it no longer requires an external virtual switch. If you still see this issue with minikube v1.4 or higher, please reopen this issue by commenting with /reopen

Thank you for reporting this issue!

[aditya-bhuyan]

/reopen

Find this issue in latest version of minikube 1.4.0

[k8s-ci-robot]

@aditya-bhuyan: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Find this issue in latest version of minikube 1.4.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Septem151]

/reopen

This issue is present in v1.12.0

[k8s-ci-robot]

@Septem151: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

This issue is present in v1.12.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.