7

I'm trying to setup bosh-lite (to then install cloudfoundry locally) on a ubuntu server machine (vagrant v1.6.3, Virtualbox 4.3.20r96996). The setup fail when vagrant tries to boot the created machine with the following error:

$ cd bosh-lite
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'cloudfoundry/bosh-lite' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...

The guest machine entered an invalid state while waiting for it to boot.
Valid states are 'starting, running'. The machine is in the 'poweroff' state.  
Please verify everything is configured properly and try again.

If the provider you're using has a GUI that comes with it, it is often helpful to open that and watch the machine, since the GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the VirtualBox GUI is open.
bachr
  • 5,780
  • 12
  • 57
  • 92
  • 1
    possible duplicate of [Vagrant Up Error In Headless Ubuntu: The guest machine entered an invalid state while waiting for it to boot](http://stackoverflow.com/questions/19419563/vagrant-up-error-in-headless-ubuntu-the-guest-machine-entered-an-invalid-state) –  Jan 27 '15 at 12:13
  • 1
    I'm on a ubuntu server (no GUI) so the solutions won't work for me :( – bachr Jan 27 '15 at 12:17
  • It doesn't matter if you use GUI or not you still can manipulate the provider (in this case VirtualBox) though command line (shell). –  Jan 27 '15 at 12:21
  • @elsoufy I am facing same error in ubuntu on azure; Have you any solution ? – Nullpointer Jan 22 '16 at 08:38
  • @RaviG. I had to enable VT-x (see my comment below), for a detailed step by step bosh lite installation check my blog post - [here](http://elsoufy.blogspot.fr/2015/02/installing-cloud-foundry-v2-locally-on.html) – bachr Jan 22 '16 at 09:37
  • @elsoufy I am working on azure cloud; there is no option to change it !!!, Also I checked on azure cloud for VT feature is enable. – Nullpointer Jan 22 '16 at 09:41
  • @RaviG. try with another version of virtualbox (i.e. downgrade) i had to do this for many similar problems (vagrant and in another case docker). – bachr Jan 22 '16 at 09:47

2 Answers2

2

I got this error after using vagrant up on the cmd after an unplanned hard shutdown of my system running several virtual box instances, including headless Vagrant (Specifically VVV) for my Wordpress development.

Solved it with the vagrant reload command.

Several WordPress dev sites now back up and running.

Aton Bridges
  • 51
  • 5
  • I fixed this issue by enabling VT-x https://github.com/cloudfoundry/bosh-lite/issues/220 – bachr Apr 29 '15 at 09:10
1

Go to your BIOS setting of your computer. Then turn on the hardware virtualization.

Mashpy Rahman
  • 698
  • 8
  • 16