GuestAdditions seems to be installed (6.1.16) correctly, but not running.

[caschbre]

trafficstars

Issue Type

• Bug Report / Support Request

Your Environment

Vagrant 2.2.14
VirtualBox 6.1.16r140961
ansible 2.9.9
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/caschbre/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.8.6 (default, Sep 25 2020, 09:36:53) [GCC 10.2.0]

Your OS

• Linux (version)

Full console output

https://gist.github.com/caschbre/750cf29520ab1ad4276d6e67848b9664

Summary

I recently rebuilt my local Drupal 7 installation which already had drupalvm configured in the repo. I was previously using an older version of drupalvm so I updated to the most recent and then ran vagrant up. Everything seems to have provisioned and I'm able to access my local site. However every time I do a vagrant up I noticed that I'm seeing "GuestAdditions seems to be installed (6.1.16) correctly, but not running."

One change I did make to my local config.yml was to add the following to eliminate using vagrant-hostsupdater.

vagrant_plugins:                                                                                                                                                                                                                                                                      
  - name: vagrant-vbguest                                                                                                                                                                                                                                                             
  - name: vagrant-cachier                                                                                                                                                                                                                                                             
  # - name: vagrant-hostsupdater

[acasadoalonso]

Not a big deal ... but I have a similar error message for VBGUEST 6.1.18 Running: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.10 DISTRIB_CODENAME=groovy DISTRIB_DESCRIPTION="Ubuntu 20.10" and VirtualBox Version 6.1.18 r142142 (Qt5.14.2) and Vagrant 2.2.13

Log:

[drupalvm] GuestAdditions seems to be installed (6.1.18) correctly, but not running. update-initramfs: Generating /boot/initrd.img-4.15.0-112-generic VirtualBox Guest Additions: Starting. VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while. VirtualBox Guest Additions: To build modules for other installed kernels, run VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup VirtualBox Guest Additions: or VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all VirtualBox Guest Additions: Building the modules for kernel 4.15.0-112-generic. update-initramfs: Generating /boot/initrd.img-4.15.0-112-generic VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted Guest Additions got installed. However, they seem not be loaded correctly. Please restart the box running vagrant reload drupalvm

Restarting the VM makes no difference !!! Thanks for this great software. AC/.

[acasadoalonso]

On my previous comment I think that the problem is related to this message from installing the plugin:

vagrant plugin install vagrant-vbguest Vagrant v2.2.13 has a bug which prevents vagrant-vbguest to register probably. vagrant-vbguest will try to do the next best thing, but might not be working as expected. If possible, please upgrade Vagrant to >= 2.2.14

I will try with the newer version of Vagrant

[acasadoalonso]

Installing Vagrant 2.2.14 made no difference !!! except that the warning message disappeared of course !!!

The VM seems to working OK ... so not big deal !!!

[stale[bot]]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[UnKulMunki]

I just built a new Vagrant instance and I am still getting : " GuestAdditions seems to be installed (6.1.18) correctly, but not running. " and then: "Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. ..."

Vagrant ver: 2.2.16 VirtualBox ver: 6.1.18 r142142 Host Windows 10, Intel i7, 16 GB RAM Guest os: Ubuntu 16.04.7 LTS

[stale[bot]]

This issue is no longer marked for closure.

[UnKulMunki]

BootLog: vagrant up Bringing machine 'usactl' up with 'virtualbox' provider... ==> usactl: [vagrant-hostsupdater] Checking for host entries ==> usactl: [vagrant-hostsupdater] Writing the following entries to (C:/windows/system32/drivers/etc/hosts) ==> usactl: [vagrant-hostsupdater] 192.168.86.115 usactl.teki.cc # VAGRANT: 8441aecfad6ae731e55fad42be8dff87 (usactl) / 4bc0c5c6-1cac-4d8b-8728-435e24f1a9ab ==> usactl: Checking if box 'ubuntu/xenial64' version '20210429.0.0' is up to date... ==> usactl: Clearing any previously set forwarded ports... ==> usactl: Clearing any previously set network interfaces... ==> usactl: Preparing network interfaces based on configuration... usactl: Adapter 1: nat usactl: Adapter 2: hostonly ==> usactl: Forwarding ports... usactl: 22 (guest) => 2225 (host) (adapter 1) usactl: 80 (guest) => 8085 (host) (adapter 1) usactl: 3306 (guest) => 33065 (host) (adapter 1) ==> usactl: Running 'pre-boot' VM customizations... ==> usactl: Booting VM... ==> usactl: Waiting for machine to boot. This may take a few minutes... usactl: SSH address: 127.0.0.1:2225 usactl: SSH username: vagrant usactl: SSH auth method: private key ==> usactl: Machine booted and ready! [usactl] GuestAdditions seems to be installed (6.1.22) correctly, but not running. update-initramfs: Generating /boot/initrd.img-4.4.0-210-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. VirtualBox Guest Additions: Starting. VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while. VirtualBox Guest Additions: To build modules for other installed kernels, run VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup VirtualBox Guest Additions: or VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all VirtualBox Guest Additions: Building the modules for kernel 4.4.0-210-generic.

VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted Restarting VM to apply changes... ==> usactl: Attempting graceful shutdown of VM... ==> usactl: Booting VM... ==> usactl: Waiting for machine to boot. This may take a few minutes... ==> usactl: Machine booted and ready! ==> usactl: Checking for guest additions in VM... ==> usactl: Setting hostname... ==> usactl: Configuring and enabling network interfaces... ==> usactl: Mounting shared folders... usactl: /vagrant => D:/Source/RHT_USAClayTarget 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=33,_netdev vagrant /vagrant

The error output from the command was:

: No such device

---

Commenting out the VirtualBox drive type in the Vagrant config file will let it start the machine correctly.

[jdilley]

any updates to this?

[geerlingguy]

Note that there are new box versions released as of last week for my other boxes. I haven't done an update to drupal-vm yet though :/

[geerlingguy]

I'm building a new version of the drupal-vm base box currently; will be posted here: https://app.vagrantup.com/geerlingguy/boxes/drupal-vm