minikube: hyperkit macOS catalina: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

I am unable to start minikube with hyperkit on mac OS Catalina. I was able to run minikube before upgrading to Catalina.

The exact command to reproduce the issue:

minikube stop && minikube delete && minikube start --vm-driver=hyperkit

The full output of the command that failed:

✋ Stopping “minikube” in virtualbox … 🛑 “minikube” stopped. 🔥 Deleting “minikube” in virtualbox … 💔 The “minikube” cluster has been deleted. 😄 minikube v1.4.0 on Darwin 10.15 🔥 Creating hyperkit VM (CPUs=4, Memory=8192MB, Disk=20000MB) … 🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥 Deleting “minikube” in hyperkit … E1010 22:01:41.581336 38132 main.go:100] libmachine: (minikube) Error reading pid file: open /Users/ashkanaleali/.minikube/machines/minikube/hyperkit.json: no such file or directory 🔥 Creating hyperkit VM (CPUs=4, Memory=8192MB, Disk=20000MB) … 🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥 Deleting “minikube” in hyperkit … E1010 22:01:49.012099 38132 main.go:100] libmachine: (minikube) Error reading pid file: open /Users/ashkanaleali/.minikube/machines/minikube/hyperkit.json: no such file or directory 🔥 Creating hyperkit VM (CPUs=4, Memory=8192MB, Disk=20000MB) … 🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥 Deleting “minikube” in hyperkit … E1010 22:01:58.676325 38132 main.go:100] libmachine: (minikube) Error reading pid file: open /Users/ashkanaleali/.minikube/machines/minikube/hyperkit.json: no such file or directory 🔥 Creating hyperkit VM (CPUs=4, Memory=8192MB, Disk=20000MB) … 🔄 Retriable failure: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥 Deleting “minikube” in hyperkit … E1010 22:02:14.547227 38132 main.go:100] libmachine: (minikube) Error reading pid file: open /Users/ashkanaleali/.minikube/machines/minikube/hyperkit.json: no such file or directory

💣 Unable to start VM: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: 👉 https://github.com/kubernetes/minikube/issues/new/choose

The output of the minikube logs command:

💣 api load: filestore “minikube”: Docker machine “minikube” does not exist. Use “docker-machine ls” to list machines. Use “docker-machine create” to add a new one.

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: 👉 https://github.com/kubernetes/minikube/issues/new/choose

The operating system version: mac OS 10.15

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 32 (11 by maintainers)

Most upvoted comments

Hmm… I also had internet sharing turned on and got this issue. I wonder if that’s the root cause of the issue? None of my co-workers were running into it.

mglidden on Mar 16, 2020

Same in 2021 on BigSur 😞

$ docker -v
Docker version 20.10.2, build 2291f61
$ hyperkit -v
hyperkit: 0.20200908

Homepage: https://github.com/docker/hyperkit
License: BSD

$ minikube start --driver=hyperkit
😄  minikube v1.17.1 on Darwin 11.2.1
✨  Using the hyperkit driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating hyperkit VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
🔥  Deleting "minikube" in hyperkit ...
🤦  StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥  Creating hyperkit VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
😿  Failed to start hyperkit VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1


❌  Exiting due to PR_HYPERKIT_VMNET_FRAMEWORK: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

💡  Suggestion: Hyperkit networking is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --driver
🍿  Related issues:
    ▪ https://github.com/kubernetes/minikube/issues/6028
    ▪ https://github.com/kubernetes/minikube/issues/5594

frnhr on Feb 18, 2021

I seem to also get this problem on the latest version of hyperkit when my mac’s internet sharing is turned on and in use

BoKleynen on Mar 16, 2020

Try deleting the /Users/ashkanaleali/.minikube directory and start minikube again and see if that helps

nanikjava on Oct 11, 2019

Did anyone found a solution to this issue?

@cglacet Are you sharing Internet in System Preferences?

Just ran into this issue locally on Big Sur 11.6, but the solution ended up being to disable Internet Sharing:

Hmm… I also had internet sharing turned on and got this issue. I wonder if that’s the root cause of the issue? None of my co-workers were running into it.

Logs looked like this

minikube start                                                                                                       [15:48:04]
😄  minikube v1.23.2 on Darwin 11.6
✨  Using the hyperkit driver based on user configuration
💾  Downloading driver docker-machine-driver-hyperkit:
    > docker-machine-driver-hyper...: 65 B / 65 B [----------] 100.00% ? p/s 0s
    > docker-machine-driver-hyper...: 10.53 MiB / 10.53 MiB  100.00% 183.79 MiB
🔑  The 'hyperkit' driver requires elevated permissions. The following commands will be executed:

    $ sudo chown root:wheel /Users/gabizou/.minikube/bin/docker-machine-driver-hyperkit
    $ sudo chmod u+s /Users/gabizou/.minikube/bin/docker-machine-driver-hyperkit


Password:
💿  Downloading VM boot image ...
    > minikube-v1.23.1.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
    > minikube-v1.23.1.iso: 225.22 MiB / 225.22 MiB  100.00% 33.91 MiB p/s 6.8s
👍  Starting control plane node minikube in cluster minikube
🔥  Creating hyperkit VM (CPUs=4, Memory=6144MB, Disk=20000MB) ...
🔥  Deleting "minikube" in hyperkit ...
🤦  StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

🔥  Creating hyperkit VM (CPUs=4, Memory=6144MB, Disk=20000MB) ...
😿  Failed to start hyperkit VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1


❌  Exiting due to PR_HYPERKIT_VMNET_FRAMEWORK: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1

💡  Suggestion: Hyperkit networking is broken. Upgrade to the latest hyperkit version and/or Docker for Desktop. Alternatively, you may choose an alternate --driver
🍿  Related issues:
    ▪ https://github.com/kubernetes/minikube/issues/6028
    ▪ https://github.com/kubernetes/minikube/issues/5594

After disabling Internet Sharing (was in a predicament where I needed to share ethernet to another set of devices), re-running minikube start worked just fine:

minikube start                                                                                                       [15:48:31]
😄  minikube v1.23.2 on Darwin 11.6
✨  Using the hyperkit driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🔄  Restarting existing hyperkit VM for "minikube" ...
🐳  Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
🔎  Verifying Kubernetes components...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟  Enabled addons: storage-provisioner, default-storageclass
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

gabizou on Oct 9, 2021