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

Automate install of GuestAdditions #104

Closed
sfc-gh-rpughsley opened this issue Nov 16, 2016 · 9 comments
Closed

Automate install of GuestAdditions #104

sfc-gh-rpughsley opened this issue Nov 16, 2016 · 9 comments
Assignees
Milestone

Comments

@sfc-gh-rpughsley
Copy link

How about automating the installation of the Vbox Guest Additions CD so we can share folders with the host (and use locally installed dev tools)

@grtjn
Copy link
Owner

grtjn commented Nov 24, 2016

The baseboxes do come with vbguest additions, but not the right ones..

@grtjn
Copy link
Owner

grtjn commented Nov 24, 2016

centos-7.1 has vbguest additions 5.0.2
centos-7.2 has vbguest additions 5.0.12
centos-7.2 v2.3.0 (which I am going to release) has vbguest additions 5.1.6 which likely work with VBox 5.1.x and below..

@grtjn
Copy link
Owner

grtjn commented Nov 24, 2016

Perhaps I should consider requiring vagrant-vbguest, and configure it to automatically install if there is a mismatch: https://github.com/dotless-de/vagrant-vbguest

@grtjn grtjn self-assigned this Nov 24, 2016
@grtjn grtjn added the bug label Nov 24, 2016
@grtjn grtjn added this to the 1.0.3 milestone Nov 24, 2016
@grtjn
Copy link
Owner

grtjn commented Nov 24, 2016

Or maybe not automatically (usually not necessary), but at least mention these convenient command-line commands to check and fix things if there is trouble:

https://github.com/dotless-de/vagrant-vbguest#running-as-a-command

@grtjn
Copy link
Owner

grtjn commented Nov 25, 2016

I published newer baseboxes, and will add docs about vagrant-vbguest in the README. Closing this ticket..

@grtjn grtjn closed this as completed Nov 25, 2016
@grtjn
Copy link
Owner

grtjn commented Jan 20, 2017

New report:

Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

@grtjn grtjn reopened this Jan 20, 2017
@grtjn
Copy link
Owner

grtjn commented Jan 20, 2017

fixed with following steps..

Install kernel include headers (required by VBoxLinuxAdditions):

Double check that kernel extensions are up and running:

  • sudo modprobe vboxsf
  • sudo service VBoxService start

@grtjn grtjn closed this as completed Jan 20, 2017
@grtjn grtjn reopened this Jan 20, 2017
@grtjn
Copy link
Owner

grtjn commented Mar 20, 2017

The plugin vagrant-vbguest seems to default to updating available additions, which is only really necessary if VBox has a larger major or minor version. I'd prefer if vagrant-vbguest does not automatically mess things up, so I'd advice adding this to your Vagrantfile if it isn't in there yet:

    if Vagrant.has_plugin?("vagrant-vbguest")
        config.vbguest.no_install = true
    end

I'll add that by default to the Vagrantfile of mlvagrant

@grtjn
Copy link
Owner

grtjn commented May 12, 2017

The end conclusion is, it should not be necessary to install guestadditions automatically. Baseboxes 6.8 and 7.2 have pretty recent guestadditions that are compatible up to vbox 5.1.4 and a little beyond probably. A tool like vagrant-vbguest expects installers and compile tools to be available upfront, which is not the case, causing it to leave a worse state than without attempting guestadditions updates.

I'll freshen up baseboxes again with newer copies from the CHEF project if there are enough requests, and if those become available in the CHEF project.

I disable auto-install via #111. Closing this as wontfix..

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

No branches or pull requests

2 participants