"Booting VM" forever (Selecting on IO)

[paulocheque]

It is stucked in "Botting VM" message forever. Any ideas?

Vagrant version 1.2.0

Using quantal64.box VAGRANT_LOG=debug vagrant up --provider virtualbox vb.customize ["modifyvm", :id, "--cpus", "1"] vb.customize ["modifyvm", :id, "--cpuexecutioncap", "50"] vb.customize ["modifyvm", :id, "--memory", "256"]

Ubuntu 12.10 64 machine RAM 512mb

[default] Running any VM customizations... INFO subprocess: Starting process: ["VBoxManage", "modifyvm", "90c9da4e-2f5b-49c1-8c86-720f6a5ff038", "--cpus", "1"] DEBUG subprocess: Selecting on IO DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999 DEBUG subprocess: Exit status: 0 INFO subprocess: Starting process: ["VBoxManage", "modifyvm", "90c9da4e-2f5b-49c1-8c86-720f6a5ff038", "--cpuexecutioncap", "50"] DEBUG subprocess: Selecting on IO DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000 DEBUG subprocess: Exit status: 0 INFO subprocess: Starting process: ["VBoxManage", "modifyvm", "90c9da4e-2f5b-49c1-8c86-720f6a5ff038", "--memory", "256"] DEBUG subprocess: Selecting on IO DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999 DEBUG subprocess: Exit status: 0 INFO warden: Calling action: #VagrantPlugins::ProviderVirtualBox::Action::Boot:0x00000002cc0d60 INFO interface: info: Booting VM... [default] Booting VM... INFO subprocess: Starting process: ["VBoxManage", "startvm", "90c9da4e-2f5b-49c1-8c86-720f6a5ff038", "--type", "headless"] DEBUG subprocess: Selecting on IO

[mitchellh]

Does this happen every time? I need reproduction steps in order to treat this as a real bug. As it stands now, everything works great on my end. Can you reproduce this on another computer? Have you tried restarting (VirtualBox kernel extensions sometimes fubar)? etc.

[paulocheque]

Yes, every time inside of a Free instance of EC2. (in my Mac it works properly the configuration).

I thought it could be something related to the memory. Do you think 512mb (256mb for cagrant vm) is enough?

25242 ubuntu 20 0 114m 5928 3812 S 0.0 1.0 0:00.17 VBoxXPCOMIPCD 25247 ubuntu 20 0 516m 9328 6432 S 0.0 1.5 0:00.48 VBoxSVC 25491 ubuntu 20 0 261m 7008 5096 S 0.0 1.2 0:00.02 VBoxManage 25498 ubuntu 20 0 530m 8008 5480 S 0.0 1.3 0:00.17 VBoxHeadless

[mitchellh]

Ah, VirtualBox doesn't work inside of EC2. Can' virtualize inside of virtualized machines.

[paulocheque]

oh... ok! mistery solved! thanks

[tgalopin]

I'm having the exact same problem, but on Windows 7. It works the first time I run vagrant just after its installation, but once the VM created, it does no work anymore, it stays forever on "Booting VM...":

 INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "startvm", "60c9d114-8
478-478f-b846-08b8c6380daa", "--type", "headless"]
DEBUG subprocess: Selecting on IO

Any idea ?

[ananya0631]

I am facing the same problem on Windows 7. Using vagrant BOX: box 'inclusivedesign/windows7-eval-x64' .The machine opens properly in GUI but the Vagrant command does not complete. On running without debug mode the "Vagrant UP" command is stuck at Booting VM.

In the debug mode i am geeting the following message

INFO subprocess: Starting process: ["C:/Program Files/Oracle/VirtualBox/VBoxManage.exe", "startvm", "b4227a86-887f-488d-8aa6-4e035beaf93e", "--type", "gui"] INFO subprocess: Command not in installer, restoring original environment... DEBUG subprocess: Selecting on IO

Please help!!!!!!!!!

[iddqdidkfa]

Try config.vm.provider :virtualbox instad of config.vm.provider "virtualbox". I found this syntax on some Vagrantfile examples. Don't know why, but it helps to resolve same situation.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.