Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I setup a Vagrant Ubuntu 12.04 box (VirtualBox as the provider) on Windows and it's been working great for the past few months. Yesterday, I added another forwarded port to the VagrantFile and did vagrant halt and vagrant up. Once I logged in, none of the programs I had installed were there ( which git showed nothing ).

I can boot the VM manually through the VirtualBox gui and everything is correct, so I know it's there and working. I tried the solution in this related stackoverflow question, but vagrant up still doesn't start the existing vm.

Here's the VirtualBox Log for my Vagrant VM:

Not sure where else to look. Is there a way to force vagrant to load the existing VM?

Edit: Here's my VagrantFile as well. It's pretty standard, but I guess it might help.

Keep in mind that the machine was working fine until I made a change to my VagrantFile. It's the only thing that changed between functioning and non-functioning.

share|improve this question
do you have a vagrant machine with same name configured elsewhere, Vagrant boxes are not dependent on Vagrantfile path, for eg., if boxname given at = "boxname" is the unique identifier for box internally and you might have used the same name in multiple locations and did the changes there. – Vaibhav Mishra Nov 28 '13 at 13:23
No, I only have one Vagrant machine on my computer (my first to be exact). The box I'm using is precise32 from the vagrant website. I'll update the question with a bit of information and my VagrantFile. – GorrillaMcD Nov 28 '13 at 16:53

The link between your working directory (the one with the Vagrantfile) and the VirtualBox VM is a file called id placed in the following subdirectory:


(Usually the <machine_name> for a single VM Vagrantfile is default).

The id file contains the UUID of the VirtualBox VM. You should check out the correct UUID using the following command:

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo <VM_NAME> | findstr /B UUID

Then you should replace the id file with that UUID, and finally run vagrant up.

share|improve this answer
You can also use VBoxManage list vms to easily get a list of VirtualBox's VMs together with their IDs. Also id file must not contain any white space characters, e.g. new-line character after the UUID. – Dawid Ferenczy Aug 18 '15 at 16:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.