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
VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
11–20 of 54 posts
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#12And 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).
The other thing you get with Fusion (and Parallels, but not Virtual Box) is decent performance; in my office we're all running Ubuntu in Fusion on OSX - we were running Virtual Box until we realised our unit tests ran in half the time under Fusion. But that's pretty much what I'd expect from two companies in the business of virtualisation, versus one behemoth who really doesn't care - particularly if they're not maki…
Hm - is this just for Mac OS X or is this true for the windows version of virtualbox as well?
I was trying to find the difference between virtualbox and vmware player on the windows side.
Can't really decide between parallels and fusion though...I need to run some opengl stuff which isn't too complicated, but I'd rather it be solid. But I do like to use virtualbox to test some python/django/nginx builds so better ubuntu and networking support would be nice.
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#13Earlier quoted context omitted.
> I didn't have to deal with weird homebrew issues... Just out of curiosity: which weird issues? The only "issues" I had involved installing XQuartz, and chowning /usr/local/ back to me[1] [1]: http://robots.thoughtbot.com/post/27985816073/the-hitchhiker...
I don't actually know any details. All I know is that when several of my coworkers upgraded to 10.8 components of their homebrew setup stopped working. It may have been related to ruby.
If I remember correctly, I had to reinstall xcode to get it working again
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#14Basically: Oracle: We reported the bug a long time ago and still Apple released the update. Apple: ... Me: How the fuck am I going to work tomorrow? Maybe going full Vagrant wasn't a good idea after all :(
Just revert back to the backup you took right before you did the upgrade.
You DID do a backup, didn't you? You HAVE tested that your backups are working, by doing a complete recovery with them, right?
Right? ;)
My personal philosophy is to be cutting edge on my personal/hobby gear (like the last gen MB Pro I keep for, ah, movies and such), but not to do ANY same-day updates on anything even remotely required for work. That shit stays behind the times but reliable for paying the bills.
After I've seen the upgrades working in the wild for a week or two, and I have verified that all the stuff I need actually works like I need it to, THEN I'll do the upgrade on my work box. After backing it up, of course. Hell, I even have a text file with search phrases and forum URLs for the software I need to have working to make it easy and ensure I don't miss anything.
Call me crazy, but I've learned that lesson the hard way.
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#15Basically: Oracle: We reported the bug a long time ago and still Apple released the update. Apple: ... Me: How the fuck am I going to work tomorrow? Maybe going full Vagrant wasn't a good idea after all :(
(Vagrant creator here)
Ugh. This is a pretty bad situation. I took a look at the VirtualBox Darwin driver source code as well as the relevant method in the Darwin kernel (`host_vmxon`), and I can't see a workaround that I can meaningfully or confidently contribute. I'm hoping for a quick turnaround by Oracle or Apple on something here. :(
For the future, I've been working on VMWare support for some time now, and it should be ready in the next few months. These sorts of problems will be mitigated then by saying "oh, well you can just use Vagrant with X instead for now" (where X is some other virtualization layer).
For now, I'm sorry, I don't think there is anything I can do here.
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#16Earlier quoted context omitted.
The other thing you get with Fusion (and Parallels, but not Virtual Box) is decent performance; in my office we're all running Ubuntu in Fusion on OSX - we were running Virtual Box until we realised our unit tests ran in half the time under Fusion. But that's pretty much what I'd expect from two companies in the business of virtualisation, versus one behemoth who really doesn't care - particularly if they're not maki…
Hm - is this just for Mac OS X or is this true for the windows version of virtualbox as well? I was trying to find the difference between virtualbox and vmware player on the windows side. Can't really decide between parallels and fusion though...I need to run some opengl stuff which isn't too complicated, but I'd rather it be solid. But I do like to use virtualbox to test some python/django/nginx builds so better ubu…
> Can't really decide between parallels and fusion though
In case you haven't seen it, MacObserver did a comparison of Parallels to Fusion to VirtualBox recently (on the Mac):
http://www.macobserver.com/tmo/article/benchmarking-parallel...
Their conclusion is that Parallels 8 is a bit faster than VMWare Fusion 5 and both are much faster than VirtualBox. VirtualBox doesn't have nearly the 3D support of the others, so depending on what OpenGL stuff you try to run it might not work.
> Hm - is this just for Mac OS X or is this true for the windows version of virtualbox as well?
You mean is Parallels and Fusion more performant than VirtualBox? I'd be willing to bet that the commercial products in this arena are easily faster.
As for me, I have no real need for Windows, I just like to keep the ability to run Windows apps on rare occasion, so I've stopped paying for VMWare Fusion updates and plan to just use VirtualBox since I don't need the speed. It was Steam on the Mac that put an end to my need for really good Windows virtualization.
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#17Basically: Oracle: We reported the bug a long time ago and still Apple released the update. Apple: ... Me: How the fuck am I going to work tomorrow? Maybe going full Vagrant wasn't a good idea after all :(
Just revert back to the backup you took right before you did the upgrade. You DID do a backup, didn't you? You HAVE tested that your backups are working, by doing a complete recovery with them, right? Right? ;) My personal philosophy is to be cutting edge on my personal/hobby gear (like the last gen MB Pro I keep for, ah, movies and such), but not to do ANY same-day updates on anything even remotely required for work…
This seems to be based on an upgrade to the EFI firmware, in addition to the 10.8.2 update. While I've got verified backups for the OS, I'm not in the habit of regularly backing up the EFI firmware, nor do I know how I would restore it on my MBP.
Anyone got advice for backing up firmware on laptops to allow for roll-backs on breaking changes?
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#18Earlier quoted context omitted.
Just revert back to the backup you took right before you did the upgrade. You DID do a backup, didn't you? You HAVE tested that your backups are working, by doing a complete recovery with them, right? Right? ;) My personal philosophy is to be cutting edge on my personal/hobby gear (like the last gen MB Pro I keep for, ah, movies and such), but not to do ANY same-day updates on anything even remotely required for work…
This seems to be based on an upgrade to the EFI firmware, in addition to the 10.8.2 update. While I've got verified backups for the OS, I'm not in the habit of regularly backing up the EFI firmware, nor do I know how I would restore it on my MBP. Anyone got advice for backing up firmware on laptops to allow for roll-backs on breaking changes?
I'm not sure there is a way for an end-user to revert to a previous version once a firmware update has been successfully applied.
If it wasn't successful, you could use the firmware restore CD that came with the box, or create the CD to do that, but again, that only works for failed upgrade attempts.
I've had to do this once in the past, and the easiest way I could find was to just take it to the local Apple Support shop and get them to do it. They did it for me while I waited, and it didn't cost me anything but time. YMMV.
But good point... I'm not in the habit of backing up firmware.
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#19Earlier quoted context omitted.
The other thing you get with Fusion (and Parallels, but not Virtual Box) is decent performance; in my office we're all running Ubuntu in Fusion on OSX - we were running Virtual Box until we realised our unit tests ran in half the time under Fusion. But that's pretty much what I'd expect from two companies in the business of virtualisation, versus one behemoth who really doesn't care - particularly if they're not maki…
Hm - is this just for Mac OS X or is this true for the windows version of virtualbox as well? I was trying to find the difference between virtualbox and vmware player on the windows side. Can't really decide between parallels and fusion though...I need to run some opengl stuff which isn't too complicated, but I'd rather it be solid. But I do like to use virtualbox to test some python/django/nginx builds so better ubu…
Moving from VMWare Server to VirtualBox on Windows I found VirtualBox to be significantly faster.
Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update
#20Can 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
For what it's worth, I just updated to 4.1.22 on such a machine and a snapshotted VM resumed without any trouble.
Edit: And then also to 4.2.0 without trouble.