Feature: Defend against odd VirtualBox version coming from MacPorts

[stagrlee]

Installing VirtualBox from Macports seems to work well, but not with vagrant. The build coming out of Macports puts a goofy version together and I think that throws off vagrant (see below). On another OSX Snow Leopard box, I have VirtualBox installed via DMG and all is well.

$ vagrant --version
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
If VirtualBox is installed, it may be an incorrect version. Vagrant currently
requires VirtualBox 4.1.x. Please install the proper version to continue.

If you have an older or newer version of VirtualBox, please make sure you're
using the proper version of Vagrant. Ask the mailing list if you have questions.

$ VBoxManage --version
4.1.8_MacPortsr75467

[mitchellh]

Ah, thanks. This won't be an issue in the latest version of Vagrant (in git) but it will still read the version wrong. Marked to fix very soon.

[stagrlee]

Cross posted upstream https://trac.macports.org/ticket/32764

[mitchellh]

Fixed: 323663c

[stagrlee]

Just writting some notes on my experiments. I was moving from a MacBookPro to a 2010 Mac Mini when my trouble started hitting. Ends up it wasn't just the MacPorts version, it was also the 32 bit kernel...

Exception `LoadError' at /Users/Lee/.rvm/gems/ruby-1.8.7-p352@devops1/gems/ffi-1.0.11/lib/ffi/library.rb:100 - Could not open library '/Applications/MacPorts/VirtualBox.app/Contents/MacOS/VBoxXPCOMC.dylib': dlopen(/Applications/MacPorts/VirtualBox.app/Contents/MacOS/VBoxXPCOMC.dylib, 5): no suitable image found.  Did find:
    /Applications/MacPorts/VirtualBox.app/Contents/MacOS/VBoxXPCOMC.dylib: mach-o, but wrong architecture

Sure 'nuff

$ lipo -info /Applications/MacPorts/VirtualBox.app/Contents/MacOS/VBoxXPCOMC.dylib 
Non-fat file: /Applications/MacPorts/VirtualBox.app/Contents/MacOS/VBoxXPCOMC.dylib is architecture: i386

By default, this mac mini boots in 32bit mode but supports a 64 bit boot. Re-installing MacPorts....

[mitchellh]

That's no big deal anymore since the latest in Vagrant git now uses VBoxManage. :)

[stagrlee]

Nice, just read some code. You don't need to worry about the /Applications/MacPorts/VirtualBox.app path change that way. Very cool.

[stagrlee]

MacPorts version of VirtualBox is running well with Vagrant/VeeWee. Got it building vagrant base boxes nightly. Working with Funtoo project to host the box files. They are about 1.3 GBytes each.