Mount vboxsf mounting failed with the error no such device vboxsf

You’re using share folders, so you need to install VirtualBox Guest Additions inside your virtual machine to support that feature.

Vagrant

If you’re using Vagrant (OS X: brew cask install vagrant), run:

vagrant plugin install vagrant-vbguest
vagrant vbguest

In case it fails, check the logs, e.g.

vagrant ssh -c "cat /var/log/vboxadd-install.log"

Maybe you’re just missing the kernel header files.

VM

Inside VM, you should install Guest Additions, kernel headers and start the service and double check if kernel extension is running.

This depends on the guest operating system, so here are brief steps:

1. Install kernel include headers (required by VBoxLinuxAdditions).

   • RHEL: sudo apt-get update && sudo apt-get install kernel-devel
   • CentOS: sudo yum update && sudo yum -y install kernel-headers kernel-devel

2. Install Guest Additions (this depends on the operating system).

   • Ubuntu: sudo apt-get -y install dkms build-essential linux-headers-$(uname -r) virtualbox-guest-additions-iso

     If you can’t find it, check by aptitude search virtualbox.

   • Debian: sudo apt-get -y install build-essential module-assistant virtualbox-ose-guest-utils

     If you can’t find it, check by dpkg -l | grep virtualbox.

   • manually by downloading the iso file inside VM (e.g. wget) and installing it, e.g.

     1. wget http://download.virtualbox.org/virtualbox/5.0.16/VBoxGuestAdditions_5.0.16.iso -P /tmp
     2. sudo mount -o loop /tmp/VBoxGuestAdditions_5.0.16.iso /mnt

     3. sudo sh -x /mnt/VBoxLinuxAdditions.run # --keep

        Extra debug: cd ~/install && sh -x ./install.sh /mnt/VBoxLinuxAdditions.run

3. Double check that kernel extensions are up and running:

   • sudo modprobe vboxsf

4. Start/restart the service:

   • manually: sudo /opt/VBoxGuestAdditions*/init/vboxadd setup (add sudo sh -x to debug)
   • Debian: sudo /etc/init.d/vboxadd-service start
   • Fedora: sudo /etc/init.d/vboxdrv setup
   • CentOS: sudo service VBoxService start

Building the main Guest Additions module

If above didn’t work, here are more sophisticated steps to fix it. This assumes that you’ve already VBoxGuestAdditions installed (as shown above).

The most common reason why mounting shared folder doesn’t work may related to building Guest Additions module which failed. If in /var/log/vboxadd-install.log you’ve the following error:

The headers for the current running kernel were not found.

this means either you didn’t install kernel sources, or they cannot be found.

If you installed them already as instructed above, run this command:

$ sudo sh -x /opt/VBoxGuestAdditions-5.0.16/init/vboxadd setup 2>&1 | grep KERN
+ KERN_VER=2.6.32-573.18.1.el6.x86_64
+ KERN_DIR=/lib/modules/2.6.32-573.18.1.el6.x86_64/build

So basically vboxadd script is expecting your kernel sources to be available at the following dir:

ls -la /lib/modules/$(uname -r)/build

Check if the kernel dir exists (symbolic link points to the existing folder). If it’s not, please install them to the right folder (e.g. in /usr/src/kernels).

So vboxadd script can enter your kernel source directory and run make kernelrelease, get the value and compare with your current kernel version.

Here is the logic:

KERN_VER=`uname -r`
KERN_DIR="/lib/modules/$KERN_VER/build"
if [ -d "$KERN_DIR" ]; then
    KERN_REL=`make -sC $KERN_DIR --no-print-directory kernelrelease 2>/dev/null || true`
    if [ -z "$KERN_REL" -o "x$KERN_REL" = "x$KERN_VER" ]; then
        return 0
    fi
fi

If the kernel version doesn’t match with the sources, maybe you’ve to upgrade your Linux kernel (in case the sources are newer than your kernel).

CentOS

Try:

vagrant plugin install vagrant-vbguest vagrant vbgues

If won’t work, try the following manual steps for CentOS:

