Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update

discussions.apple.com

Post reply on HN
Print view View original

1–10 of 54 posts

Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update

#3

Post by zrail »

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.

Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update

#6

Post by elithrar »

zrail wrote: post #3

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.

> 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...

Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update

#7

Post by webjprgm »

igorgue wrote: post #4

Basically: 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 :(

Is there a discussion with details on the issue? Parallels and VMWare release new versions all the time for compatibility issues, they just fix them before the update comes so their new version is ready. Should VirtualBox just fix the bug on their side, or is this really an Apple issue?

Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update

#8

Post by zrail »

elithrar wrote: post #6
zrail wrote: post #3

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.

> 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.

Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update

#9

Post by igorgue »

webjprgm wrote: post #7
igorgue wrote: post #4

Basically: 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 :(

Is there a discussion with details on the issue? Parallels and VMWare release new versions all the time for compatibility issues, they just fix them before the update comes so their new version is ready. Should VirtualBox just fix the bug on their side, or is this really an Apple issue?

I'm not sure who to blame, these are the details everyone is posting so far: https://www.virtualbox.org/ticket/10965 It seems like the VirtualBox community was talking about this problem for a long time already, since early september.

Re: VirtualBox broken on Ivy Bridge Macbooks after 10.8.2 and Firmware Update

#10

Post by vosper »

jeffh wrote: post #5

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).

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 making a significant slice of revenue (or any?) from it.

Post reply on HN