From 0022d48e3a2883d1eff34cda012c3f601d4f34a7 Mon Sep 17 00:00:00 2001 From: brandondrew Date: Mon, 27 Aug 2012 13:29:19 -0700 Subject: [PATCH] Updated `vagrant up` hangs at "Waiting for VM to boot. This can take a few minutes" (markdown) --- ...g-for-VM-to-boot.-This-can-take-a-few-minutes\".md" | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) 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" index a8e78e7..3e2638a 100644 --- "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" @@ -33,6 +33,12 @@ As long as the issues regarding this topic are not resolved, I intend to sum up VBoxManage controlvm poweroff - After this the vm can be started again by + You can get the VM id by executing - vagrant up + VBoxManage list runningvms + + and finding the name the VM you want to power down in the resulting list. + + After this the vm can be started again by entering + + vagrant up \ No newline at end of file