VM can't be started with vbox 4.3 #10

mplatt · 2014-01-02T14:10:42Z

Documentation should reflect which version of Virtualbox is necessary to start the virtual machine through vagrant.

Win8 with VirtualBox Version: 4.3 and Vagrant 1.4.2 fails with the following message:

Guest Additions Version: 4.1.12
VirtualBox Version: 4.3
[default] Setting hostname...
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
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 vagrant | cut -d: -f3`
/vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` /vagrant /vagrant

The text was updated successfully, but these errors were encountered:

faabsen · 2014-01-02T14:16:15Z

Same on MacOSX 10.9.1 with VirtualBox Version: 4.3.6 and Vagrant 1.3.5

physikerwelt · 2014-01-02T14:33:31Z

Currently I'm using Vagrant 1.4.0 and VirtualBox 4.3.6 but the version should not patter too much. Do you have suficcient access rights. In unix you need to be root and in windows I had to enter the admin password.

physikerwelt · 2014-01-02T14:33:50Z

@hendrikheller @AndreG-P what versions do you use?

mplatt · 2014-01-02T15:00:56Z

@physikerwelt I have reproduced the issue with the versions mentioned. Steps to reproduce the problem:

Reproduction steps on Windows 8-Pro x64

Retrieve and install VirtualBox 4.3.6 for Windows hosts from http://download.virtualbox.org/virtualbox/4.3.6/VirtualBox-4.3.6-91406-Win.exe with default settings
Retrieve and install Vagrant 1.4.0 for Windows from https://dl.bintray.com/mitchellh/vagrant/Vagrant_1.4.0.msi
Git clone revision 02699f6 from https://github.com/TU-Berlin/dopa-vm to C:\vagrant-up
Run vagrant up as administrator in C:\vagrant-up

Output:

c:\dopa-vm-master>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise-cloud'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] -- 8090 => 8090 (adapter 1)
[default] -- 8081 => 8081 (adapter 1)
[default] -- 8088 => 8088 (adapter 1)
[default] -- 50075 => 50075 (adapter 1)
[default] -- 50070 => 50071 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
DL is deprecated, please use Fiddle
[default] Machine booted and ready!
[default] The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.

Guest Additions Version: 4.1.12
VirtualBox Version: 4.3
[default] Setting hostname...
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
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 vagrant | cut -d: -f3`
/vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` /vagrant /vagrant

physikerwelt · 2014-01-02T15:32:56Z

mh.. you probably cloned to C:\dopa-vm-master ?
I tried again with the following procedure
run->cmd-
cd C:\dopa-vm-master\dopa-vm-master
vagrant up
and everything looks fine

C:\dopa-vm-master\dopa-vm-master>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise-cloud'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Fixed port collision for 22 => 2222. Now on port 2200.
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2200 (adapter 1)
[default] -- 8090 => 8090 (adapter 1)
[default] -- 8081 => 8081 (adapter 1)
[default] -- 8088 => 8088 (adapter 1)
[default] -- 50075 => 50075 (adapter 1)
[default] -- 50070 => 50071 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
DL is deprecated, please use Fiddle
[default] Machine booted and ready!
[default] The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.

Guest Additions Version: 4.1.12
VirtualBox Version: 4.3
[default] Setting hostname...
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] -- /dopa-vm
[default] -- /tmp/vagrant-puppet-1/manifests
[default] -- /tmp/vagrant-puppet-1/modules-0
[default] Running provisioner: shell...
[default] Running: inline script
[default] Running provisioner: puppet...
Running Puppet with site.pp...
info: Loading facts in /tmp/vagrant-puppet-1/modules-0/stdlib/lib/facter/facter_
dot_d.rb
info: Loading facts in /tmp/vagrant-puppet-1/modules-0/stdlib/lib/facter/pe_vers
ion.rb
info: Loading facts in /tmp/vagrant-puppet-1/modules-0/stdlib/lib/facter/puppet_
vardir.rb
info: Loading facts in /tmp/vagrant-puppet-1/modules-0/stdlib/lib/facter/root_ho
me.rb
warning: Could not retrieve fact fqdn
debug: importing '/tmp/vagrant-puppet-1/manifests/base.pp' in environment produc
tion
debug: importing '/tmp/vagrant-puppet-1/manifests/roles.pp' in environment produ
ction
debug: importing '/tmp/vagrant-puppet-1/manifests/hadoop.pp' in environment prod
uction
debug: importing '/tmp/vagrant-puppet-1/manifests/manifests.d/dummy.pp' in envir
onment production
debug: Executing '/vagrant/puppet/extra/config-version'
warning: Host is missing hostname and/or domain: dopa-vm
debug: importing '/tmp/vagrant-puppet-1/modules-0/apt/manifests/init.pp' in envi
ronment production
debug: Automatically imported apt from apt into production
debug: importing '/tmp/vagrant-puppet-1/modules-0/apt/manifests/ppa.pp' in envir
onment production
debug: Automatically imported apt::ppa from apt/ppa into production
debug: Scope(Class[Apt]): Retrieving template apt/wikimedia.list.erb
debug: template[/tmp/vagrant-puppet-1/modules-0/apt/templates/wikimedia.list.erb
]: Bound template variables for /tmp/vagrant-puppet-1/modules-0/apt/templates/wi
kimedia.list.erb in 0.01 seconds
debug: template[/tmp/vagrant-puppet-1/modules-0/apt/templates/wikimedia.list.erb
]: Interpolated template /tmp/vagrant-puppet-1/modules-0/apt/templates/wikimedia
.list.erb in 0.00 seconds
debug: Failed to load library 'selinux' for feature 'selinux'
debug: importing '/tmp/vagrant-puppet-1/modules-0/env/manifests/init.pp' in envi
ronment production
debug: Automatically imported env from env into production
debug: importing '/tmp/vagrant-puppet-1/modules-0/env/manifests/profile.pp' in e
nvironment production
...

