4 ms·

A couple important notes about this: * Vagrant is being updated to work with 4.3 now. A release should be out today or at the latest tomorrow. (UPDATE: Vagrant

A couple important notes about this: * Vagrant is being updated to work with 4.3 now. A release should be out today or at the latest tomorrow. (UPDATE: Vagrant 1.3.5 is now out and supports VirtualBox 4.3) * VirtualBox 4.3 doesn't run at all on Mavericks (10.9) because their kernel extensions aren't signed. OS X 10.9 requires signed kexts now. So the changelog where they said "limited" Mavericks support they actually should've said "no support". (UPDATE: Some people are reporting it is working for them on Mavericks. I can't get it to work. YMMV) Based on these two bullet points, I would stick with VirtualBox 4.2 for the time being. The bullet point that says "rewritten VT-x and AMD-V code" is especially vague and could be "super unstable virtual machine manager" just as easily as it can mean "slight performance improvements." So be careful. Other than that, it is good to see VirtualBox have some sort of big release. This is their first major ("4.x") release in over a year. I also want to note that if you are on Mavericks, VMware Fusion works perfectly. As a disclaimer to this sentence though: I make money from Vagrant + VMware users. I'm not trying to advertise that, I just want to state that Vagrant _itself_ is fine. VirtualBox 4.3 doesn't work. VirtualBox 4.2 does. VMware Fusion 5 and 6 does.

whalesalad 13y ago
Thanks a lot for this comment. After upgrading to Mavericks I had to ditch my hacked together and hand-compiled PHP setup, so I converted to Vagrant+Virtualbox. I'd have hated to break that with the upgrade to 4.3 haha.
- jtreminio 13y ago
  I made something for you: https://puphpet.com https://puphpet.com
CJefferson 13y ago
I tried googling for mac os x signed kernel extensions, but couldn't find anything useful. Is this an easy issue to fix (get free key, slap a signature on), or could this be a more serious issue?
- mitchellh 13y ago
  The change is still under NDA. If you sign into your Apple dev account and look up the WWDC talk on OS X kernel extension development, you'll find it within that slide deck. Deep, I know. I also reported the issue to the VirtualBox team many weeks ago and they confirmed the bug and know it exists. It just seems like it wasn't important enough for them to fix prior to release.
  - untog 13y ago
    Honestly, the fact that the change is under NDA seems like reason enough for them to not bother yet. Who knows what NDA violation an open source project could make in discussing how they are going to implement it.
    - glibgil 13y ago
      I know what NDA violation they could make. It is called "NDA violation". It is where you sign an NDA and then you disclose information. Release of source code could be considered a disclosure. Now Apple can go right ahead and do a whole lot of nothing against VirtualBox and Oracle because no one cares. Neither should you. Stop lionizing contract law. It is a civil matter and no big deal almost always and especially when no money has changed hands.
Xylakant 13y ago
> VirtualBox doesn't work. VMware does. I haven't tried Virtualbox 4.3 but Virtualbox 4.2 sort of works on Mavericks. The kernel extensions don't load on boot, but can be loaded manually. I blogged about that here http://asquera.de/development/2013/06/20/vagrant-on-mavericks/ http://asquera.de/development/2013/06/20/vagrant-on-maverick...
- mitchellh 13y ago
  Good catch. I updated that. Thanks!
  - alwillis 13y ago
    It also depends on how your Gatekeeper settings are set; mine are set to "Mac App store and indentified developers". The OS alerted me that the kexts were unsigned, it said it would load them anyway.
chrisrogers 13y ago
Curious. I went ahead and updated, as my use of VirtualBox isn't critical to my workflow. I received warning during install of the unsigned kexts, but the warning stated that they would be loaded anyway. I'm now running vbox 4.3 just fine on Mavericks GM.
aroch 13y ago
Unsigned extensions should run just fine under Mavericks, you'll get an error/warning message on first install but a reboot should load it fine
- Angostura 13y ago
  Does it perhaps depend on your Gatekeeper settings? which could explain the diverse experiences being reported.
  - aroch 13y ago
    It does, Gatekeeper has gotten a little more restrictive as the seeds have gone out (at least compared to where it started). If you don't have "allow me to install whatever I fucking want" checked Gatekeeper will refuse to load unsigned Kexts...which I suppose is ultimately not a bad thing. The majority of users have no idea what a kext is or recognize the security implications of them
yeukhon 13y ago
http://docs.vagrantup.com/v2/vmware/known-issues.html http://docs.vagrantup.com/v2/vmware/known-issues.html So this is now the only issue left. If I remember correct there used to be multiple issues with VMWare + Vagrant. I just checked now and seems only one left. Correct? I might actually switch to fusion + vagrant on my mac osx if the support is stable.
- mitchellh 13y ago
  That is correct. The adapter is continuously improved and is at a very stable point now.
