VirtualBox compatibility issues with MAC OSX Mavericks

Hi I am also seeing this same issue but as a temporary fix for the host only adapter whenever you startup your Mac go to the terminal and use this command:

sudo /Library/StartupItems/VirtualBox/VirtualBox restart

Then go to the Virtuabox Preferences in your top left corner and click on Network and vboxnet0 should be there if not click the green plus sign

I had the same exact issue. You will need to upgrade to Virtualbox 4.3

https://www.virtualbox.org/wiki/Downloads .

There is a bug fix in 4.3 that resolves this exact issue.

Other than upgrading VirtualBox I have not had any other issues.

The built in VirtualBox Auto Updater tool will unreliably tell you that you have the latest version.

I updated to 4.3 and still wasn't able to shutdown my VM or Mac afterwards

Steps to Recreate My Issue

1) Update to 4.3

2) Have at least 2 VM's (i.e. XP, and Windows 7)

3) Open both VM's

4) Try to shutdown the 1st VM you opened by clicking the red x

expected results - VM Shutsdown and icon removes from Dock

actual results - VM Shutsdown but the icon is still in the Docking station, Force Quit and Activity Monitor cant remove it the user is also unable to shutdown his Mac without doing a manual shutdown by holding the power button. After manually shutting down n bringing it back the user is back at square 1 with the host-only adapter not available.

@brownbytes I have the issue you're reporting as well. I thought it was something I did. It is very annoying when trying to shut down.

Work Around:

1. Apple -> Sleep
2. Wake up your Mac
3. Verify you are prompted with Login screen
4. Click on Switch user
5. Click Shutdown
6. Type in your user name & password
7. Shuts down like normal.

Note: I am assuming that you have admin rights to your machine and can boot other users.

I'll check the Virtualbox Forums to see if this issue has been reported.

Over on the VirtualBox forums, we're also having vey strange hanging issues on Mavericks. At least for quite a few of us, the problem goes away by removing the host-only network adaptor (this is a work-around though, as this needs to get fixed).

Thanks to andschwa for pointing out the discussion on VBox forums, I have solved this issue in my MBP late 2007.

My problem, as mentioned in the VBox thread, comes with the host-only network adapter vboxnet0, I created a new adapter and selected it in the VM that prevents the restarts/shutdown and now it closes normally.

You can find my post here or try the other workaround suggested.

Hi I upgraded from 10.8 to 10.9 and VirtualBox from 4.2 to 4.3

After upgrade I had issue that kernel extentions were not loaded after reboot.

Re-installing solved issue until next reboot.

I found topic in https://forums.virtualbox.org/viewtopic.php?f=8&t=52406.

After un-installation VirtualBox with script included in installation dmg and installation issue dissapeared.

I never tried bash script, but seems that shall work also.

Have you tried version 4.3.2?

4.3.0's check for update function didn't report that there was a new version. 4.3.2 was released on November 1st and seems to address some of the problems.

See: https://www.virtualbox.org/wiki/Changelog

• Mac OS X host: reworked a mechanism of adding a VM desktop alias from the VM selector
• Mac OS X installer: remove old kernel extensions during upgrade (bug #12258)

Host only still doesn't seem to work and closing a VM still doesn't close everything correctly. For both of those I didn't find a bug report for Mavericks.

Since I wasn't able to work any longer because of these VirtualBox problems, I've switched to VMware Fusion. I still had a version 5 and altough it also seems to have some Mavericks issues, it is working fine for me and also seems a lot faster.

FYI, some bugs were fixed in 4.3.1 but there's still a blocker that VirtualBox prevents the Mac from shutting down.

The bug ticket is: #12241 (VirtualBoxVM Application can't quit) – Oracle VM VirtualBox

And today a dev posted an explanation:

Comment 4 describe a work-around:

I have found that this problem (at least in my case) is caused by the host-only interface ("vboxnet0" on my machine). If I don't have a host-only interface active on a given VM, it will stop cleanly. If one is active, the "stuck" behavior will be exhibited, the VM will be unable to be Force Quit and will prevent shutdown or reboot from the GUI. The machine can, however, be rebooted or shut down from the command line via "sudo reboot" or "sudo shutdown -h now", although there is a significant delay before the actual reboot/shutdown occurs (up to a minute).

I have also found that removing the host-only interface via "VBoxManage hostonlyif remove vboxnet0" will clear the condition and allow the stuck VM to finish its shutdown and disappear from the Dock.

Anyway, in VM's settings, set only Adapter 1, attached to NAT, and disable others. This way all things is fine, and when you close VM you che shutdown OSX fine. Then you can try to re-set the other network adapters.

bye

Max