Changing Vagrant's Default SSH Port To Prevent Collision When Resuming a Suspended Instance

Problem

When you are running multiple Vagrant instances you often find you are unable to resume a suspended vm instance because the port forwarding clashes with another running Vagrant box

Solution (Updated 04/09/2015)

 Assign each Vagrant instance a unique port in the Vagrantfile.

config.vm.network :private_network, ip: '192.168.115.12'
config.vm.network :forwarded_port, guest: 22, host: 12914, id: 'ssh'

Setting the id: to 'ssh' overwrites the default mapping. In previous version, you had to explicitly disable the default port first else both would be created and you'd still clash but in current versions the cleaner single line works as expected.

config.vm.network :private_network, ip: "192.168.115.12"
config.vm.network :forwarded_port, guest: 22, host: 2222, id: "ssh", disabled: true
config.vm.network :forwarded_port, guest: 22, host: 64673, auto_correct: true

There is discussion of this at https://github.com/mitchellh/vagrant/issues/3232 where I got the origional solution.