Description of problem:
unable to mount shared folders in guest
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. do NOT install guest additions from VirtualBox's ISO (i.e. "Insert Guest additions CD image" in the "Devices" menu)
2. share a folder
3. try to mount that folder inside the guest: mount -t vboxsf SHAREDFOLDER /mnt
error: vboxsf wrong fs type, bad option, bad superblock on support, missing codepage or helper program, or other error.
shared folder mounted on /mnt
mount.vboxsf is no longer necessary, the latest version of the vboxsf kernel module works with the standard mount utility.
The problem is that the Fedora 28 kernel includes the vboxvideo and vboxguest drivers as those are part of the mainline kernel now. But the vboxsf driver has not been merged into the mainline kernel yet (this is being worked on).
A version of vboxsf compatible with the mainline kernel version of vboxguest is available in rpmfusion, follow the instructions for enabling rpmfusion-free here:
And then do:
dnf install akmod-VirtualBox
After that: "mount -t vboxsf SHAREDFOLDER /mnt" should work.
(In reply to Hans de Goede from comment #1)
> mount.vboxsf is no longer necessary, the latest version of the vboxsf kernel
> module works with the standard mount utility.
> The problem is that the Fedora 28 kernel includes the vboxvideo and
> vboxguest drivers as those are part of the mainline kernel now. But the
> vboxsf driver has not been merged into the mainline kernel yet (this is
> being worked on).
This implies to me that, at least for Fedora 28, mount.vboxsf is still
necessary. As it stands, Fedora 28 doesn't support mounting VirtualBox shared
folders despite appearing to provide first-party support for acting as a VBox
guest. While installing the kernel module from RPM Fusion is an option, it
shouldn't be necessary. IMO, mount.vboxsf shouldn't be removed from Fedora
until the kernel driver ships inside a Fedora kernel.
to mount.vboxsf work you also need vboxsf.ko kernel module
*** This bug has been marked as a duplicate of bug 1576832 ***