Basically:<p>Oracle: We reported the bug a long time ago and still Apple released the update.<p>Apple: ...<p>Me: How the fuck am I going to work tomorrow? Maybe going full Vagrant wasn't a good idea after all :(
This is another benefit of still being on Lion. I didn't have to deal with weird homebrew issues and now I don't have to deal with this. I have not upgraded to Mountain Lion on any of my machines, and the way things are going I'm probably not going to until forced.
The (annoying, but working) workaround is the following:<p>I imported my Vagrant-managed Ubuntu 10.04.4 LTS VM into a trial copy of Parallels Desktop 8. I then logged into the VM manually using the Parallels VM window using the default Vagrant user / password (vagrant/vagrant) and changed the password for my custom Vagrantfile dev login. Then in Parallels I switched the networking on the VM to Bridge Mode (so I can access it via IP address on my local network).<p>Remarkably everything in the VM worked and I'm back to coding. Would like to see a quick fix for VirtualBox so I can get back to my Vagrant awesomeness.
Can anyone confirm this update does not break VirtualBox on the mid 2011 Macbook Air i7? I rely on Vagrant and am not feeling confident enough to update since the issue appears to be related to VT-x on the CPU
And somehow VMware Fusion doesn't have any problems after the same update ... sometimes you do get what you pay for (then again, I remember when an earlier Fusion update bricked itself, so YMMV).
It seems as though it will take a few more of these before Apple users learn what Windows users learned awhile ago -- there's rarely any good reason to upgrade any software, particularly your operating system, immediately upon release.
Has anyone installed the relevant firmware update <a href="https://support.apple.com/kb/DL1590" rel="nofollow">https://support.apple.com/kb/DL1590</a> for 2010 MacBook Airs? I'd like to know if that introduces the same bug.
From vbox forums, someone at Oracle:<p>"That said, I believe we're now far enough along to say that there will highly likely be at least a test build pretty soon. Certainly sooner than in two weeks..."<p><a href="https://forums.virtualbox.org/viewtopic.php?p=236591#p236591" rel="nofollow">https://forums.virtualbox.org/viewtopic.php?p=236591#p236591</a>