"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."

[roelvanduijnhoven]

At the moment I can no longer vagrant up from an initial Vagrentfile using box precise64 (but also precise32). The strange thing is that it did work before (just after I installed it).

The output of running VAGRANT_LOG=info vagrant up is found in this gist: https://gist.github.com/roelvanduijnhoven/6477492

I have no clue what is going wrong!

The error I get is:

"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."

[x-zheng16]

Thanks a lot~

[milan612-zz]

Using Ubuntu Trusty on OSX. checked "Enable hyperversion applications on this virtual machine." in VM setting and all good :)

[sgsheg]

:+1: It help me.

[miparnisari]

I got this error right after upgrading Windows to Windows Anniversary Update.

[mattkaye]

Just found this: http://superuser.com/questions/1111027/fix-vagrant-up-after-windows-10-anniversary-update

[miparnisari]

Yep, that answer did the trick for me.

[thiyagarajan]

$ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'hashicorp/precise64' 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: Forwarding ports... default: 3000 (guest) => 3000 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate with the guest machine within the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that Vagrant had when attempting to connect to the machine. These errors are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly working and you're able to connect to the machine. It is a common problem that networking isn't setup properly in these boxes. Verify that authentication configurations are also setup properly, as well.

If the box appears to be booting properly, you may want to increase the timeout ("config.vm.boot_timeout") value.

VTR@VTR-pc MINGW64 ~

[mattkaye]

thiyagarajan, this has already been solved. It has nothing to do with networking or a timeout issue

[unifreak]

using vagrant on Windows 7 64bit, with Virtual box 4.3.12. every thing is normal when I first installed vagrant and some box. then this day it just vagrant up just can start, with the same erorr message.

Vt-* is enabled. other box in virtual machine is fine.

I solved this by update virtual box to 5.1.10

[CatoMinor]

I received the "The guest machine entered an invalid state while waiting for it to boot" error after performing a reinstall of Norton Internet Security (antivirus software). I was able to run my VM via the VirtualBox GUI, just not with vagrant up (also MySQL Workbench could not connect to DB). I went into my BIOS, disabled virtualization, restarted, went into BIOS again and then re-enabled virtualization. Odd as it may seem, following this, vagrant up (and MySQL Workbench) began working properly again.

[agnesdai]

I had the error. I followed the instructions here and dowloaded virtual box 4.3.12 ; vagrant init hashicorp/precise32 ; vagrant up and vagrant ssh and it worked in less than 5 mins. Hope this helps.

[starikovs]

Hey! I just had this error when I upgraded my osx to macOS Sierra, so I entered vagrant up and got:

The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'aborted' 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.

So, after upgrading the VirtualBox from 4.3 to the current 5.1 version, and vagrant from 1.7.2 to 1.9.5, it fixed!!

[maksnester]

Virtual Box Version 5.1.22 Vagrant 1.9.5 Windows 10

Have this problem too. I can see in GUI that machine is running but cli doesn't think so.

[lzh1104]

Bringing machine 'default' up with 'virtualbox' provider... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: You are trying to forward to privileged ports (ports <= 1024). Most

==> default: operating systems restrict this to only privileged process (typical ly ==> default: processes running as an administrative user). This is a warning in case ==> default: the port forwarding doesn't work. If any problems occur, please try a ==> default: port higher than 1024. ==> default: Forwarding ports... default: 22 (guest) => 1322 (host) (adapter 1) default: 80 (guest) => 80 (host) (adapter 1) default: 443 (guest) => 443 (host) (adapter 1) default: 3306 (guest) => 3306 (host) (adapter 1) default: 6379 (guest) => 6379 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'unknown' 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.

The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue.

[MehdiElayeb]

ayebm vagrant $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'bento/ubuntu-16.04-i386'... ==> default: Matching MAC address for NAT networking... ==> default: Checking if box 'bento/ubuntu-16.04-i386' is up to date... ==> default: Setting the name of the VM: vagrant_default_1519659828987_21771 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 8000 (guest) => 8000 (host) (adapter 1) default: 8080 (guest) => 8080 (host) (adapter 1) default: 5000 (guest) => 5000 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'unknown' 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.

The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue.

[guilhermeureis]

Step by step: I opened Virtualbox. I turned off the Homestead Then I used the vagrant up

It worked!

[godhandkiller]

@guilhermeureis Thank you!

First I destroy the vagrant machine, so I created a new one (I'm using Laravel Homestead). Then I followed @guilhermeureis steps and It worked!

[racibaz]

Thank you @guilhermeureis

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.