Virtual Machine could not boot.

[nanopico-jp]

I use VirtualBox with vagrant. I wrote Vagrantfile and ran `vagrant up chef_server'. But this tasks failed with the following errors.

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

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

I'm not well know what to do. Please let me know if you have a solutions.

Thanks.

[nanopico-jp]

Vagrantfile

[Frank Mehnert]

Sorry, we have no resources to support Vagrant.

When you try to start your VM and Vagrant complains that the guest cannot be started, could you look at 'dmesg' and check if there is any log entry about a crashed VirtualBox process? If so, we would require a core dump.

[nanopico-jp]

Thank you for replying. I tried your instruction, but VirtualBox does not output core dump in /var/crash. So I report this issue to Vagrant community.

[nanopico-jp]

A Vagrant support said: Unfortunately this is not a bug in Vagrant. Please open an issue with the Virtualbox team, but I highly suspect it has to do with the special characters in your username/path.

---

The error occured after running Vagrant, I tried launch VM from GUI. VirtualBox showed an error message box and outputted a core dump.

A message box is the following(translate by Japanese) Virtual Machine could not the session - "chef-sandbox_chef_server_1449849470743_99321"

VT-x is disabled in the BIOS for both all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[nanopico-jp]

Sorry, the crash file cannot be uploaded because the file size is too large. So, I'll send the file via Dropbox.

Please let me know if you would download this file.

[Frank Mehnert]

I would download this file but actually Dropbox wants to have either a Google account or a Dropbox account. I would prefer if you could send me this dump via private email to frank _dot_ mehnert _at_ oracle _dot_ com. Please don't forget to compress the file.

[Frank Mehnert]

After a couple of email exchanges it turns out that the VM process was probably crashing and that VT-x was disabled. After installing the latest 5.0.11 test build and enabling VT-x, the user is able to start VMs.