Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guest Additions are installed without dkms support #332

Closed
breakpointninja opened this issue Mar 11, 2015 · 4 comments
Closed

Guest Additions are installed without dkms support #332

breakpointninja opened this issue Mar 11, 2015 · 4 comments

Comments

@breakpointninja
Copy link

If the guest linux kernel version gets updated then Vagrant fails to mount host directories. This is because the kernel module vboxsf was compiled for an older version of the kernel.
This gets fixed after installing dkms and then reinstalling guest additions.
yum install dkms

It would be much more convenient if guest additions were compiled from the start with dkms support.

Example error:
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that                                                                                                                                        
the guest additions are properly installed in the guest and                                                                                                                                          
can work properly. The command attempted was:                                                                                                                                                        

mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3`,dmode=777,fmode=666 db_data /db_data                                                                                 
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant`,dmode=777,fmode=666 db_data /db_data                                                                                                      

The error output from the last command was:                                                                                                                                                          

/sbin/mount.vboxsf: mounting failed with the error: No such device
@juliandunn
Copy link
Contributor

So the reason the boxes are set up this way is to keep their size down. Otherwise you need a whole C compiler, make, etc. on the box which is undesirable.

Generally, the use cases for the Bento boxes are for userland testing, which are generally agnostic to the kernel version.

@ghost
Copy link

ghost commented Mar 19, 2015

You could alternatively use veewee for they compile Guest Additions with dkms.

@juliandunn
Copy link
Contributor

Or just maintain a fork if you don't like how we set up these boxes 😁

I'm closing this because it's "by design".

@breakpointninja
Copy link
Author

Thanks. I will go ahead and try veewee.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants