Error with machine config

[yellis]

With the new config update, the vagrant box completed download successfully. Now it is giving the following error (appeared immediately after the download completed):

Successfully added box 'ubuntu-12.04-amd64' with provider 'virtualbox'!
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The following settings shouldn't exist: customize, forward_port

[yellis]

(Sorry for causing problems)

Next error message, after the machine tries to boot up:

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

I can't seem to find any type of log file that might say why it is not starting up properly.

[JasonPunyon]

@yellis Try vagrant destroy followed by vagrant up

[yellis]

Yeah, I tried that a few times already. Same result each time.

On Wed, Nov 6, 2013 at 3:07 PM, Jason Punyon [email protected]:

@yellis https://github.com/yellis Try vagrant destroy followed by vagrant
up

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-27871561
.

[JasonPunyon]

hashicorp/vagrant#1871 Looks like this always means a bug with VirtualBox (which doesn't surprise me, they've been seriously fucking up lately). Maybe try an older version of VirtualBox. What OS are you on?

[yellis]

Windows 8.1

On Wed, Nov 6, 2013 at 3:12 PM, Jason Punyon [email protected]:

hashicorp/vagrant#1871 https://github.com/mitchellh/vagrant/issues/1871Looks like this always means a bug with VirtualBox (which doesn't surprise
me, they've been seriously fucking up lately). Maybe try an older version
of VirtualBox. What OS are you on?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-27871907
.

[yellis]

What version of VirtualBox is working for you?

On Wed, Nov 6, 2013 at 3:15 PM, Yaakov Ellis [email protected] wrote:

Windows 8.1

On Wed, Nov 6, 2013 at 3:12 PM, Jason Punyon [email protected]:

hashicorp/vagrant#1871 https://github.com/mitchellh/vagrant/issues/1871Looks like this always means a bug with VirtualBox (which doesn't surprise
me, they've been seriously fucking up lately). Maybe try an older version
of VirtualBox. What OS are you on?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-27871907
.

[JasonPunyon]

I'm not on Win 8.1, but I believe the last sane version was 4.12?

[JasonPunyon]

@rossipedia: Thoughts?

[rossipedia]

Hmmmm lemme give it a shot here

[rossipedia]

@yellis which version of Virtual Box are you running? I'm using 4.3 on 8.1 and wasn't able to reproduce this.

[yellis]

I was on 4.3, windows 8.1. Completely fresh install of virtual box and
vagrant with most up to date versions.
On Nov 6, 2013 8:36 PM, "Bryan J. Ross" [email protected] wrote:

@yellis https://github.com/yellis which version of Virtual Box are you
running? I'm using 4.3 on 8.1 and wasn't able to reproduce this.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-27900507
.

[rossipedia]

Try turning on gui mode for the box:

  # Set virtual machine memory size
  config.vm.provider :virtualbox do |vbox|
    vbox.customize ["modifyvm", :id, "--memory", 1024]
    vbox.gui = true # <- turn on GUI
  end

Hopefully the boot process of the vm will give some more insight as to what's going on.

This forum post indicates that gurumeditation is an error state for Virtual Box (not too helpful I know, but at least it's a start).

[yellis]

I tried it with VirtualBox 4.1.28, no go.

Gist of the log file here.

Looks like the issue happens around line 2280 when in the {vgatext} section. Unfortunately, all it logs in that section are blank lines, and then switches to gurumeditation mode.

Did some poking around to see if anyone else had something similar. The closest that I can find is this thread, but couldnt see any replies that added anything.

I also found this thread, which sites a very similar vagrant error. There is seems that the issue was with VirtualBox 4.2.14, with issue fixed in 4.2.16. So similar, but nothing there that I could use.

Any thoughts on something else to try? Otherwise I might have to throw in the towel on this one...

[rossipedia]

The error from the log file is:

The guest is trying to switch to the PAE mode which is currently disabled by default in VirtualBox. PAE support can be enabled using the VM settings (General/Advanced)

Are you using 32 bit Virtual Box? Also, I believe with recent VirtualBox versions PAE support is under the System -> Processor tab.

[yellis]

That did it! Thanks @rossipedia. The exact setting that I needed to change was in the Virtual Box GUI, Settings > Processor tab > check [Enable PAE/NX]. Then start up the box in the VB GUI (starting it using vagrant up from the command line still does not work).

[yellis]

Final fix on this - per here I had to enable virtualization in my computer bios.

Only after I did this would the vagrant box really start up without issue.

[rossipedia]

Ahhhh that makes sense.

[yellis]

Makes sense...and quite annoying.