<p>When trying to run <code>minikube</code> with hyperkit, I was getting errors about xhyve not being installed. I installed that and reran <code>minikube start --vm-driver hyperkit</code> with no issues.</p>

<p>I was under the impression that hyperkit was a replacement for xhyve, not a supplement to it.</p>

<p>When I run <code>ps</code> I see both <code>com.docker.hyperkit</code> and <code>docker-machine-driver-xhyve</code> running.</p>

<p>How can I confirm that minikube is correctly using hyperkit?</p>

<p><a href="https://www.docker.com/docker-mac" rel="noreferrer">Docker for Mac</a> changed virtualization layer few times last years, and it can confuse users after updates of environment.</p>

<p>If the process list shows both <a href="https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#hyperkit-driver" rel="noreferrer">com.docker.hyperkit</a> and <a href="https://github.com/mist64/xhyve" rel="noreferrer">xhyve</a> processes is probably due
to docker-machine environment which was previously set up using <a href="https://github.com/machine-drivers/docker-machine-driver-xhyve" rel="noreferrer">docker-machine-driver-xhyve</a>.</p>

<p>You may consider cleaning up installation by</p>

<ul>
<li>stopping Docker (from command line or from tray icon),</li>
<li>next removing machines created by <code>docker-machine</code> tool. </li>
</ul>

<p>I can also suggest to remove current minikube installation using</p>

<pre><code>minikube stop &amp;&amp; minikube delete
</code></pre>

<p>and start fresh one with: </p>

<pre><code>minikube start --v=10 --vm-driver=hyperkit" 
</code></pre>

<p>That will add additional verbose output of building minikube environment.</p>
