When using the latest version of VirtualBox (v 4.3.10), the Vagrant box built via the packer script does not mount the "/vagrant" shared folder so the provisioning halts.
This is a known issue with the installation of the VBboxAdditions. The issue and the workaround are found here:
hashicorp/vagrant#3341
and here:
https://www.virtualbox.org/ticket/12879
The workaround is to add the symlink within the VM using this command:
sudo ln -s /opt/VBoxGuestAdditions-4.3.10/lib/VBoxGuestAdditions/usr/lib/VBoxGuestAdditions
This can be executed as an additional line in the packer serverconfig.json file after the VBoxAdditions have been installed. It also can be executed within the running VM (vagrant ssh) followed by a vagrant reload.
I have confirmed the issue and the fix works with both a Linux host and a Windows host.
This issue is apparently fixed in the upcoming v 4.3.11 release of VirtualBox.
When using the latest version of VirtualBox (v 4.3.10), the Vagrant box built via the packer script does not mount the "/vagrant" shared folder so the provisioning halts.
This is a known issue with the installation of the VBboxAdditions. The issue and the workaround are found here:
hashicorp/vagrant#3341
and here:
https://www.virtualbox.org/ticket/12879
The workaround is to add the symlink within the VM using this command:
This can be executed as an additional line in the packer serverconfig.json file after the VBoxAdditions have been installed. It also can be executed within the running VM (vagrant ssh) followed by a vagrant reload.
I have confirmed the issue and the fix works with both a Linux host and a Windows host.
This issue is apparently fixed in the upcoming v 4.3.11 release of VirtualBox.