VMware Fusion 3 on Mac offers three kinds of networking: bridged, NAT and host-only.
When using host-only networking, VMware Fusion runs a DHCP server for you on the virtual network “vmnet1“. By default, this daemon hands out IP addresses in the 172.16.115.0/24 network.
There are no settings in Preferences to configure or disable the DHCP server. This causes problems when trying to run your own virtualized DHCP server or PXE boot environment on the host-only network.
The VMware DHCP server can be disabled either temporarily or permanently. For a temporary fix (until you restart Fusion), end the DHCP server process. Open a Terminal window and type:
sudo kill -15 `sudo cat /var/run/vmnet-dhcpd-vmnet1.pid`
To permanently disable the DHCP server, you need to change one line in /Library/Application Support/VMware Fusion/networking. This file normally looks like this:
VERSION=1,0 answer VNET_1_DHCP yes answer VNET_1_DHCP_CFG_HASH D06F14D2911502FA261951B0F568992FEC46C8B3 answer VNET_1_HOSTONLY_NETMASK 255.255.255.0 answer VNET_1_HOSTONLY_SUBNET 172.16.115.0 answer VNET_1_VIRTUAL_ADAPTER yes answer VNET_8_DHCP yes answer VNET_8_DHCP_CFG_HASH 9894EC355205C9C006F1BE90320DF38FEE4CC80A answer VNET_8_HOSTONLY_NETMASK 255.255.255.0 answer VNET_8_HOSTONLY_SUBNET 172.16.178.0 answer VNET_8_NAT yes answer VNET_8_VIRTUAL_ADAPTER yes add_bridge_mapping en0 2
Quit VMware Fusion, run “sudo vi /Library/Application Support/VMware Fusion/networking” and change the highlighted line to read:
answer VNET_1_DHCP no
Reboot your Mac or run “sudo /Library/Application Support/VMware Fusion/boot.sh --restart” to activate the changes.