box-cutter/centos511 is in a 'gurumeditation' state and doesn't work.

[kitsunde]

Tested on two different machines with:

macOS Sierra 10.12.1 and 10.12 VirtualBox 5.1.8

Any other box runs fine. One of the machines was running an old version of box-cutter/centos511 and it broke when I did a box update.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'box-cutter/centos511'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'box-cutter/centos511' is up to date...
==> default: Setting the name of the VM: vagrant_default_1478238840903_98242
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    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
'gurumeditation' 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.

My vagrantfile is super simple:

Vagrant.configure('2') do |config|
  config.vm.box = 'box-cutter/centos511'
end

Any other box I run including boxcutter/ubuntu runs fine.

[annawake]

This is likely a problem with VirtualBox 5.1.8 itself and not the boxes. I can reproduce the error merely by trying to boot up from a CentOS 5.x boot DVD in VirtualBox. You might want to consider filing an issue with the VirtualBox folks by following the instructions in the error message.

[kitsunde]

Thanks. I've raised the issue with VirtualBox over at: https://www.virtualbox.org/ticket/15613.

[annawake]

Looks like the issue is in the paravirt support that was added back in recent 5.1.x builds. Here's a workaround: https://twitter.com/amdprophet/status/803679629957435392

[annawake]

https://github.com/boxcutter/centos/commit/f7fcc9d82dcbbf187f47e4a330aa7b3cabecfbb6