in the virtualbox ui the mount points should look like
http://snag.gy/Iwnlt.jpg

mplatt · 2014-01-02T16:22:29Z

Yes, sorry. The path c:\vagrant-up was a copy&paste mistake.

The contents of c:\dopa-vm-master read:

C:\dopa-vm-master>dir
 Volume in drive C has no label.
 Volume Serial Number is BA51-745F

 Directory of C:\dopa-vm-master

02/01/2014  15:54    <DIR>          .
02/01/2014  15:54    <DIR>          ..
02/01/2014  15:48                39 .gitattributes
02/01/2014  15:48               157 .gitignore
02/01/2014  15:48                92 .gitreview
02/01/2014  15:55    <DIR>          .vagrant
02/01/2014  15:48    <DIR>          lib
02/01/2014  15:48             1,150 LICENSE
02/01/2014  15:48             2,920 MapReduceWordCount.md
19/12/2013  12:19    <DIR>          puppet
02/01/2014  15:48             3,991 README.md
02/01/2014  15:48               106 script.meteor
02/01/2014  15:48               126 test.json
02/01/2014  16:26             3,830 Vagrantfile
02/01/2014  15:48             1,532 Vagrantfile-extra-example.rb
              10 File(s)         13,943 bytes
               5 Dir(s)  428,608,663,552 bytes free

The virtualbox shared folders gui looks similar to your example:

Still, vagrant up quits after the following statement without importing any artifacts. Subsequently, HDFS web frontend, MapReduce JobTracker and the PACT web interface are not accesible.

[default] Mounting shared folders...
[default] -- /vagrant
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 vagrant | cut -d: -f3`
/vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` /vagrant /vagrant

faabsen · 2014-01-02T17:03:06Z

Still not working, is it necessary to be logged in the tu network?

mplatt · 2014-01-02T17:18:59Z

The same issue can be reproduced on another test system with the following specifications:

Ubuntu Release 12.10 (quantal) 64-bit Kernel Linux 3.5.0-44-generic
vagrant_1.4.2_x86_64
Virtualbox 4.1.18

Take the following steps to reproduce:

sudo apt-get install virtualbox

wget https://dl.bintray.com/mitchellh/vagrant/vagrant_1.4.2_x86_64.deb
sudo dpkg -i vagrant_1.4.2_x86_64.deb

git clone https://github.com/TU-Berlin/dopa-vm.git
cd dopa-vm/

vagrant up

The output following this command is:

Bringing machine 'default' up with 'virtualbox' provider...
[default] Box 'precise-cloud' was not found. Fetching box from specified URL for
the provider 'virtualbox'. Note that if the URL does not have
a box for this provider, you should interrupt Vagrant now and add
the box yourself. Otherwise Vagrant will attempt to download the
full box prior to discovering this error.
Downloading box from URL: https://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-amd64-vagrant-disk1.box
Extracting box...te: 551k/s, Estimated time remaining: 0:00:01))
Successfully added box 'precise-cloud' with provider 'virtualbox'!
[default] Importing base box 'precise-cloud'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] -- 8090 => 8090 (adapter 1)
[default] -- 8081 => 8081 (adapter 1)
[default] -- 8088 => 8088 (adapter 1)
[default] -- 50075 => 50075 (adapter 1)
[default] -- 50070 => 50071 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
[default] Machine booted and ready!
[default] Setting hostname...
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
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 vagrant | cut -d: -f3` /vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` /vagrant /vagrant

physikerwelt · 2014-01-02T17:29:39Z

mh I pasted your commands... no error occured... That said, it could be realated to
https://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-amd64-vagrant-disk1.box
... let me see if I can get rid of my local copy

mplatt · 2014-01-02T17:46:25Z

@physikerwelt That could be the reason.
FYI: If I start the virtual machine with gui, the state it gets stuck in is the following:

physikerwelt · 2014-01-02T18:09:37Z

Yes.

I got the same error! Now... I start to figure out the problem.

physikerwelt · 2014-01-02T18:32:09Z

I downloaded the image at 2013-12-11 16:00:29 UTC but this file does not seem to be availible right now.
At the moment it seems as if I get the same problem with the offical version from
http://www.mediawiki.org/wiki/MediaWiki-Vagrant

However I have to double check that before filing a bug report there.

physikerwelt · 2014-01-03T10:58:43Z

I submitted a bug at
https://bugzilla.wikimedia.org/show_bug.cgi?id=59243

physikerwelt · 2014-01-06T12:19:52Z

It seems as the problem has been resolved with the latest box image.
run

vagrant box remove precise-cloud

to clean you local caches.

mplatt closed this as completed Jan 2, 2014

mplatt reopened this Jan 2, 2014

physikerwelt closed this as completed Jan 6, 2014

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

VM can't be started with vbox 4.3 #10

VM can't be started with vbox 4.3 #10

mplatt commented Jan 2, 2014

faabsen commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

mplatt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

mplatt commented Jan 2, 2014

faabsen commented Jan 2, 2014

mplatt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

mplatt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

physikerwelt commented Jan 3, 2014

physikerwelt commented Jan 6, 2014

VM can't be started with vbox 4.3 #10

VM can't be started with vbox 4.3 #10

Comments

mplatt commented Jan 2, 2014

faabsen commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

mplatt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

mplatt commented Jan 2, 2014

faabsen commented Jan 2, 2014

mplatt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

mplatt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

physikerwelt commented Jan 2, 2014

physikerwelt commented Jan 3, 2014

physikerwelt commented Jan 6, 2014