Every now and again I run into issues using Vagrant and VMware Fusion togther. Specifically around starting VMNET-DHCP servers. The following commands have done wonders to fix that in a pinch:
sudo /Applications/VMware Fusion.app/Contents/Library/vmnet-cli --configure sudo /Applications/VMware Fusion.app/Contents/Library/vmnet-cli --stop sudo /Applications/VMware Fusion.app/Contents/Library/vmnet-cli --start
As and edit on this,
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –start
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –configure
as Mac being a unix backend doesn’t read spaces so require the \ for vmware
Looks like James was on a Mac and the double dashes got converted to a single long dash. Here’s the copy and pastable version:
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –start
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –configure
“`
sudo “/Applications/VMware Fusion.app/Contents/Library/vmnet-cli” –configure
sudo “/Applications/VMware Fusion.app/Contents/Library/vmnet-cli” –stop
sudo “/Applications/VMware Fusion.app/Contents/Library/vmnet-cli” –start
“`