I am using VirtualBox 4.2.18 and Vagrant 1.3.3 on Window 7. I have done a vagrant box add

vagrant box add MyBox http://ergonlogic.com/files/boxes/debian-LAMP-current.box

But, when I get to the step of vagrant up I get the following error: "vboxmanage.exe error could not rename the directory..."

Any help would be appreciated.

Thanks,
Derek

I tried:

• vagrant destroy -f


• manually deleting the virtualboxes in their directory


• restarting my machine


• reinstalling both vagrant and virtualbox


• downgrading vagrant and virtualbox


• running with sudo

and nothing worked. The only thing that worked for me was opening Virtualbox interface and going to Preferences and changing the Default Machine Folder from VirtualBox VMs to just VMs

Wasted about 4 hours of my time on that problem. Hopefully someone with the same problem finds this post.

I went to the Directory

VirtualBox VMs

And deleted everything inside. Then I just did vagrant up, and it worked.

I was finally able to figure this out. Turns out it is useful to know how to set two specific directory paths for VirtualBox. This was particularly useful because I run my machine under an account that does not have administrative privileges. So I needed to get VirtualBox to used directory paths which I had access to security-wise. The first is the VBOX_USER_HOME environment variable which can be done within the System Properties/Environment Variables on Windows 7. In this way the VBOX_USER_HOME variable will control where the .VirtualBox directory goes. Secondly, set where the *.vbox files goes which is typically a directory called VirtualBox VMs. To set this path open the VirtualBox GUI and go to File  Preference and set the path at the Default Machine Folder input box.

Hopefully this info will help others.

Derek

I just removed every sub folder under this folder and it worked

That error means there is other VM in Virtual Machine with the same name as the one you used for this VM. So go back to the folder of that VM you run previously and destroy it with "vagrant destroy -f". Then try again running this VM.

Vagrant

Working with Vagrant I had a similar error. This was due to naming conflicts. What solved it for me was to remove the name of the instance from the Vagrantfile.

vb.customize ["modifyvm", :id,
 "--name", "oracle",
 "--memory", "512",
 "--natdnshostresolver1", "on"]

Change that to

vb.customize ["modifyvm", :id,
 "--memory", "512",
 "--natdnshostresolver1", "on"]

Don't destroy your vagrant machine! This is a last option.

Write in you console:

VBoxManage list vms

Copy id of your machine, something like:

7fca07b2-65c6-420e-84b5-b958c15449a1

Open your vagrant machine id file, something like:

.vagrant/machines/default/virtualbox/id

Replace with id you just copied and do:

Vagrant up

This allways works for me. If not, only as last option you can try: vagrant destroy -f

You Just need find your folder called VirtualBox VMs

In that folder should see your machines

And rename what folder you want, and run:

vagrant up

So you have run it successfully.