DiViMe icon indicating copy to clipboard operation
DiViMe copied to clipboard

GuestAdditions versions and shared folders, test failed

Open bfmalle opened this issue 6 years ago • 1 comments

vagrant installed, but toward the end I received these messages:

Got different reports about installed GuestAdditions version: Virtualbox on your host claims: 4.2.0 VBoxService inside the vm claims: 6.0.10

then a little further down:

==> default: Mounting shared folders... default: /vagrant => /Users/bfmalle/DiViMe 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

Probably unsurprisingly, the test didn't work:

$ vagrant ssh -c "launcher/test.sh" bash: launcher/test.sh: No such file or directory Connection to 127.0.0.1 closed.

** Running vagrant 2.2.4 on MacBook Pro (15-inch, 2017), 2.8 GHz Intel Core i7, 16 GB 2133 MHz LPDDR3, MacOS 10.14.5 **

bfmalle avatar Jul 24 '19 17:07 bfmalle

Oh dear, I would suggest to rebuild the entire VM, but this has probably happened already. Would you be able to attach the entire log file, plus provide the versions of the plugins and Virtualbox etc? The error referenced above is not typically an issue, because vagrant updates the guest additions as it builds the VM, and even without that it should work.

You may also be able to build the VM with the docker provider (https://www.vagrantup.com/docs/docker/basics.html)

fmetze avatar Jul 27 '19 22:07 fmetze