mitchellh/vagrant — Issue #764: When port forwarding Vagrant doesn't detect if the port is already on use
Author: luismreis
Created: 2012-02-25 22:25:32+00:00
State: open

My "vagrant up" kept failing with a stalling just after printing "Waiting for VM to boot. This can take a few minutes.".

Turns out that I had already Parallels doing port forwarding on port 2222, so the message appeared but nothing more happened.

I don't know if this is a Vagrant or VirtualBox issue. Either Vagrant should fail by detecting something already running on port 2222, before attempting to configure virtual box or the VBoxManage command should report the port already on use.

Having Vagrant detect this seems more natural to me because if you're executing a "vagrant up" command it's expected to start using the port right away. Using VBoxManage report this doesn't seem so adequate because you're just configuring something permanent that doesn't have to be used at the moment.