Re: [vagrant-up] Vagrant loses reference to box/cannot detect box!

I've seen this on Windows also and I'm sure nothing modified the contents of the .vagrant folder. My way of solving it (once, when I really needed the old machine) was to search for the id in the folder where the actual VMs are stored and update the id in .vagrant folder On 11 February 2014

Re: [vagrant-up] Vagrant loses reference to box/cannot detect box!

Hi, This happens when VBoxManage fails to occasionally give information about the old machine. So once again a VirtualBox bug, but I believe the next Vagrant version will retry getting the info if the first call fails, which should decrease the possibility hitting it. -- Cheers, - Teemu On

Re: [vagrant-up] Vagrant loses reference to box/cannot detect box!

Hi, Thanks for clarifying that ! I guess it would be good to add a message when doing vagrant up and even stopping the creation of a new VM in this case. It's very strange to see everything working 'ok' but once you try to use the VM nothing works because it's a base box with nothing installed..

Re: [vagrant-up] Vagrant loses reference to box/cannot detect box!

On Windows I use cygwin to run vagrant commands and I have seen this happen if I have the virtualbox gui running before up'ing any vms. I think vboxsvc gets a different home vm folder when started from cygwin vs gui. -- You received this message because you are subscribed to the Google Groups

[vagrant-up] Vagrant is waiting for machine to boot... and never come back

Hi guys. Look at the image. In a first step, i run vagrant up, and then vagrant ssh and into the VM I executed some commands. Then, execute exit, do a single change in the Vagrant File, then execute vagrant reload and then, I have this problem... Vagrant never can re-comunicate with the

Re: [vagrant-up] Vagrant is waiting for machine to boot... and never come back

can you share your vagrantfile and tell what's the change you are doing? On Thu, Feb 13, 2014 at 6:06 AM, Noel Broda brodan...@gmail.com wrote: Hi guys. Look at the image. In a first step, i run vagrant up, and then vagrant ssh and into the VM I executed some commands. Then, execute exit,

Re: [vagrant-up] Vagrant download

Unfortunately, we pushed a broken version of the website. We are working on getting that fixed ASAP. In the meantime, you can find the download links here:  https://bintray.com/mitchellh/vagrant/vagrant/1.4.3/files Best Regards, Armon Dadgar From: cr...@vethno.com cr...@vethno.com Reply: 

Re: [vagrant-up] Vagrant download

great thanks! On Wednesday, February 12, 2014 2:37:47 PM UTC-5, Armon Dadgar wrote: Unfortunately, we pushed a broken version of the website. We are working on getting that fixed ASAP. In the meantime, you can find the download links here:

[vagrant-up] Centralized vagrant config file?

Hi All, I have several multi-vm vagrant projects on my laptop. Is there such a thing as a centralized Vagrantfile or configuration file that can configure things such as the private network the vms boot on, or perhaps where the vms should look for apt-cacher-ng or other proxies? Or should I just

Re: [vagrant-up] Centralized vagrant config file?

Hi There, You can use this, for all the code that is the same: This came from mitchellh: you can work around this at the moment by creating a home-directory Vagrantfile in ~/.vagrant.d/Vagrantfile and doing something like this: ENV[DEFAULT_BRIDGE] ||= foo Then in your main project