$ sudo yum update
$ sudo yum install kernel-$(uname -r) kernel-devel kernel-headers # or: reinstall
$ rpm -qf /lib/modules/$(uname -r)/build
kernel-2.6.32-573.18.1.el6.x86_64
$ ls -la /lib/modules/$(uname -r)/build
$ sudo reboot # and re-login
$ sudo ln -sv /usr/src/kernels/$(uname -r) /lib/modules/$(uname -r)/build
$ sudo /opt/VBoxGuestAdditions-*/init/vboxadd setup

Getting /sbin/mount.vboxsf: mounting failed with the error: No such device #4

Hi
Getting the following error. Please would you recommend a path to resolution? Thank you

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:

stdin: is not a tty
/sbin/mount.vboxsf: mounting failed with the error: No such device

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

ran into a similar issue myself.

If you haven’t already, you may need to rebuild the VirtualBox guest additions:

Works first time, but fails afterwards. Specially if you need this to work before shell script.

Went for a plugin:
vagrant vbguest plugin

This may be related to the missing kernel sources in your VM.

So try to install Guest Additions and check the log file for details, e.g. follow these steps and it VBoxLinuxAdditions fails, then check the /var/log/vboxadd-install.log for more details.

Like @esteban-xrow said, just install Vagrant plugin: vagrant-vbguest, which can keep your VirtualBox Guest Additions up to date.

@kiwenlau YES thank you that worked! vagrant plugin install vagrant-vbguest

I was able to resolve this on bento/centos-7.2 by performing the following:

yum update
yum install kernel-headers kernel-devel

Then reboot the vagrant, and run the following
sudo /opt/VBoxGuestAdditions-*/init/vboxadd setup

So I was fighting with this same issue for quite a while. rcvboxadd was complaining that I did not have kernel-headers installed. I am on CentOS 7 with kernel 3.10.0-957.21.2.el7.x86_64 and with just doing a yum install kernel-headers it was installing the latest of 3.10.0-957.21.3.el7.x86_64 which is a little newer and not matching my current kernel. So I erased the headers with yum and explicitly installed the version that matched my kernel. I also had to reinstall gcc. I then installed my specific kernel version of kernel-devel . With these now matching my kernel version, I then ran /usr/sbin/rcvboxadd setup and it finally built everything correctly and started the service up. After that I mounted my HOST folder to my Linux GUEST with: sudo mount -t vboxsf -o rw,uid=1000,gid=1000 REPOS

REPO is the name of the share in the properties of my VM in the Shared Folders section.

I hope this helps someone else out — I could’ve probably just updated my kernel to the already installed version of kernel-headers and kernel-devel — but either way, this small victory is a great way to finish off a Friday.

Источник

virtualbox.org

End user forums for VirtualBox

• Board index‹Guest systems‹Linux Guests
• Change font size
• Print view

• FAQ
• Login

Shared folder won’t mount

by ianbasore » 19. Apr 2008, 23:58

Okay, I’m new here and I need some help.
I’ve never used linux before now, so bear with me.

I’m running VirtualBox 1.5.6 on a host system of Windows XP SP2.
In a virtual machine (through which I am typing now) I’m running Ubuntu 7.10.

Now, everything’s been going well so far, except I can’t get the shared folder to mount in Ubuntu.

I type the command «sudo mount -t vboxsf shared /home/ian/shared»

and I get this error: «/sbin/mount.vboxsf: mounting failed with the error: No such file or directory»

I don’t know what I’m doing wrong.
I’ve created the shared folder in Ubuntu in «shared» simply enough.
I’ve also used the Shared Folders utility in VirtualBox to create a folder called «shared» and all that.

I could use some help. please?
I think i’m just missing some step or some command.

by TiX » 20. Apr 2008, 12:54

Did you try to share a complete hard disk drive C: or D: ?
It it is the case you can forget it, there is a bug in VirtualBox 1.5.6.

You can either only share a subfolder or use VirtualBox 1.5.4.

Have a nice day.

by ianbasore » 20. Apr 2008, 19:43

by n6yga » 14. May 2008, 22:46

I am having the same stupid problem. Maybe I am just stupid today, I don’t know. But, the command:
mount.vboxsf XDrive /media/share WILL NOT WORK. I have spent the last four hours trying to get this to work.

