Page MenuHomePhabricator

Failed to mount folders in Linux guest.
Closed, ResolvedPublic

Description

Author: physik

Description:
Try the following to reproduce the error run
$ vagrant box remove precise-cloud
clone a fresh vagrant copy by
$ git clone https://gerrit.wikimedia.org/r/mediawiki/vagrant
$ cd vagrant
$ vagrant up
and you get the error

Failed to mount folders in Linux guest. This is usually beacuse
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 www-data | cut -d: -f3 /vagrant /vagrant
mount -t vboxsf -o uid=id -u vagrant,gid=id -g www-data /vagrant /vagrant

This was reproduced with various versions

  • Windows 8 Version: 4.3.6 and Vagrant 1.3.5,
  • Ubuntu 12.04 LTS apt dependencis
  • MacOSX 10.9.1 with VirtualBox Version: 4.3.6 and Vagrant 1.3.5
  • Win8 with VirtualBox Version: 4.3 and Vagrant 1.4.2
  • Ubuntu Release 12.10 (quantal) 64-bit Kernel Linux 3.5.0-44-generic vagrant_1.4.2_x86_64 Virtualbox 4.1.18

Maybe there was a major change in
https://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-amd64-vagrant-disk1.box

The origial error was found a modified version of the vm which I misued for teaching purposes
https://github.com/TU-Berlin/dopa-vm/issues/10

However, I think I have a systematically error somewhere in my system setup. So please try to reproduce the problem by yourself.


Version: unspecified
Severity: normal

Details

Reference
bz59243

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:18 AM
bzimport set Reference to bz59243.

physik wrote:

I tried it again with today’s version and the problem has disappeared.

[WORKSFORME if no identifiable commit]

physik wrote:

Similar problem with today's version of
https://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-amd64-vagrant-disk1.box

[default] Machine booted and ready!
GuestAdditions seems to be installed (4.1.12) correctly, but not running.
bash: line 2: /etc/init.d/vboxadd: No such file or directory
bash: line 2: /etc/init.d/vboxadd: No such file or directory
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/etc/init.d/vboxadd setup

Stdout from the command:

Stderr from the command:

bash: line 2: /etc/init.d/vboxadd: No such file or directory

swithching to

config.vm.box_url = 'http://files.vagrantup.com/precise64.box'

and running
vagrant destroy
vagrant box remove precise-cloud
vagrant up

resolves the problem

It might be a good idea to use a static link to a particular box version, i.e. with regard to reproducibility.

physik wrote:

The problem might be an old virtualbox version

vboxheadless --version
Oracle VM VirtualBox Headless Interface 4.1.12_Ubuntu
(C) 2008-2013 Oracle Corporation
All rights reserved.

4.1.12_Ubuntur77245

Can we add a minimal requirement for the virtualboxversion to
https://www.mediawiki.org/wiki/MediaWiki-Vagrant ?

swalling wrote:

*** Bug 63643 has been marked as a duplicate of this bug. ***

Created attachment 15110
"vagrant up" log

Attached:

Change 126137 had a related patch set uploaded by Ori.livneh:
Revert "Bundle vagrant-vbguest plugin"

https://gerrit.wikimedia.org/r/126137

Change 126137 merged by jenkins-bot:
Revert "Bundle vagrant-vbguest plugin"

https://gerrit.wikimedia.org/r/126137

swalling wrote:

After this patch, a git pull and vagrant provision has vagrant working as expected without any local hacks to lib/vagrant-vbguest.rb etc.

Thanks for the fix guys. :)