mitchellh/vagrant — Issue #585: w/ CentOS-5.7-x86_64 basebox.. vagrant 0.8.8 just sits there
Author: nemonik
Created: 2011-12-08 20:07:28+00:00
State: open

I can build the veevee/templates/CentOS-5.7-x86_64-netboot basebox and one of my creation using the http://mirror.steadfast.net/centos/5.7/isos/x86_64/CentOS-5.7-x86_64-bin-DVD-1of2.iso with a rvm installed ruby 1.8.7 and puppet and chef gems.

Afterwards, *with vagrant 0.8.8 I set up a Vagrantfile and bring up vm using either of the aforementioned baseboxes and the resulting VM wil simply sit there like so*:

Lionshark:mediawiki nemonik$ vagrant up
[default] Box mediawiki was not found. Fetching box from specified URL...
[default] Downloading with Vagrant::Downloaders::File...
[default] Copying box to temporary location...
[default] Extracting box...
[default] Verifying box...
[default] Cleaning up downloaded box...
[default] Importing base box 'mediawiki'...
[default] Exporting NFS shared folders...
[default] Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
[default] Preparing host only network...
[default] Matching MAC address for NAT networking...
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- ssh: 22 => 2222 (adapter 1)
[default] Creating shared folders metadata...
[default] Running any VM customizations...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.

But after I suppose the config.ssh.timeout and max_tries amount of dictated time occurs it throws the following error before quitting:

[default] Failed to connect to VM!
Failed to connect to VM via SSH. Please verify the VM successfully booted
by looking at the VirtualBox GUI.

And the gui was long since up before the failure and is sitting normally at the login in prompt. Running 'vagrant ssh', I can ssh right into the virtualized development environment, and I can then use 'vagrant destroy' to force the shutdown of the VM...

Now, if I take the same Vagrantfile and change the value of config.vm.box_url to say "../bases/oneiric64.box" to create an Ubuntu 11.10 virtualized development environment, I move past:

[default] Waiting for VM to boot. This can take a few minutes.

And I'm up and running.

If I build and install the vagrant gem from source, same problem. *If I roll back to 0.8.7 though and give it a go, it works.*

To create my basebox and run vagrant I'm using:

I'm using VirtualBox 4.16 r74713 on OS X Lion 10.7.2 with a multi-user install of rvm 1.9.2.

My default ruby is 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin11.2.0]

Before rolling back to vagrant 0.8.8, my installed local gems are:

archive-tar-minitar (0.5.2)
builder (3.0.0)
bundler (1.0.21 ruby)
cucumber (1.1.3, 1.0.6)
diff-lcs (1.1.3)
erubis (2.7.0)
ffi (1.0.11)
gherkin (2.6.9, 2.4.21)
highline (1.6.8)
i18n (0.6.0)
json (1.6.3, 1.5.4)
net-scp (1.0.4)
net-ssh (2.2.1, 2.1.4)
open4 (1.3.0)
Platform (0.4.0)
popen4 (0.1.2)
progressbar (0.9.2)
rake (0.9.2.2, 0.9.2)
rspec (2.7.0)
rspec-core (2.7.1)
rspec-expectations (2.7.0)
rspec-mocks (2.7.0)
term-ansicolor (1.0.7)
thor (0.14.6)
vagrant (0.8.8)
veewee (0.2.1)
virtualbox (0.9.2)

All gems appeared to be up-to-date.

My Vagrantfile is simply:

Vagrant::Config.run do |config|
config.vm.box = "mediawiki"

config.vm.box_url = "../bases/CentOS-5.7-x86_64.box"
# config.vm.box_url = "../bases/oneiric64.box"

config.vm.boot_mode = :gui
config.vm.network "192.168.27.100"

config.ssh.max_tries = 100
config.ssh.timeout = 300

config.vm.boot_mode = :gui

config.vm.customize do |vm|
vm.memory_size = 1024
end

end

Before entering a ticket into VeeWee's issues I pounded my forehead flat for two days before @eclubb responded saying t he problem existed for him as well and was introduced in 0.8.8, but that 0.8.7 worked for him. I'm thinking at this point, there's a bug.