- mafro 13y ago
  I can attest to the solid Vagrant+VMWare Fusion support. I've been using it for at least the last six months and have not seen a single problem. I've completely stopped using VirtualBox now! Good work mitchellh :)
taternuts 13y ago
Awesome, thanks for the information - I've been using VirtualBox + Vagrant nightly for the last few weeks with a huge smile on my face, I really love that tool. What a pain in the ass it is to get a native RoR dev. environment working...
aioprisan 13y ago
actually, Vagrant works on Mavericks but on every updated version, from beta to beta, I had to remove Vagrant completely and reinstall vagrant fresh.. the kernel extensions don't seem to carry over, but it definitely working on Mavericks

whalesalad 13y ago

Thanks a lot for this comment. After upgrading to Mavericks I had to ditch my hacked together and hand-compiled PHP setup, so I converted to Vagrant+Virtualbox. I'd have hated to break that with the upgrade to 4.3 haha.

jtreminio 13y ago
I made something for you: https://puphpet.com https://puphpet.com

CJefferson 13y ago

I tried googling for mac os x signed kernel extensions, but couldn't find anything useful. Is this an easy issue to fix (get free key, slap a signature on), or could this be a more serious issue?

mitchellh 13y ago
The change is still under NDA. If you sign into your Apple dev account and look up the WWDC talk on OS X kernel extension development, you'll find it within that slide deck. Deep, I know. I also reported the issue to the VirtualBox team many weeks ago and they confirmed the bug and know it exists. It just seems like it wasn't important enough for them to fix prior to release.
- untog 13y ago
  Honestly, the fact that the change is under NDA seems like reason enough for them to not bother yet. Who knows what NDA violation an open source project could make in discussing how they are going to implement it.
  - glibgil 13y ago
    I know what NDA violation they could make. It is called "NDA violation". It is where you sign an NDA and then you disclose information. Release of source code could be considered a disclosure. Now Apple can go right ahead and do a whole lot of nothing against VirtualBox and Oracle because no one cares. Neither should you. Stop lionizing contract law. It is a civil matter and no big deal almost always and especially when no money has changed hands.

Xylakant 13y ago

> VirtualBox doesn't work. VMware does. I haven't tried Virtualbox 4.3 but Virtualbox 4.2 sort of works on Mavericks. The kernel extensions don't load on boot, but can be loaded manually. I blogged about that here http://asquera.de/development/2013/06/20/vagrant-on-mavericks/ http://asquera.de/development/2013/06/20/vagrant-on-maverick...

mitchellh 13y ago
Good catch. I updated that. Thanks!
- alwillis 13y ago
  It also depends on how your Gatekeeper settings are set; mine are set to "Mac App store and indentified developers". The OS alerted me that the kexts were unsigned, it said it would load them anyway.

chrisrogers 13y ago

Curious. I went ahead and updated, as my use of VirtualBox isn't critical to my workflow. I received warning during install of the unsigned kexts, but the warning stated that they would be loaded anyway. I'm now running vbox 4.3 just fine on Mavericks GM.

aroch 13y ago

Unsigned extensions should run just fine under Mavericks, you'll get an error/warning message on first install but a reboot should load it fine

Angostura 13y ago
Does it perhaps depend on your Gatekeeper settings? which could explain the diverse experiences being reported.
- aroch 13y ago
  It does, Gatekeeper has gotten a little more restrictive as the seeds have gone out (at least compared to where it started). If you don't have "allow me to install whatever I fucking want" checked Gatekeeper will refuse to load unsigned Kexts...which I suppose is ultimately not a bad thing. The majority of users have no idea what a kext is or recognize the security implications of them

yeukhon 13y ago

http://docs.vagrantup.com/v2/vmware/known-issues.html http://docs.vagrantup.com/v2/vmware/known-issues.html So this is now the only issue left. If I remember correct there used to be multiple issues with VMWare + Vagrant. I just checked now and seems only one left. Correct? I might actually switch to fusion + vagrant on my mac osx if the support is stable.

mitchellh 13y ago
That is correct. The adapter is continuously improved and is at a very stable point now.
mafro 13y ago
I can attest to the solid Vagrant+VMWare Fusion support. I've been using it for at least the last six months and have not seen a single problem. I've completely stopped using VirtualBox now! Good work mitchellh :)

taternuts 13y ago

Awesome, thanks for the information - I've been using VirtualBox + Vagrant nightly for the last few weeks with a huge smile on my face, I really love that tool. What a pain in the ass it is to get a native RoR dev. environment working...

aioprisan 13y ago

actually, Vagrant works on Mavericks but on every updated version, from beta to beta, I had to remove Vagrant completely and reinstall vagrant fresh.. the kernel extensions don't seem to carry over, but it definitely working on Mavericks