Eddie Hinkle

Quirks with Mac OS X 10.9

I love new Mac OS X updates as much as the next person. However, for those of us who are the first to update we will often find bugs that haven't been fixed either with the new operating system or with applications that don't update to meet the new operating system's rules.

This blog is where I'll be documenting the quirks and bugs I notice in the new Mac OS X 10.9 "Mavericks" release for the good of mankind. I will update the "published date" of this article whenever I have new content added.

Quirks noticed

• VirtualBox 4.3 • VirtualBox All Versions

Virtual Box 4.3

I installed VirtualBox 4.3 and it installed fine except for a few errors. However, the errors let me continue onward leading me to assume all was fine. It wasn't. Part of what the kernels do is allow support for things like Virtual Box's command line interface which I use with Vagrant. After lots of searching on the internet I found this post from ycombinator that explains it:

`VirtualBox 4.3 doesn't run at all on Mavericks (10.9) because their kernel extensions aren't signed. OS X 10.9 requires signed kexts now...VirtualBox 4.3 doesn't work. VirtualBox 4.2 does. VMware Fusion 5 and 6 does.`

So in this instance, the rule of thumb is to downgrade to VirtualBox 4.2 until they sign their kernels as Mavericks requests. You can still download VirtualBox 4.2 here

Virtual Box All Versions

While Virtual Box 4.1 and 4.2 work on 10.9, occasionally while using Vagrant you'll receive the following error: There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

I found a person on Stack Overflow that had the Answer, you enter the following into Terminal: sudo /Library/StartupItems/VirtualBox/VirtualBox restart

Waldorf, Marylandtech
Please note: This site is in an active redesign. Some things might be a little off 🧐