Oracle VM VirtualBox is the first product to provide the modern PC architecture expected by OS X without requiring any of the modifications used by competing. Note that this feature is experimental and thus unsupported. While you’re at it, you may as well reinstall the Guest Additions in your respective VMs after you fix your VirtualBox install. Oracle VM VirtualBox enables you to install and execute unmodified versions of Mac OS X guests on supported host hardware. Step 3 above is important because it appears that those Kernel Extension files are for older versions of VirtualBox (pre-4.3) that are not cleaned up by a re-install of VirtualBox, and will cause issues with 4.3 (which is the latest version of VirtualBox at the time of this writing). In a shell (Terminal), cd /Library/Extensions and sudo rm -rf VBox*.kext (Re)Download (re)install the respective Extension Pack.ģ. (Re)Download and (re)install the latest version of VirtualBox for OS X.Ģ.
These issues will include anything relating to “Kernel Extension” errors when launching the VirtualBox application or “Kernel Driver Not Installed” errors when launching a Virtual Machine.ġ. On a Windows host, this file is in the Oracle VM VirtualBox installation directory, usually in C:Program filesOracleVirtualBox. If you’re a Mac user like me, who uses VirtualBox to run guest / virtual Operating Systems within OS X, you will most likely encounter errors with VirtualBox under Mavericks, specifically if you upgrade to OS 10.9 from a pre-existing OS X install where VirtualBox was already installed.
