Yep, the issue here seems to be that VirtualBox needs to be updated to version 4.2.20. Unfortunately, if you are using an older version of VirtualBox and you select the "Check for updates" menu item with VirtualBox, it will often report incorrectly that it is using the latest version, when in fact it needs to be updated. I ran into this issue too.
On Monday, January 12, 2015 at 11:27:50 AM UTC-8,
kel...@berkeley.edu wrote:
virtual box 4.2.12