I encountered multiple software updates over the last few weeks. I did as you recommended and the issue appears to be resolved.
macOS 10.12.2 VMware Fusion 8.5.3 (4696910) Vagrant 1.9.1 $ vagrant plugin list vagrant-share (1.1.6) - Version Constraint: > 0 vagrant-vmware-fusion (4.0.15) - Version Constraint: > 0 Thanks! -- Chris On Tuesday, December 20, 2016 at 1:32:55 PM UTC-6, Alvaro Miranda Aguilera wrote: > > Hello. > > Can you update to Vagrant 1.9.1 and then update the plugin ? > > vagrant plugin list > vagrant plugin install <plugin> > > Install will force reinstall/update of the plugin. > > Alvaro > > On Tue, Dec 20, 2016 at 6:20 PM, Chris Bandy <[email protected] > <javascript:>> wrote: > >> Alvaro, >> >> I am experiencing this same issue on macOS 10.12.1 with Vagrant 1.8.4 and >> VMware Fusion 8.5.3 (4696910). >> >> Per Andrew's suggestion, I tried deleting lines from the [incomingtcp] >> section of '/Library/Preferences/VMware Fusion/vmnet8/nat.conf'. However, >> when starting the box vagrant continued to find a port collision and the >> lines I deleted reappeared. >> >> Exploring this preferences folder further, I found another file, >> '/Library/Preferences/VMware Fusion/networking', with the following lines: >> >> add_nat_portfwd 8 tcp 2200 192.168.52.185 22 >> add_nat_portfwd 8 tcp 2201 192.168.52.185 22 >> add_nat_portfwd 8 tcp 2202 192.168.52.185 22 >> add_nat_portfwd 8 tcp 2203 192.168.52.185 22 >> add_nat_portfwd 8 tcp 2204 192.168.52.185 22 >> add_nat_portfwd 8 tcp 2222 192.168.52.185 22 >> >> >> When I delete these (along with those in 'nat.conf',) vagrant no longer >> reports a collision during startup. However, this only lasts for one boot. >> Issuing a `vagrant halt && vagrant up` triggers another port collision and >> additional lines in both preference files. >> >> -- Chris >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/6fd7a698-51fd-4491-a0cb-31ccda765fe4%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/6fd7a698-51fd-4491-a0cb-31ccda765fe4%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alvaro > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/74b9b679-9682-4d4d-b905-a90d7611af68%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
