Vagrant: A VirtualBox machine with the name 'homestead' already exists.

[Soufraz]

Yesterday I worked until 2 am usually in my box homestead.
Before bed I ran a vagrant suspend and lay on my bed in peace.
I woke up today and homestead simply no longer works.
The vagrant resume not worked. The vagrant halt not worked. The vagrant suspend not worked. The vagrant up not worked.
When I try to start the box I get the following message:

#~ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
A VirtualBox machine with the name 'homestead' already exists.
Please use another name or delete the machine with the existing
name, and try again.

I read a lot of questions and tutorials on the web from google. (ahhhh)
But almost all solutions is destroy the machine and init again. But I don't have backup of my databases and I really can't believe that doing NOTHING the vagrant stops.

Is there a fix to this? Thanks advice..

[sethvargo]

Hi @Soufraz

When you open up the Virtualbox GUI, do you see the virtual machine in the list?

[Soufraz]

Yes. homestead - Powered Off
Location: /home/soufraz/VirtualBox VMs/homestead/box-disk1.vmdk

[Soufraz]

Can I create a new box with an existing disk?

[Soufraz]

I fixed a tiny part of the problem.
First I ran vboxmanage list vms to see my vms id. I copied the homestead id and I browsed to ~/Homestead/.vagrant/machines/default/virtualbox and put the id into id file.
But now, the vagrant up stops in default: Warning: Connection timeout. Retrying....
Is better to help me now? :)

[Soufraz]

I think that is something about the ssh keys.

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 80 => 8000 (adapter 1)
    default: 443 => 44300 (adapter 1)
    default: 3306 => 33060 (adapter 1)
    default: 5432 => 54320 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

[Soufraz]

Here my solution:

mkdir -p /home/vagrant/.ssh
wget --no-check-certificate https://raw.github.com/mitchellh/vagrant/master/keys/vagrant.pub -O /home/vagrant/.ssh/authorized_keys
chmod 0700 /home/vagrant/.ssh
chmod 0600 /home/vagrant/.ssh/authorized_keys
chown -R vagrant /home/vagrant/.ssh

Source: http://superuser.com/questions/745881/how-to-authenticate-to-a-vm-using-vagrant-up

[kenorb]

Related: A VirtualBox machine with the name 'homestead' already exists.

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.