I'm having an issue with hostonly ethernet devices starting disconnected on autostarted VMs.
The following appears in the log.
Jan 29 23:21:33: vmx| VNET: Notification enabled for Ethernet1
Jan 29 23:21:33: vmx| MAC_Connect: Could not find any suitable backend for adapter 1
Jan 29 23:21:33: vmx| Msg_Post: Warning
Jan 29 23:21:33: vmx| \[msg.hostonly.GIFFLAGS] Could not get interface flags for vmnet1: No such device
Jan 29 23:21:33: vmx| \[msg.device.startdisconnected] Virtual device Ethernet1 will start disconnected.
Jan 29 23:21:33: vmx| \----
Jan 29 23:21:33: vmx| POST(no connection): Could not get interface flags for vmnet1: No such device
Jan 29 23:21:33: vmx| Virtual device Ethernet1 will start disconnected.
Jan 29 23:21:33: vmx|
The cause of this problem seems to be that net-services.sh starts hostonly interfaces in the background, and the ping/address-conflict test takes so long that the VM finishes POSTing before the hostonly networks are online.
I was able to work around this problem easily enough for now (change vmware_bg_exec to vmware_exec in net-services.sh), but the workaround will be zapped when I upgrade, and I'm not likely to remember to re-apply it. I'm also wondering why nobody else seems to have this problem (searching this forum didn't turn up any other similar incidents).