I recently modified my Parallels DHCP settings because I’m really particular about the internal subnets I work with in the lab (192.168 is the ugliest subnet ever). Once I modified the file at /Library/Preferences/VMware\ Fusion/networking (OS X) my Parallels Desktop erred out and said
Interface vmnet1 is not present. This should be created at boot time.
Someone on this thread suggested a reinstall but that only worked as a temporary fix. Turns out, when you modify the networking file, you also need to restart your vmnet-cli service. You can do this with the following commands:
/Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –config
/Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –start
/Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –status
I ended up just throwing the stop and start commands into a script and running it each time I modified my settings.