A VirtualBox machine with the name 'homestead' already exists

Question

Since homestead 2.0 homestead laravel has not been working

I don\'t know why \'homestead init\' creates a Homestead.yaml file in mydirectory/.homestead and not in

Answer 1

For me, the machine was not showing up as an active VM in the VirtualBox application. To fix I had to do this:

vagrant global-status

This gave me the ID of the machine that I needed to destroy. With the ID, run:

vagrant destroy {VM ID}

I had to run that in sudo to actually destroy the machine. At that point, I was able to run

vagrant up