I cannot believe that I have to completely restart my Mac every time this problem happens (at random). I followed advice found at but still have the problem. # VBoxManage dhcpserver remove -ifname vboxnet0 But the next time I start up a new VM, or when I quit VirtualBox and restart all the VMs, or just randomly, this situation can recur.

restarting the whole machine works every time, and then it's like nothing has changed but now it suddenly works.

logging out and back in the user does nothing.

Apple Installers will tell you it is not a supported installation type, but you can launch a Terminal and run the installation using command line.

killall -HUP configd (manually sending a Hangup interrupt to the configd process to reset the network (and just about everything else) does nothing. > patched Maverick disk image is ready Then, you can create a Mac OS X 10.7 64-bit or OS X 10.8 64-bit virtual machine and boot using the patched disk image.

scutil -r 192.168.10.10 says the host is reachable.

ifconfig down followed by ifconfig up for all IP interfaces.

From either side pings result in timeouts. ifconfig on both sides shows the shared network interface vboxnet0.

Very nice except the Mac cannot see it until after I restart the whole machine. It was configured to have two adaptors #1 NAT and #2 Host-only 192.168.10.10/24. Most recently I was running a Vagrant avenuefactory/wordpress VM. I have experienced several times that with different VMs (particularly Ubuntu Linux VMs) after the first time the VM is brought up host-only networking will not work. I have a MacOS X Mavericks host running Vagrant using VirtualBox as a provider.

Virtualbox mac os x mavericks