mitchellh/vagrant — Issue #606: Resume port collision detection doesn't take into account what is currently set.
Author: mitchellh
Created: 2011-12-25 18:18:02+00:00
State: open
Labels: bug

Resume only looks at the `config.vm.forward_port` settings, but doesn't take into account that the VM might have already been started with fixed collisions. For example, with SSH that goes to 2222 on the host:

1. Start VM A
1. Start VM B - Fixes SSH to 2200 to avoid collision.
1. Suspend VM B.
1. Resume VM B - Error message is shown, except that SSH actually WOULDN'T collide.