Last modified: 2013-10-03 10:12:39 UTC
I am having trouble with creating a default Vagrant VM. I have two machines (old one and a new one), both have Mac OS X 10.8.5, VirtualBox 4.2.18, Vagrant 1.3.3. and the latest MediaWiki-Vagrant (e07bee). When I run "vagrant up", the older machine times out (tried at least three times). Terminal output is attached. MediaWiki is not available at http://127.0.0.1:8080/
Created attachment 13381 [details] terminal output
I was looking at Activity Monitor while running "vagrant up" and of course, both cores were at 100% all the time, hence the timeout after reaching boot_timeout value (this is a pretty old machine). I will try increasing config.vm.boot_timeout in Vagrantfile-extra.rb from the default 300[1] to 600 seconds. 1: http://docs.vagrantup.com/v2/vagrantfile/machine_settings.html
This does not increase the timeout (to my surprise) config.vm.boot_timeout = '600' but this does config.vm.boot_timeout = 600 but "vagrant up" still times out. I will try increasing VM RAM to 1024 and see if it helps, before further increasing boot_timeout.
Increasing boot timeout to 600 seconds and increasing VM RAM to 1024 MB solved the problem. Since I do not have this problem on my other machine, looks like the problem is in the old machine, not in Vagrant.
I have been testing vagrant on my old laptop and it also does not time out if I increase boot timeout from 300 to 1200 seconds, without increasing VM RAM. That machine used to work just fine with previous versions of mediawiki-vagrant. Did you change anything recently that could cause boot timeouts on older machines?