Debian lenny. Vbox 1.5.6 on an Ubuntu 7.10 host.

by davmk » 15. May 2008, 01:43

Do you have installed guest additions? Because this commands works on my box.

Please note the destination folder must exists.

by ianbasore » 15. May 2008, 02:44

by tonne » 15. May 2008, 19:02

Ubuntu 8.04 on Vista Home Premium 64 bit.
Added a shared folder in vb:
Path t:temp
Name temp

In Ubuntu as root (sudo -s)
mount -tvboxsf temp /mnt

If mounting to /media/share make sure the folder exist.

by n6yga » 15. May 2008, 19:57

With guest additions installed, and a share created in VB, I get the «device not found» error everytime I try to mount a share.

Ubuntu 7.10. VB version 1.5.6

Guest is a daily build of Lenny, kernel 2.6.24-1. Guest additions installed against the kernel fine. No errors.

created a share /home/n6yga/VirtualDrive, name test.

as root, I enter mount.vboxsf test /media/share. The share folder does exist.

I get the «device not found» error ever time. No matter how I form the command.

I must be doing something really stupid cause I can’t see the error.

Also, mount -t vboxsf test /media/share errors out the same way.

by n6yga » 15. May 2008, 20:00

tonne wrote: Ubuntu 8.04 on Vista Home Premium 64 bit.
Added a shared folder in vb:
Path t:temp
Name temp

In Ubuntu as root (sudo -s)
mount -tvboxsf temp /mnt

If mounting to /media/share make sure the folder exist.

Just tried your exact command and got the same error: «no such device»

Any other ideas?
M.

by nico » 21. May 2008, 19:11

I just had the same problem, and I found a solution !

This worked for me, under Debian:

install Guest Additions

Code: Select all Expand viewCollapse view sudo modprobe vboxvfs Code: Select all Expand viewCollapse view sudo mount -t vboxsf shared /mnt/vbshared

then, it worked like a charm

by n6yga » 21. May 2008, 19:29

Nice work! I will give it a try and report back. How did you ever think to modprobe it? Wow!

by n6yga » 21. May 2008, 20:01

Ok, here’s the way it worked for me:

1. as root, install the virtualbox guest additons.
2. reboot the guest system (in this case a lenny install)
3. modprobe vboxvfs (reports nothing so all is well)
4. mount.vboxsf VirtualDrive /media/shared

Using the virtualbox command was the only way it would work for me. My version of vitualbox is 1.5.6

Obviously, VirtualDrive is a folder on the HOST system, in the /home/ directory.

I sincerely hope that this will help some other poor shlub who is guesting linux repos on a linux host.

Mark.
P.S. THANK YOU NICO. I don’t know why the new virtualbox kernel module doesn’t load after a reboot, but this works so I’ll move on.

by n6yga » 21. May 2008, 20:47

A smaller new problem:

Adding vboxvfs to /etc/modules should start that module at boot time. Unfortunately it does not.

I’ll keep at it and report back.

by lot » 22. May 2008, 20:00

n6yga wrote: A smaller new problem:

Adding vboxvfs to /etc/modules should start that module at boot time. Unfortunately it does not.

I’ll keep at it and report back.

I’m guessing you’re problem would be solved (in a cleaner way) by the solution I gave there: http://forums.virtualbox.org/viewtopic.php?t=6139

Doesn’t work for me

by stanley » 22. May 2008, 20:00

What does it mean when I do modprobe vboxvfs and it tells me FATAL ERROR module not found.

What’s supposed to put it wherever it’s supposed to be. I have run LinuxAdditions and it completed OK.

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

• Темы без ответов
• Активные темы
• Поиск
• Статус форума

VirtualBox и общие папки (не видит)

VirtualBox и общие папки

Сообщение Олександр » 29.02.2008 02:43

Re: VirtualBox и общие папки

Сообщение -sanches- » 29.02.2008 12:33

Re: VirtualBox и общие папки

Сообщение Олександр » 05.03.2008 12:30

Re: VirtualBox и общие папки

