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

If you are a Windows User, make sure you delete C:\Users\<Username>\VirtualBox VMs\homesteadfolder. Because if there is still a folder named homestead, the action of vagrant up will not be completed

Answer 2

Windows10

Edit Homestead.yaml file and give a new name for the box:

ip: "192.168.10.10"
memory: 2048
cpus: 2
provider: virtualbox
name: my-new-vbox      #new name for the box

and run vagrant up or vagrant up --provision

Or

Open Virtualbx application in GUI and delete all the virtualbox that was causing problem and run the above command

Or

Delete the "Vagrant" file inside homestead folder and run the above command.

Answer 3

I edited Homestead.yaml and add new name for it

ip: "192.168.10.10"
memory: 2048
cpus: 4
provider: virtualbox
name: my-new-homestead-box-name

Answer 4

I was receiving the same error message, even after running "homestead destory", and "vagrant destroy". Same as you, I was using the VirtualBox provider, vagrant, and homestead. Here's what I did:

1. Opened VirtualBox GUI. I see "homestead" as a VM, but I cannot remove it, button is greyed out.
2. I logged out of my OS, logged back in and re-opened VirtualBox. Status is now "aborted" and i'm able to remove.
3. There were some residual files in ~/VirtualBox\ VMs/homestead, so i ran rm -r /Users/gabriel/VirtualBox\ VMs/homestead
4. I am now able to run "homestead up"

Answer 5

Add --force after box, and before your given name.

Answer 6

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