After altering postinstall.sh to install VBoxGuestAdditions for 4.2.0 (rather than VBoxGuestAdditions for 4.2.1), vagrant basebox validate passes all tests.
However, after creating a vagrant box and booting, I get:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -t vboxsf -o uid=id -u vagrant,gid=id -g vagrant v-root /vagrant
id -u vagrant
id -g vagrant
Running that mount command in the running vagrant box gives:
mount: unknown filesystem type 'vboxsf'
This is probably due to the VBoxGuestAdditions being installed in the running kernel (which is updated during the installation), so after a reboot vboxsf is not a valid filesystem module.
Is it possible to run the postinstall.sh after a reboot?
In my case, it happens when there is an upgrade of the kernel host ?
Did you upgrade the host ?
Is probably do lacking dkms so the kernel modules don't work after reboot.
Dkms will be activated when the templates will be cleaned
A way to solve this issue is to rebuild kernel module of VB :
sudo /etc/init.d/vboxdrv setup