Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

A connection with the name you specified already exists

I am setting up my previously working vagrant environment in Windows 10. I've updated to the newest version of both VirtualBox (https://www.virtualbox.org/ticket/14040) and Vagrant.

When I vagrant up I get an error: Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.

I've since tried deleting all of my boxes, deleting the .vagrant and .virtualbox directories, reinstalling both virtualbox and vagrant. Yet, I always get the same error. Here is the error message from my console:

The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again.

If the provider you're using has a GUI that comes with it, it is often helpful to open that and watch the machine, since the GUI often has more helpful error messages than Vagrant can retrieve. For example, if you're using VirtualBox, run vagrant up while the VirtualBox GUI is open.

The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue.

like image 771
Chris Avatar asked Aug 04 '15 20:08

Chris


People also ask

How can I see hidden network connections?

Type Start DEVMGMT. MSC , and then press ENTER. Click View, and then click Show Hidden Devices. Expand the Network adapters tree.


1 Answers

I had the same issue with Scotchbox, and even after installing the test build the issue was still there.

This is how I fixed the issue.

Step 1: Download and install https://www.virtualbox.org/attachment/ticket/14040/VBox-Win10-fix-14040.exe and leave it running in the background

Step 2: Head to the Virtual box program files ( C:\Program Files\Oracle\VirtualBox ).

Step 3: Go to compatibility for these three .exe ( Virtualbox.exe, VBoxHeadless.exe, and VBoxManage.exe ) and choose windows 7.

Then just run vagrant up again and it should work.

like image 111
BlastedGh0st Avatar answered Sep 18 '22 08:09

BlastedGh0st