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

You just have to add the key name to your homestead.yaml file right after the provider like this:

name: name_of_you_machine

That works for me.

Answer 2

You probably have a virtualbox running! Open the programme virtualbox and shut down the other virtualbox ;) http://smallbusiness.chron.com/shut-down-virtualbox-43657.html

If this isn't working then you might want to delete the old homestead folder and place all your projects in the new folder ;)

Answer 3

I had same issue today. Spend few hours to find the solution. If by any reason you can't find the list of exiting virtual machines then type in terminal

sudo virtualbox

This will run Virtual Box in GUI. You should see the the full list of VMs and from there you'd be able to manage them. Typing "virtualbox" only won't show anything. You need to be root (administrator).

Thanks to mightyspaj for the tip.

Answer 4

If you're using homestead in Windows, just open up your Oracle VM VirtualBox and delete the homestead VM.

Answer 5

I had an old .vagrant directory in my project which was causing the error :)

If this doesn't fix it for you i would suggest opening VirtualBox and removing all VirtualBoxes and trying again.

Answer 6

For me id file was present in the below-mentioned location. D:\drupalvm.vagrant\machines\drupalvm\virtualbox