[mitchellh]

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

[jherdman]

Thanks for looking into this and working so hard on Vagrant. It's an awesome product.

[igorgue]

It's not your fault, I shouldn't have upgraded :( Thanks for vagrant it's really awesome!

[misnome]

I've used virtualbox for a while, but hadn't heard of Vagrant; it looks awesome. Luckily, this article popped up before I upgraded, so I'm sticking firmly to .1 now.

But I'm definitely going to download and use vagrant now :)

[blairwadman]

I've used VMWare for a while now, and it is indeed very fast. I've just started using Vagrant (thanks for creating it!) and love it, despite the slowness of Virtual Box. Good luck with VMWare support, I'm looking forward to that.