From 3ab611ca712fac4d55431c2a2230f89ca60d9a11 Mon Sep 17 00:00:00 2001 From: janschumann Date: Sun, 26 Aug 2012 00:56:34 -0700 Subject: [PATCH] Created `vagrant up` hangs at "Waiting for VM to boot. This can take a few minutes" (markdown) --- ...to-boot.-This-can-take-a-few-minutes\".md" | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 "`vagrant-up`-hangs-at-\"Waiting-for-VM-to-boot.-This-can-take-a-few-minutes\".md" diff --git "a/`vagrant-up`-hangs-at-\"Waiting-for-VM-to-boot.-This-can-take-a-few-minutes\".md" "b/`vagrant-up`-hangs-at-\"Waiting-for-VM-to-boot.-This-can-take-a-few-minutes\".md" new file mode 100644 index 0000000..a8e78e7 --- /dev/null +++ "b/`vagrant-up`-hangs-at-\"Waiting-for-VM-to-boot.-This-can-take-a-few-minutes\".md" @@ -0,0 +1,38 @@ +As long as the issues regarding this topic are not resolved, I intend to sum up some workarounds working for me. + +## This is a list of issues related to this topic: + +- [#391](https://github.com/mitchellh/vagrant/issues/391) +- [#455](http://github.com/mitchellh/vagrant/issues/455) +- [#1064](https://github.com/mitchellh/vagrant/issues/1064) +- [#1066](https://github.com/mitchellh/vagrant/issues/1066) + +## Workarounds + +1. Reboot using GUI mode and fix network issues manually + + After rebooting in GUI mode, and issuing + + $ /etc/init.d/networking/restart + + will SOMETIMES solve the problem. + + Some people also proposed to add the above line to /etc/r.local or similar. But in my experience, this will not finally solve the problem. + +1. Reboot using shell provisioner to fix network issues + + Instead of booting in GUI mode and fix networking issues manually, some people propose to doing this via shell provisioner: + + config.vm.provision :shell, :inline => "/etc/init.d/networking restart" + + I tried this several times, but it failed most often. + +1. Recover VM state using VBoxManage + + When changing the environment (Office, Home Office, Coop) which also means the network, the issue occurs everytime. The solution is to simply poweroff the machine by + + VBoxManage controlvm poweroff + + After this the vm can be started again by + + vagrant up