Сообщение landgraf » 05.03.2008 13:44

Re: VirtualBox и общие папки

Сообщение NIS » 06.03.2008 00:12

Re: VirtualBox и общие папки

Сообщение Олег777 » 08.03.2008 12:28

Re: VirtualBox и общие папки

Сообщение Олександр » 09.03.2008 20:07

А вот у меня как раз этого самого VirtualBox и не видно

Re: VirtualBox и общие папки

Сообщение landgraf » 09.03.2008 22:07

Re: VirtualBox и общие папки

Сообщение Олександр » 10.03.2008 23:24

Re: VirtualBox и общие папки

Сообщение Flaming » 06.10.2008 14:23

Re: VirtualBox и общие папки

Сообщение minder » 07.10.2008 11:00

Re: VirtualBox и общие папки

Сообщение Sabivan » 21.12.2008 13:05

основная система — XP, гостевая система — kubuntu 8.10

Использую версию 2.0.4 — но проблема та же.
Guest Additions установлены. Как справиться с неподключающейся флешкой в руководстве Virtualbox написано, а вот как бороться с No such device — увы нет

Re: VirtualBox и общие папки

Сообщение Flaming » 21.12.2008 13:12

Re: VirtualBox и общие папки

Сообщение Sabivan » 29.12.2008 16:06

Re: VirtualBox и общие папки

Сообщение Flaming » 29.12.2008 18:40

Re: VirtualBox и общие папки

Сообщение Sabivan » 30.12.2008 10:48

не,ну без ложки дёгтя просто никак не обойтись
обновить c 2.0.4 до 2.0.6 попробую, но сомневаюсь что это что-то даст.

Re: VirtualBox и общие папки

Сообщение grechan » 14.01.2009 16:51

Re: VirtualBox и общие папки

Сообщение SLEDopit » 14.01.2009 17:27

Re: VirtualBox и общие папки

Сообщение grechan » 14.01.2009 17:52

Re: VirtualBox и общие папки

Сообщение SLEDopit » 14.01.2009 17:59

Re: VirtualBox и общие папки

Сообщение basolov » 17.01.2009 18:30

Re: VirtualBox и общие папки

Сообщение durc » 17.01.2009 18:45

Re: VirtualBox и общие папки

Сообщение basolov » 17.01.2009 19:33

Re: VirtualBox и общие папки

Сообщение Ivan08 » 27.01.2010 10:53

У меня после этой команды вылазит вот такое:
/sbin/mount.vboxsf: mounting failed with the error: No such device

Что делать подскажите.

Re: VirtualBox и общие папки

Сообщение Vardo » 28.01.2010 06:51

я так понимаю проблема в правильной настройке сетевого интерфейса, тоже долго мучался получилось сделать так
1) Меню — Устройства — Сетевые адаптеры
2) Выбираем плату которая будет связующим звеном между компом и виртуалкой
3) Тип подключения: Сетевой мост
4) Имя: (если вдруг их несколько и одна смотрит в инет)
5) Ставим галочку «Кабель подключен»
6) Жмем ОК
7) Меню — Устройства — Общие папки
Добавляем новую папку

у меня в виртуалке винда поэтому я цепляюсь к компу так
На виртуалке идем в: Сетевое окружение — Отобразить компьютеры рабочей группы (сетевые задачи) — Microsoft Windows Network (другие места) — Вся сеть (другие места) — VirtualBox Shared Folders собственно там указанные папки

Re: VirtualBox и общие папки

Сообщение dedok2010 » 13.03.2010 18:45

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

• Темы без ответов
• Активные темы
• Поиск
• Статус форума

VirtualBox и общие папки (не видит)

VirtualBox и общие папки

Сообщение Олександр » 29.02.2008 02:43

Re: VirtualBox и общие папки

Сообщение -sanches- » 29.02.2008 12:33

Re: VirtualBox и общие папки

Сообщение Олександр » 05.03.2008 12:30

Re: VirtualBox и общие папки

Сообщение landgraf » 05.03.2008 13:44

Re: VirtualBox и общие папки

Сообщение NIS » 06.03.2008 00:12

Re: VirtualBox и общие папки

