You are not logged in.

#1 2016-09-25 06:53:52

zanculmarktum
Member
Registered: 2016-09-25
Posts: 10

[SOLVED] vboxsf can't be started

I have Arch Linux running inside VirtualBox. After I install virtualbox-guest-modules-arch and virtualbox-guest-utils, every time I boot, the Kernel Modules took so long (approx. 4 minutes) to boot.
I need to uncomment vboxsf manually within /usr/lib/modules-load.d/virtualbox-guest-modules-arch.conf as follows:

vboxguest
vboxsf
vboxvideo

to:

vboxguest
#vboxsf
vboxvideo

The problem solved. But when I try to:

modprobe -a vboxsf

it took so long, just like the previous issue, and then it said that the vboxsf module has timed out without even started.
It also said:

[ 2160.472495] INFO: task modprobe:628 blocked for more than 120 seconds.
[ 2160.472680]       Tainted: G           O    4.7.4-1-ARCH #1
[ 2160.472777] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

The version of virtualbox-guest-modules-arch, virtualbox-guest-utils and my VirtualBox (host) are 5.1.6.

Thanks in advance, and sorry for my bad English.

Last edited by zanculmarktum (2016-09-26 09:16:59)

Offline

#2 2016-09-25 07:01:11

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED] vboxsf can't be started

Moving to Apps and DEs...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2016-09-26 09:15:46

zanculmarktum
Member
Registered: 2016-09-25
Posts: 10

Re: [SOLVED] vboxsf can't be started

OK, solved.
VirtualBox Guest Additions can only use LTS kernel.

Offline

#4 2016-09-28 10:01:20

puntaier_gtec
Member
Registered: 2016-09-28
Posts: 1

Re: [SOLVED] vboxsf can't be started

Thanks for this important hint about LTS. In summary:

    sudo pacman -S linux-lts-headers linux-lts
    grub-mkconfig -o /boot/grub/grub.cfg
    reboot
    sudo pacman -S virtualbox-gueste-dkms virtualbox-guest-utils

Offline

Board footer

Powered by FluxBB