VMware Fusion - quirks and tricks

Tags: #<Tag:0x00007f389dba7c78> #<Tag:0x00007f389dba7b38> #<Tag:0x00007f389dba79f8> #<Tag:0x00007f389dba78b8>


VMware Fusion is VMware Workstation for Mac OS X

This is a quirks and tricks article for reference. Sometimes… but only sometimes… this might be helpful.

Quirks - issues that exist

No DHCP for guests


A guest system does not have network connectivity, using NATing and internal (shared) networking with the host. The interfaces do not get an IP. The DHCP client times out, and does not get a lease.

Version: 10.1.1


The DHCP client / the setup of the guest is sane. The network config of the interfaces is sane.
All issues indicate, that the DHCP server is not working.

Solution: restart the VMware Fusion DHCP server with the vmnet-cli

It’s dead, Jim.

➜  VMware Fusion sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
Stopped DHCP service on vmnet1
Disabled hostonly virtual adapter on vmnet1
Stopped DHCP service on vmnet8
Stopped NAT service on vmnet8
Disabled hostonly virtual adapter on vmnet8
Stopped all configured services on all networks
➜  VMware Fusion sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start
Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
Started all configured services on all networks

On the respective guest (example is an Ubuntu Linux):

➜  ~ sudo /etc/init.d/networking restart
[ ok ] Restarting networking (via systemctl): networking.service.

➜  ~ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto ens33
iface ens33 inet dhcp

After the restart, the guest should have gotten an IP:

➜  ~ ifconfig ens33
ens33     Link encap:Ethernet  HWaddr 00:0c:29:c7:76:a0  
          inet addr:  Bcast:  Mask:

3.4.2018 - published: VMware Fusion DHCP server restart
4.4.2018 - added version