Port is not freed when used with VMWare Fusion
RReverser opened this issue · comments
Whenever I restart my VM, it looks like currently used port is not freed (neither on halt nor on reload), so I'm getting the following error:
Some of the defined forwarded ports would collide with existing
forwarded ports on VMware network devices. This can be due to
existing Vagrant-managed VMware machines, or due to manually
configured port forwarding with VMware. Please fix the following
port collisions and try again:
<currently used port>
After this, each time I have to go to Vagrantfile and manually set/bump config.notify_forwarder.port to a new value to avoid that conflict, and then it works again till the next restart.
@mhallin Any chance of taking look at this?