Vagrant Up Error In Headless Ubuntu: The guest machine entered an invalid state while waiting for it to boot

Question

I need to install vagrant in headless ubuntu(Ubuntu 12.04.2 LTS- 64 Bit).Vagrant ver-v1.3.0 and Virtual box- 4.2.18. After adding the vagrant package box, when I am giving \"vag

Answer 1

Had an unplanned hard shutdown of my system running several virtual box instances, including Vagrant (Specifically VVV) producing the same error output when vagrant up was attempted.

Solved it with the vagrant reload command.

Several WordPress dev sites now back up and running.

Answer 2

A lot of these answers assume you're debugging a machine with a GUI, whereas the question is about a headless Ubuntu server.

The equivalent of looking in the Virtualbox GUI is the vboxmanage command, which can give you a log of info. Trying to do stuff that isn't working in Vagrant through VBoxManage directly will give you plenty of options to troubleshoot.

In my case just clearing up old VMs fixed my issues.

vboxmanage list vms

This will display the name and UUID of the VMs Virtualbox currently has registered. Grabbing the UUID of existing machines and clearing them up fixed the problems.

vboxmanage unregistervm $uuid --delete

Answer 3

In my case:

• updating vbox
• when running vagrant up, the OS was booting and waiting for a network connection, taking forever
• to fix, open vbox, show the active vm, click the icon for network adapters, disable ethernet connection, enable nat.
• the vm continues to boot, and vagrant can connect through ssh

Answer 4

In case if you've installed the virtual box 4.3.14 then there is a known issue of "Anti virus conflict". You need to uninstall the 4.3.14 and install 4.3.15 as explained in this thread.

https://forums.virtualbox.org/viewtopic.php?f=6&t=62615

Answer 5

In my case I tried to start the VirtualBox via the GUI. It turned out that VT-x/AMD-V hardware acceleration was not activated on my system and later that it wasn't available. I had to use a 32 Bit Distribution along with this config settings.

Answer 6

For me this started to happen just after upgrading Avast Free Antivirus to v11.1.2253.

Although I'm having the VT-X option enabled, when started a box using VirtualBox Manager I've been receiving errors that it is not (VERR_VMX_MSR_LOCKED_OR_DISABLED).

Another issue was that the VirtualBox Manager showed up Operating system Ubuntu (32-bit), when the box is 64-bit.

Solution is to disable 'Enable hardware-assisted virtualization' in Avast Antivirus, at least until Avast team solves it.

Source: Avast forums > Avast Free 11.1.2253 & VirtualBox 5.0.14

For future reference: VirtualBox may conflict with other programs using virtualization: The usual culprits are system level debuggers, other VM platforms, and some resident anti-virus applications as described on [VirtualBox forum](https://forums.virtualbox.org/viewtopic.php?f=1&t=62339.