31–40 of 54 posts
Earlier quoted context omitted.
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
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 :(
I'd be interested in knowing whether this is genuinely a bug on Apple's side or whether it's something that VirtualBox should have been aware of. It sounds like a bug, but if there's an issue with virtualization surely VMWare and Parallels would also have broken functionality as well.
The "VMX root mode" problem is known since at least 2008. On Linux hosts it's been possible to disable whatever puts the CPU into that mode, but that may be harder on OSX.
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 maki…
I also found Parallels 8 to have a bug where when using it with Ubuntu 12.04 XFCE, it would skip tabs in Chrome. Downgraded back to 7 - 8 was a free upgrade for me anyway.
Have you locked your framerate to 60 with fusion? I'd be interested in using fusion 5 if it has good performance compared to Parallels, especially now that 8 is buggy for me.
Earlier quoted context omitted.
I'd be interested in knowing whether this is genuinely a bug on Apple's side or whether it's something that VirtualBox should have been aware of. It sounds like a bug, but if there's an issue with virtualization surely VMWare and Parallels would also have broken functionality as well.
https://forums.virtualbox.org/viewtopic.php?p=52266 The "VMX root mode" problem is known since at least 2008. On Linux hosts it's been possible to disable whatever puts the CPU into that mode, but that may be harder on OSX.
Earlier quoted context omitted.
Vagrant will work with Parallels and VMWare in the next 12 months.
How are the chances of a version working with libvirt/kvm? Would be willing to help.
Earlier quoted context omitted.
https://forums.virtualbox.org/viewtopic.php?p=52266 The "VMX root mode" problem is known since at least 2008. On Linux hosts it's been possible to disable whatever puts the CPU into that mode, but that may be harder on OSX.
Thanks. Well that certainly makes it look like a VB issue rather than Apple, doesn't have an impact for me but I can imagine there's some very stressed developers this morning.
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 :(
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).
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.
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).
A main reason many of us use Virtualbox is because of Vagrant. If the same thing was easily possible (Is it?) with Parallels or VMWare we'd use those exclusively. I have licenses for both and use Parallels for any Windows-required work.