Laravel Homestead Vagrant - "vboxsf" unavailable issue

Question

So, I tried to install Laravel Homestead through Vagrant / VirtualBox. It worked, but now it does not work at all. I have included what is being returned from running vagrant up in addition to the /var/log/vboxadd-install.log log file specified in the error from the guest machine. Below are all version numbers for my current setup.

OS: Windows 8.1 (64-bit), VirtualBox: 4.3.26, Vagrant: 1.7.2

Here is the result of running the vagrant up command

 PS C:\Users\brand_000\Homestead> vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'laravel/homestead' is up to date... ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 80 => 8000 (adapter 1) default: 443 => 44300 (adapter 1) default: 3306 => 33060 (adapter 1) default: 5432 => 54320 (adapter 1) default: 22 => 2222 (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection timeout. Retrying... default: Warning: Connection timeout. Retrying... ==> default: Machine booted and ready! Got different reports about installed GuestAdditions version: Virtualbox on your host claims: 4.3.18 VBoxService inside the vm claims: 4.3.8 Going on, assuming VBoxService is correct... GuestAdditions versions on your host (4.3.26) and guest (4.3.8) do not match. Got different reports about installed GuestAdditions version: Virtualbox on your host claims: 4.3.18 VBoxService inside the vm claims: 4.3.8 Going on, assuming VBoxService is correct... Reading package lists... Building dependency tree... Reading state information... linux-headers-3.16.0-23-generic is already the newest version. dkms is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Copy iso file C:\Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso mount: /dev/loop0 is write-protected, mounting read-only Installing Virtualbox Guest Additions 4.3.8 - guest version is 4.3.8 Verifying archive integrity... All good. Uncompressing VirtualBox 4.3.8 Guest Additions for Linux............ VirtualBox Guest Additions installer Removing installed version 4.3.8 of VirtualBox Guest Additions... Copying additional installer modules ... Installing additional modules ... Removing existing VirtualBox DKMS kernel modules ...done. Removing existing VirtualBox non-DKMS kernel modules ...done. Building the VirtualBox Guest Additions kernel modules The headers for the current running kernel were not found. If the following module compilation fails then this could be the reason. Building the main Guest Additions module ...done. Building the shared folder support module ...fail! (Look at /var/log/vboxadd-install.log to find out what went wrong) Doing non-kernel setup of the Guest Additions ...done. Installing the Window System drivers Could not find the X.Org or XFree86 Window System, skipping. An error occurred during installation of VirtualBox Guest Additions 4.3.8. Some functionality may not work as intended. In most cases it is OK that the "Window System drivers" installation failed. ==> default: Checking for guest additions in VM... ==> default: Setting hostname... ==> default: Configuring and enabling network interfaces... ==> default: Mounting shared folders... default: /vagrant => C:/Users/brand_000/Homestead Failed to mount folders in Linux guest. This is usually because 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 error output from the last command was: /sbin/mount.vboxsf: mounting failed with the error: No such device PS C:\Users\brand_000\Homestead> 

Here is the contents of the error file. PasteBin Download error file @ / var / log / vboxadd-install.log

I installed the vbguest vagrant plugin for several guides and answers here in StackOverflow, but so far nothing has worked. Even tried to downgrade VirtualBox to 4.3.8 and another version with no luck. I followed the installation instructions for Laravel Homestead correctly. As I said, he worked in the past. Any suggestions?

Answer 1

Change scripts\homestead.rb , change:

 mount_opts = folder["type"] == "nfs" ? ['actimeo=1'] : [] 

to

 mount_opts = folder["type"] == "nfs" ? [''] : [] 

Then install VBoxGuestAdditions:

 C:\Homestead> vagrant plugin install vagrant-vbguest C:\Homestead> vagrant up C:\Homestead> vagrant ssh $ sudo ln -s /opt/VBoxGuestAdditions-4.3.18/lib/VBoxGuestAdditions /usr/lib/VBoxGuestAdditions $ sudo apt-get install --yes dkms linux-headers-3.16.0-23-generic $ sudo /etc/init.d/vboxadd setup $ exit C:\Homestead> vagrant halt C:\Homestead> vagrant up 

Answer 2

Looks like Laravel docs 5.0 is still the guide for Homestead 1.x. But Laravel docs 4.2 already contains a guide for Homestead 2.x. Since laravel/homestead already on version 2, now you better follow 4.2 docs.

Another good source is the laracasts homestead 2 introduction .

Answer 3

I solved a similar problem as the output from vagrant up was as follows:

 Installing Virtualbox Guest Additions 5.0.4 - guest version is 4.3. Verifying archive integrity... All good. Uncompressing VirtualBox 5.0.4 Guest Additions for Linux........... VirtualBox Guest Additions installer Removing installed version 4.3.14 of VirtualBox Guest Additions... Copying additional installer modules ... Installing additional modules ... Removing existing VirtualBox non-DKMS kernel modules[ OK ] Building the VirtualBox Guest Additions kernel modules Building the main Guest Additions module[FAILED] (Look at /var/log/vboxadd-install.log to find out what went wrong) 

and then later

 Failed to mount folders in Linux guest. This is usually because 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 

Symptoms

My stroller script worked for quite some time, but yesterday I changed the physical hardware for my drives by moving the drives from the Lenovo T520 to T530. Ok with this, I had to update several drivers.

Thus, I was not able to run my firewall script on new hardware on the same drive.

Cause

The reason was the new graphics card, the NVIDIA graphics card. This card has a GPU processor that connects to every process on the computer and tries to determine if it uses a GPU or not. By default, the GPU on my machine was configured to connect the GPU to each running process.

This processor connecting this NVIDIA effectively uses VirtualBox so that VBGuestAdditions cannot correctly install drivers or at least say that something is missing.

Decision

Open NVIDIA Control => 3D Settings → Manage 3D Settings. Then select the "Program Settings" tab.

Now the trick is to add VirtualBox.exe to the "1. Select a program to configure" drop-down list, and then set "2. Select your preferred graphics handler for this program" to "Integrated Graphics"

It does the whole trick. Vagrant up spins the machine and does not throw the message "Failed to install folders on the Linux guest system"

I’m exploring this program again and again for the whole day.

Answer 4

This works for me on Linux, I think it will solve the problem on Windows as well.

Fast solution for unsuccessful installation of folders in the guest version of Linux.

Add the following line to your Homestead / Vagrantfile:

 config.vbguest.auto_update = false 

Your Homestead / Vagrantfile should look like this:

 /... Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| # To avoid install and uninstall VBoxGuessAdditions during vagrant provisioning. config.vbguest.auto_update = false .../ 

Save it and run

 $ vagrant destroy --force $ vagrant up 

Answer 5

Try installing VBox Guest Additions to support folder sharing and VirtualBox Oracle VM VirtualBox Extension Pack for additional support for specific devices.

Using Vagrant, you can run:

 vagrant plugin install vagrant-vbguest vagrant vbguest 

Or install manually .

Answer 6

Just delete the line type: "nfs" from the Homestead.yaml file.

From:

 folders: - map: ~/Code to: /home/vagrant/Code type: "nfs" 

To:

 folders: - map: ~/Code to: /home/vagrant/Code