Can't mount /vagrant after building Ubuntu 12.04 basebox #389

Closed
polivers opened this Issue Sep 22, 2012 · 3 comments

Projects

None yet

3 participants

@polivers

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

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?

@gpsnail

Hello,

In my case, it happens when there is an upgrade of the kernel host ?

Did you upgrade the host ?

BR

@jedi4ever
Owner

Is probably do lacking dkms so the kernel modules don't work after reboot.

Dkms will be activated when the templates will be cleaned

@jedi4ever jedi4ever closed this Feb 20, 2013
@gpsnail

A way to solve this issue is to rebuild kernel module of VB :
sudo /etc/init.d/vboxdrv setup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment