I'm experiencing the same issue and removing and recreating the vboxnet0 helped killing the "zombie" virtual machine.
But, experimenting with other machines that also have a host only network configured (different from vboxnet0) I found that they are closing normally, so I tried creating another host only network identical to vboxnet0 (with same IP address/mask) and replacing it in the problematic VM and "voilà", the VM now closes correctly.
To create a new network adapter go to: Preferences... > Network > Host-only network tab, click the NIC with the plus sign on the right and edit the configuration with the screwdriver if needed.
After that, select the new network adapter on the VM configuration.
My setup:
- MacBook Pro late 2007
- OS X 10.9 (clean install)
- VirtualBox 4.3.2 (upgraded from 4.3.0)
- VM's came from VirtualBox 4.2.x (cannot remember the exact version)
- 1 NAT virtual network adapter, 2 Host-only (now 3 with the workaround)
UPDATE: I was trying to reproduce the issue after creating the new network adapter and now everything appears to be normal using either vboxnet0 or vboxnet2 (the newly created adapter). May be something got corrupted during the VM import from v4.2.x to 4.3.0?
Edit: UPDATE2: This solution was temporal... turned off my computer at the end of the day and now I'm experiencing the same issue with vboxnet2. I don't understand why vboxnet1 (the other host-only network adapter) is working normally. |