Сообщение Олег777 » 08.03.2008 12:28

Re: VirtualBox и общие папки

Сообщение Олександр » 09.03.2008 20:07

А вот у меня как раз этого самого VirtualBox и не видно

Re: VirtualBox и общие папки

Сообщение landgraf » 09.03.2008 22:07

Re: VirtualBox и общие папки

Сообщение Олександр » 10.03.2008 23:24

Re: VirtualBox и общие папки

Сообщение Flaming » 06.10.2008 14:23

Re: VirtualBox и общие папки

Сообщение minder » 07.10.2008 11:00

Re: VirtualBox и общие папки

Сообщение Sabivan » 21.12.2008 13:05

основная система — XP, гостевая система — kubuntu 8.10

Использую версию 2.0.4 — но проблема та же.
Guest Additions установлены. Как справиться с неподключающейся флешкой в руководстве Virtualbox написано, а вот как бороться с No such device — увы нет

Re: VirtualBox и общие папки

Сообщение Flaming » 21.12.2008 13:12

Re: VirtualBox и общие папки

Сообщение Sabivan » 29.12.2008 16:06

Re: VirtualBox и общие папки

Сообщение Flaming » 29.12.2008 18:40

Re: VirtualBox и общие папки

Сообщение Sabivan » 30.12.2008 10:48

не,ну без ложки дёгтя просто никак не обойтись
обновить c 2.0.4 до 2.0.6 попробую, но сомневаюсь что это что-то даст.

Re: VirtualBox и общие папки

Сообщение grechan » 14.01.2009 16:51

Re: VirtualBox и общие папки

Сообщение SLEDopit » 14.01.2009 17:27

Re: VirtualBox и общие папки

Сообщение grechan » 14.01.2009 17:52

Re: VirtualBox и общие папки

Сообщение SLEDopit » 14.01.2009 17:59

Re: VirtualBox и общие папки

Сообщение basolov » 17.01.2009 18:30

Re: VirtualBox и общие папки

Сообщение durc » 17.01.2009 18:45

Re: VirtualBox и общие папки

Сообщение basolov » 17.01.2009 19:33

Re: VirtualBox и общие папки

Сообщение Ivan08 » 27.01.2010 10:53

У меня после этой команды вылазит вот такое:
/sbin/mount.vboxsf: mounting failed with the error: No such device

Что делать подскажите.

Re: VirtualBox и общие папки

Сообщение Vardo » 28.01.2010 06:51

я так понимаю проблема в правильной настройке сетевого интерфейса, тоже долго мучался получилось сделать так
1) Меню — Устройства — Сетевые адаптеры
2) Выбираем плату которая будет связующим звеном между компом и виртуалкой
3) Тип подключения: Сетевой мост
4) Имя: (если вдруг их несколько и одна смотрит в инет)
5) Ставим галочку «Кабель подключен»
6) Жмем ОК
7) Меню — Устройства — Общие папки
Добавляем новую папку

у меня в виртуалке винда поэтому я цепляюсь к компу так
На виртуалке идем в: Сетевое окружение — Отобразить компьютеры рабочей группы (сетевые задачи) — Microsoft Windows Network (другие места) — Вся сеть (другие места) — VirtualBox Shared Folders собственно там указанные папки

Re: VirtualBox и общие папки

Сообщение dedok2010 » 13.03.2010 18:45

Источник

Vagrant version

Vagrant 1.9.1

c:wwwhtdocsvagrant>vagrant plugin list
vagrant-share (1.1.6, system)
vagrant-vbguest (0.13.0)

Host operating system

Win10

Guest operating system

VirtualBox 5.0.24 r108355

CentOS Linux release 7.3.1611 (Core)(after run yum update)
Kernel 3.10.0-514.6.2.el7.x86_64

Vagrantfile

Vagrant.configure(2) do |config|
  config.vm.box = "CentOS-7-Vagrant-1505-x86_64-01"

  config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
   config.vm.network "private_network", ip: "192.168.33.10"

  config.vm.synced_folder ".", "/home/vagrant/sync", type: "virtualbox"

    config.vm.provision "shell", inline: <<-SHELL
  SHELL
