CODEWITHSUNDEEP
windowsvagrantvirtualbox
Rooster
Rooster

Reputation: 10077

Vagrant up created VM disappears after completion of vagrant up

I'm running the latest versions of Vagrant and VirtualBox.

I'm trying to set up a new VM from a VagrantFile that was provided to me. When I run:

vagrant up

from the directory the VagrantFile lives in, over the course of several hours Vagrant setups the new VM. I can see the new VM in the VirtualBox GUI while its setting up the new VM.

However, on completion of this process, the VM disappears from within the VirtualBox GUI.

I initially tried this with cygwin, but after that failed and a little bit of research as to where the VM's might get put, I also tried it through windows console hoping to avoid this. No dice either way.

I've also checked in

C:/Users/_my_user_/VirtualBox_VMs

which is empty, and

C:/cygwin64/home/_my_user_/

and dont even have a VirtualBox directory.

This whole process takes 6 hours to finish and doesnt even throw an error at the end, which is very frustrating. Any help or insight would be greatly appreciated. Can happily update question with any requested pertinent information!

Cheers!

Upvotes: 0

Views: 230

Answers (1)

unrivaledcreations
unrivaledcreations

Reputation: 938

Vagrant has a debugging mode:

vagrant up --debug

Because of the variety of hypervisors that Vagrant can utilize, problems that surface on that end can be examined using their logging and debugging mechanisms. In your case, VirtualBox keeps very detailed logs by default. Those can be found in the Logs directory. Look in your home directory, under VirtualBox\{virtual_box_name}\Logs.

In my case, I'm using VMWare's AppCatalyst, so I would find the hypervisor log here:

/Users/unrivaled/puphpet/zYQHgJ/.vagrant/machines/default/vmware_appcatalyst/vagrant-{vm_uid}

For other hypervisor providers, check their documentation for their logging options and file locations.

Upvotes: 2

Related Questions