Upgrading to Virtualbox 4.3.0 causes multiple bugs in Vagrant installation

[jtakayama]

Description:

The "precise32" base box that is used for the Makahiki virtual machine deployment uses VirtualBox Guest Additions 4.2.0. Virtualbox 4.3.0 (and presumably any later 4.3.x versions) provide VirtualBox Guest Additions 4.3.0.

A "precise32" Vagrant virtual machine that was created under an earlier 4.2.x version of Virtualbox and is run on a host operating system with VirtualBox 4.3.0 or later installed may experience shared folder issues and may be unable to build Sphinx documentation.

A "precise32"-based virtual machine that is created under Vagrant 1.3.5 and VirtualBox 4.3.0 will fail to copy configuration files onto the virtual machine from the Vagrant shared folder. However, the provisioning script will incorrectly report that the operations were successful.

Affects

Vagrant virtual machine installations using:

• Vagrant 1.3.5
• Virtualbox 4.3.0
• Virtual machines based on the "precise32" base box (Ubuntu 12.04)

  Resolution

Makahiki on Vagrant will not officially support Virtualbox versions greater than 4.2.18.

For users that need to use Virtualbox 4.3.0, an alternate installation method which uses the third-party vbguest plugin (https://github.com/dotless-de/vagrant-vbguest) is being tested.

[jtakayama]

I re-tested this with VirtualBox 4.3.8 + Vagrant 1.4.3, and the shared folder and Sphinx issues no longer occur in the virtual machine. This issue will be closed after the documentation is changed.

[jtakayama]

Closed following merge of pull request GH-603.