Minikube: Unable to start VM: create: precreate: exit status 126 (VBoxManage: cannot execute: No such file or directory)

[awadodeh]

I was unable to start minikube on macOS.
and thats what I got
```!bash
minikube start --v=7
😄 minikube v1.0.0 on darwin (amd64)
🤹 Downloading Kubernetes v1.14.0 images in the background ...
🔥 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
Reading certificate data from /Users/owdaa/.minikube/certs/ca.pem
Decoding PEM data...
Parsing certificate...
Reading certificate data from /Users/XXXX/.minikube/certs/cert.pem
Decoding PEM data...
Parsing certificate...
COMMAND: /usr/local/bin/VBoxManage --version
STDOUT:
{
}
STDERR:
{
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/usr/local/bin/VBoxManage: line 2: /Applications/VirtualBox.app/Contents/MacOS/VBoxManage: No such file or directory
/usr/local/bin/VBoxManage: line 2: exec: /Applications/VirtualBox.app/Contents/MacOS/VBoxManage: cannot execute: No such file or directory
}

💣 Unable to start VM: create: precreate: exit status 126

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

My machine specs:

```!bash
$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.14.4
BuildVersion:   18E226

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-26T00:04:52Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"darwin/amd64"}
The connection to the server localhost:6443 was refused - did you specify the right host or port?

$ minikube version
minikube version: v1.0.0

[awadodeh]

I was able to start minikube on my local machine using using Hyperkit driver

brew install hyperkit

&

curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-hyperkit \
&& sudo install -o root -g wheel -m 4755 docker-machine-driver-hyperkit /usr/local/bin/

and then started it by

$ minikube start --vm-driver hyperkit
😄  minikube v1.0.0 on darwin (amd64)
🤹  Downloading Kubernetes v1.14.0 images in the background ...
🔥  Creating hyperkit VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
📶  "minikube" IP address is 192.168.64.2
🐳  Configuring Docker as the container runtime ...
🐳  Version of container runtime is 18.06.2-ce
⌛  Waiting for image downloads to complete ...
✨  Preparing Kubernetes environment ...
💾  Downloading kubeadm v1.14.0
💾  Downloading kubelet v1.14.0
🚜  Pulling images required by Kubernetes v1.14.0 ...
🚀  Launching Kubernetes v1.14.0 using kubeadm ... 
⌛  Waiting for pods: apiserver proxy etcd scheduler controller dns
🔑  Configuring cluster permissions ...
🤔  Verifying component health .....
💗  kubectl is now configured to use "minikube"
🏄  Done! Thank you for using minikube!

[tstromberg]

Thanks for the bug report! I think this is the sign of an invalid VirtualBox install. So that we can provide a more useful error message, can you provide the output of:

ls -la /usr/local/bin/VBoxManage
/usr/local/bin/VBoxManage --version

[awadodeh]

Sure.

~$ ls -la /usr/local/bin/VBoxManage
-rwxr-xr-x@ 1 root  wheel    77B Aug 14  2018 /usr/local/bin/VBoxManage*

~$ /usr/local/bin/VBoxManage --version
/usr/local/bin/VBoxManage: line 2: /Applications/VirtualBox.app/Contents/MacOS/VBoxManage: No such file or directory
/usr/local/bin/VBoxManage: line 2: exec: /Applications/VirtualBox.app/Contents/MacOS/VBoxManage: cannot execute: No such file or directory

[tstromberg]

This seems like a broken VirtualBox install - VirtualBox no longer appears in the /Applications folder.

Do you mind trying to reinstall VirtualBox to see if it helps? Thanks!

[danielbankhead]

Thanks @tstromberg - installing via brew cask install virtualbox resolved this issue for me

[awadodeh]

@tstromberg it also solved the issue for me!

[tstromberg]

Great news. Thanks for the update!

[imbatman4]

@tstromberg Thanks! this worked for me too!

[akapei]

Thanks @tstromberg - installing via brew cask install virtualbox resolved this issue for me

brew cask reinstall virtualbox if you already have virtualbox installed