crc: [BUG] Error getting MAC address from UUID on macOS with hyperkit

General information

  • OS: macOS
  • Hypervisor: hyperkit
  • Did you run crc setup before starting it? Yes

CRC version

# Put `crc version` output here

CRC status

Machine 'crc' does not exist. Use 'crc start' to create it.

CRC config

Host Operating System

ProductName:	Mac OS X
ProductVersion:	10.15.1
BuildVersion:	19B88

Steps to reproduce

  1. crc start

Expected

CRC to start

Actual

CRC fails with following error:

ERRO Error creating host: Error creating the VM: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1 

Logs

crc start -p ~/Downloads/pull-secret --log-level debug    
DEBU Unable to find out if a new version is available: Get https://mirror.openshift.com/pub/openshift-v4/clients/crc/latest/release-info.json: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) 
INFO Checking if running as non-root              
INFO Checking if oc binary is cached              
DEBU oc binary already cached                     
INFO Checking if HyperKit is installed            
DEBU Checking if hyperkit is installed            
INFO Checking if crc-driver-hyperkit is installed 
DEBU Checking if crc-driver-hyperkit is installed 
DEBU crc-driver-hyperkit is already installed in /Users/arthurbarr/.crc/bin/crc-driver-hyperkit 
INFO Checking file permissions for /etc/resolver/testing 
INFO Checking file permissions for /etc/hosts     
Checking file: /Users/arthurbarr/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_hyperkit_4.2.8.crcbundle ... 
INFO Creating CodeReady Containers VM for OpenShift 4.2.8... 
Found binary path at /Users/arthurbarr/.crc/bin/crc-driver-hyperkit
Launching plugin server for driver hyperkit
Plugin server listening at address 127.0.0.1:63732
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(crc) Calling .GetMachineName
(crc) Calling .DriverName
Running pre-create checks...
(crc) Calling .PreCreateCheck
(crc) DBG | exe=/Users/arthurbarr/.crc/bin/crc-driver-hyperkit uid=0
(crc) Calling .GetConfigRaw
Creating machine...
(crc) Calling .Create
(crc) DBG | exe=/Users/arthurbarr/.crc/bin/crc-driver-hyperkit uid=0
(crc) Downloading /Users/arthurbarr/.crc/cache/crc.disk from file:///Users/arthurbarr/.crc/cache/crc_hyperkit_4.2.8/crc.qcow2...
(crc) DBG | exe=/Users/arthurbarr/.crc/bin/crc-driver-hyperkit uid=0
(crc) DBG | clean start, hyperkit pid file doesn't exist: /Users/arthurbarr/.crc/machines/crc/hyperkit.pid
(crc) DBG | Using hyperkit binary from /Users/arthurbarr/.crc/bin/hyperkit
(crc) DBG | Using UUID c3d68012-0208-11ea-9fd7-f2189899ab08
(crc) DBG | virtio_net: Could not create vmnet interface, permission denied or no entitlement?
ERRO Error creating host: Error creating the VM: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1 
Making call to close driver server
(crc) Calling .Close
Successfully made call to close driver server
Making call to close connection to plugin binary
(crc) DBG | Closing plugin on server side

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 50 (19 by maintainers)

Most upvoted comments

@gbraad I followed the documentation when I was installing crc first time. But then I got some issue and after searching on google, I ended up at this ticket.

Based on your suggestion in the last comment, I followed the following steps. crc cleanup rm -rf ~/.crc crc setup crc start --log-level debug

After doing all this, I received again the same error log mentioned in comment

Before running above steps, I manually checked that there wasn’t any process running with hyperkit and my internet sharing is switched off already.

I had the same issue today, I followed the steps in https://github.com/code-ready/crc/issues/882#issuecomment-564363049, but had the same error.

after reading other comments here, I restarted my macOS, followed by

$ rm ~/.crc
$ crc setup
$ crc start

worked for me.

I was also running into this same issues, which the crc start stuck trying to SSH for long time https://github.com/code-ready/crc/issues/1033. But it got fixed somehow I don’t see it happening now.

Just ran into this issue on a fresh install of crc 1.13. This comment https://github.com/code-ready/crc/issues/882#issuecomment-637535245 worked for me, though I didn’t need to install a new version of hyperkit. I just needed to copy the newer on over to ~/crc/.bin and to kill the running hyperkit (which crashed docker desktop) but allowed crc start to work.

Just to mention that somehow I got this issue in version 1.11.0 but got past it with Aenima4six2’s comment

Comment above mentions issue moby/hyperkit#263 but that has been merged 3 months ago and I am on latest patch level of Mac OS, but realised my version of hyperkit failry outdated:

hyperkit -v
hyperkit: v0.20180403-36-ge3b37f

Moved to latest available from brew:

hyperkit -v
hyperkit: 0.20190802

And cleaned up/tried again but yet failing with the same:

$ rm -fr  ~/.crc
$ ./crc setup
INFO Checking if oc binary is cached              
INFO Caching oc binary                            
INFO Checking if CRC bundle is cached in '$HOME/.crc' 
INFO Unpacking bundle from the CRC binary         
INFO Checking if running as non-root              
INFO Checking if HyperKit is installed            
INFO Setting up virtualization with HyperKit      
INFO Will use root access: change ownership of /Users/gallomas/.crc/bin/hyperkit 
Password:
INFO Will use root access: set suid for /Users/gallomas/.crc/bin/hyperkit 
INFO Checking if crc-driver-hyperkit is installed 
INFO Installing crc-machine-hyperkit              
INFO Will use root access: change ownership of /Users/gallomas/.crc/bin/crc-driver-hyperkit 
INFO Will use root access: set suid for /Users/gallomas/.crc/bin/crc-driver-hyperkit 
INFO Checking file permissions for /etc/resolver/testing 
INFO Checking file permissions for /etc/hosts     
Setup is complete, you can now run 'crc start' to start the OpenShift cluster
$ ./crc start --pull-secret-file ./pull-secret.txt 
INFO Checking if oc binary is cached              
INFO Checking if running as non-root              
INFO Checking if HyperKit is installed            
INFO Checking if crc-driver-hyperkit is installed 
INFO Checking file permissions for /etc/resolver/testing 
INFO Checking file permissions for /etc/hosts     
INFO Extracting bundle: crc_hyperkit_4.2.14.crcbundle ... 
INFO Creating CodeReady Containers VM for OpenShift 4.2.14-x86_64... 
ERRO Error creating host: Error creating the VM: Error creating machine: Error in driver during machine creation: getting MAC address from UUID: vmnet: error from vmnet.framework: -1