HyperV network instability: wsarecv: An existing connection was forcibly closed by the remote host

[QAnders]

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Please provide the following details:

Environment: Hyper-V on Windows 10 Enterprise version: 1709

Minikube version (use minikube version): v0.25.2

• OS (e.g. from /etc/os-release):
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName):
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
• Install tools:
• Others:
  The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):

minikube version
echo "";
echo "OS:";
cat /etc/os-release
echo "";
echo "VM driver": 
grep DriverName ~/.minikube/machines/minikube/config.json
echo "";
echo "ISO version";
grep -i ISO ~/.minikube/machines/minikube/config.json

What happened: I setup minikube according to this guide: https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c
After creating the virtual switch I see a decrease in Internetspeeds but still working. Minukube VM is created and I can see that it starts and connect to it but trying to start any applications, e.g. minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch" it starts working and gets an IP and starts downloading but soon stops with the following error:
Downloading localkube binary 1.16 MB / 163.02 MB [>---------------------------------------] 0.71% 5h10m46s E0413 07:22:58.427478 13424 start.go:234] Error updating cluster: Error updating localkube from uri: Error attempting to download and cache localkube: downloading localkube: failed to download: failed to download to temp file: failed to copy contents: read tcp 192.168.1.18:54897->216.58.207.208:443: wsarecv: An existing connection was forcibly closed by the remote host. E0413 07:22:58.466277 13424 util.go:151] Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: dial tcp: lookup clouderrorreporting.googleapis.com: no such host

What you expected to happen: For it to download and start the Kube env.

How to reproduce it (as minimally and precisely as possible):

Output of minikube logs (if applicable):

Anything else do we need to know: As stated I get the impression the whole Internet connection on the hosts is also "slowed down" but working...

[shyyawn]

I have the same issue of internet slowing down. Can you help?

[discosultan]

I had a similar issue when I created a new external virtual switch. However, using the "Default Switch" for Minikube's VM does not pose that problem.

[ghettosamson]

I used the same link to setup minikube. After creating the "Primary Virtual Switch" internet speeds completely slowed down. I had to delete the created switch and use the "Default Switch".

[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

[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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

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

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.