Takes 95 seconds to stop a xhyve VM

[ahmetb]

A simple minikube stop just took 95 seconds.

This is a relatively fresh/empty VM. I only ran:

• minikube start --container-runtime=containerd --docker-opt containerd=/var/run/containerd/containerd.sock

• minikube addons enable gvisor

• kubectl logs

• minikube stop (took 95s.)

The exact command to reproduce the issue: minikube stop (xhyve driver)

The full output of the command that failed took too long:

Output

[23:31:16] ~ $ minikube stop
✋  Stopping "minikube" in xhyve ...
🛑  "minikube" stopped.
[23:32:51] ~ $ <--

The output of the minikube logs command:

minikube logs

N/A – host stopped

The operating system version: 10.14.5 (18F132)
minikube version: 1.2
minikube addons: gvisor

[medyagh]

Thank you for creating this issue, 95 seconds is not acceptable for waiting to stop. Btw I am curious is there a specific reason to use xhyve driver ? We have depricated support for that driver. But I am curious if there is any advantage of using xhyve to hyperkit ?

[ahmetb]

Mostly gMac compliance I think. Or maybe I’ve been using minikube since far too long. I should try the hyperkit option. Thanks.

[medyagh]

We are working on VM free minikube for all platforms, with that coming it will speed up super fast !

[ahmetb]

That sounds dope but I have no idea how would it work :P

[tstromberg]

For "gmac compliance", I suggest just installing hyperkit from brew.

[ahmetb]

Yeah, I think we can close this I suspect xhyve is going to be removed.