end

Actual behavior

c:wwwhtdocsvagrant>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> 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 (guest) => 8080 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> 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: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
[default] GuestAdditions versions on your host (5.0.24) and guest (4.2.10) do not match.
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.ustc.edu.cn
 * extras: centos.ustc.edu.cn
 * updates: centos.ustc.edu.cn
Package kernel-devel-3.10.0-514.6.2.el7.x86_64 already installed and latest version
Package gcc-4.8.5-11.el7.x86_64 already installed and latest version
Package binutils-2.25.1-22.base.el7.x86_64 already installed and latest version
Package 1:make-3.82-23.el7.x86_64 already installed and latest version
Package 4:perl-5.16.3-291.el7.x86_64 already installed and latest version
Package bzip2-1.0.6-13.el7.x86_64 already installed and latest version
Nothing to do
Copy iso file C:Program FilesOracleVirtualBox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
mount: /dev/loop0 is write-protected, mounting read-only
Installing Virtualbox Guest Additions 4.2.10 - guest version is 4.2.10
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.2.10 Guest Additions for Linux..........
VirtualBox Guest Additions installer
Removing installed version 4.2.10 of VirtualBox Guest Additions...
                                                     Removing existing VirtualBox non-DKMS kernel modules[  OK  ]
Building the VirtualBox Guest Additions kernel modules
Building the main Guest Additions module[  OK  ]
Building the shared folder support module[FAILED]
(Look at /var/log/vboxadd-install.log to find out what went wrong)
Doing non-kernel setup of the Guest Additions[  OK  ]
Installing the Window System drivers[FAILED]
(Could not find the X.Org or XFree86 Window System.)

==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.2.10
    default: VirtualBox Version: 5.0
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /home/vagrant/sync => C:/www/htdocs/vagrant
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 home_vagrant_sync /home/vagrant/sync

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

Network question, I got this output in the machine image

[root@localhost ~]# service network restart
Restarting network (via systemctl):  Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
                                                           [FAILED]
[root@localhost ~]# systemctl status network.service
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2017-02-25 00:25:03 EST; 1min 20s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 16813 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Feb 25 00:25:03 nodename.domainname network[16813]: [  OK  ]
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
Feb 25 00:25:03 nodename.domainname network[16813]: RTNETLINK answers: File exists
[root@localhost ~]# ifconfig -a
eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:73:0f:b1  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.33.10  netmask 255.255.255.0  broadcast 192.168.33.255
        inet6 fe80::a00:27ff:fe34:7557  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:34:75:57  txqueuelen 1000  (Ethernet)
        RX packets 2063  bytes 724832 (707.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1089  bytes 278076 (271.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

install VBoxGuestAdditions_5.0.2

[root@localhost vagrant]# sudo mount -o loop,ro VBoxGuestAdditions_5.0.2.iso /media/VBoxGuestAdditions
[root@localhost vagrant]# sudo sh /media/VBoxGuestAdditions/VBoxLinuxAdditions.run rm VBoxGuestAdditions_5.0.2.iso
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.0.2 Guest Additions for Linux............
VirtualBox Guest Additions installer
Please specify an absolute path

Usage: /media/VBoxGuestAdditions/VBoxLinuxAdditions.run install [<installation directory>]
       [--with-<module>] |
       uninstall
       [--force] [--no-setup]

Example:
/media/VBoxGuestAdditions/VBoxLinuxAdditions.run install
[root@localhost vagrant]# sudo umount /media/VBoxGuestAdditions
[root@localhost vagrant]# sudo rmdir /media/VBoxGuestAdditions
[root@localhost vagrant]# sudo /etc/init.d/vboxadd setup
Removing existing VirtualBox non-DKMS kernel modules       [  OK  ]
Building the VirtualBox Guest Additions kernel modules
Building the main Guest Additions module                   [  OK  ]
Building the shared folder support module                  [FAILED]
(Look at /var/log/vboxadd-install.log to find out what went wrong)
Doing non-kernel setup of the Guest Additions              [  OK  ]
[root@localhost vagrant]# vi /var/log/vboxadd-install.log