Hide Forgot
Description of problem: VirtualBox Guest Addition does not mount a permanent shared folder exported by the host Version-Release number of selected component (if applicable): virtualbox-guest-additions-5.2.10-1.fc28.x86_64 the host runs Fedora 27 and VirtualBox-5.2-5.2.10_122088_fedora26-1.x86_64 How reproducible: always Steps to Reproduce: 1. on a host configure a permanent shared folder to a Fedora 28 guest 2. start or reboot the guest 3. Actual results: The shared folder is not mounted. In guest system log there is the following error message: May 10 15:10:15 localhost.localdomain VBoxService[718]: 00:00:00.525649 automount Error: vbsvcAutoMountWorker: Could not mount shared folder 'pasiasty' to '/media/sf_pasiasty': No such device (19) On host, in the VM's log there is the following line: 00:00:02.814077 SharedFolders host service: Adding host mapping 00:00:02.814097 Host path '/mnt/SSD02e/home/pasiasty', map name 'pasiasty', writable, automount=true, create_symlinks=false, missing=false Expected results: The shared folder should be mounted to /media/<userid>/sf_<foldername> if a logged in user belongs to vboxsf group Additional info:
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: https://rpmfusion.org/Configuration And then do: dnf install akmod-VirtualBox And reboot, after that things should work.
Unfortunately, still does not work, however with different error message: May 10 16:16:20 localhost.localdomain kernel: 00:00:00.123637 automount vbsvcAutoMountWorker: Shared folder 'pasiasty' already is mounted! May 10 16:16:20 localhost.localdomain VBoxService[714]: 00:00:00.123637 automount vbsvcAutoMountWorker: Shared folder 'pasiasty' already is mounted! This is a bit misleading, because the shared volume is not mounted anywhere.
Created attachment 1434420 [details] system logs from booting time
*** Bug 1576585 has been marked as a duplicate of this bug. ***
(In reply to Evangelos Foutras from comment #76) > @Hans Do you know if the upstream fix for VBoxServiceAutoMount and > vboxsf.mount will support both pre-4.16 and current kernels? (Or if it's > going to support mainline vboxsf only.) > > Supporting both in VBoxServiceAutoMount seems somewhat straightforward > (current Arch Linux workaround at [1]), but mount.vboxsf is more tricky. In > my hacky patch linked below, I just print a message to use `mount -cit` > instead. A problem with this approach, however, is that there's no way (that > I can see) to disable the helper from within fstab entries. > > If the upstream solution is going to be in line with Fedora's (only > supporting option strings for mounting), then we might as well roll with > that in Arch Linux. Seems like it was an easy decision for Fedora 28 since > only Linux 4.16 has to be supported, but we also ship the latest LTS kernel > (and Manjaro even ships almost all kernels found on kernel.org :O). > > [1] https://git.archlinux.org/svntogit/community.git/tree/trunk/010-linux-4.16-mount-fixes.patch?h=packages/virtualbox @Evangelos moving your question to here, I built new vbox release (5.2.12) on RPMFUsion and I added some fixes to akmods (to not build old vboxguest) . Now I'm going build new release on Fedora and I will check if we should include 010-linux-4.16-mount-fixes.patch. Thanks for the reports .
I'm not terribly happy with 010-linux-4.16-mount-fixes.patch; mainly because it doesn't work with /etc/fstab entries. In Arch, we could remove the mount.vboxsf helper (like Fedora does) but then we'd lose support for pre-4.16 kernels. Ideally the vboxsf module shipped with VirtualBox Guest Additions would start accepting an options string like mainline vboxsf does. After that, VBoxServiceAutoMount and mount.vboxsf (if it still exists) would transparently work with either bundled or mainline vboxsf. :\
(In reply to Evangelos Foutras from comment #6) > I'm not terribly happy with 010-linux-4.16-mount-fixes.patch; mainly because > it doesn't work with /etc/fstab entries. In Arch, we could remove the > mount.vboxsf helper (like Fedora does) but then we'd lose support for > pre-4.16 kernels. > > Ideally the vboxsf module shipped with VirtualBox Guest Additions would > start accepting an options string like mainline vboxsf does. After that, > VBoxServiceAutoMount and mount.vboxsf (if it still exists) would > transparently work with either bundled or mainline vboxsf. :\ Are you aware of "our" patch ? [1] [1] https://src.fedoraproject.org/rpms/virtualbox-guest-additions/blob/master/f/0001-VBoxServiceAutoMount-Change-Linux-mount-code-to-use-.patch
(In reply to Sergio Monteiro Basto from comment #7) > Are you aware of "our" patch ? [1] > > [1] > https://src.fedoraproject.org/rpms/virtualbox-guest-additions/blob/master/f/ > 0001-VBoxServiceAutoMount-Change-Linux-mount-code-to-use-.patch I would switch to that if Arch was to support only Linux 4.16 (and later) + mainline vboxsf in guest VMs. Otherwise, it can't be used for older kernels with the vboxsf module from VirtualBox Guest Additions. Same issue as with removing mount.vboxsf basically.
(In reply to Evangelos Foutras from comment #8) > (In reply to Sergio Monteiro Basto from comment #7) > > Are you aware of "our" patch ? [1] > > > > [1] > > https://src.fedoraproject.org/rpms/virtualbox-guest-additions/blob/master/f/ > > 0001-VBoxServiceAutoMount-Change-Linux-mount-code-to-use-.patch > > I would switch to that if Arch was to support only Linux 4.16 (and later) + > mainline vboxsf in guest VMs. Otherwise, it can't be used for older kernels > with the vboxsf module from VirtualBox Guest Additions. Same issue as with > removing mount.vboxsf basically. I triple check and 0001-VBoxServiceAutoMount-Change-Linux-mount-code-to-use-.patch works on Centos 7 vm ( kernel 3.10 )
virtualbox-guest-additions-5.2.12-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-df01c86e0a
virtualbox-guest-additions-5.2.12-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-df01c86e0a
virtualbox-guest-additions-5.2.12-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
It still doesn't work for me, even after installing virtualbox-guest-additions-5.2.12-1.fc28. What am I missing here?
(In reply to Luiz Kill from comment #13) > It still doesn't work for me, even after installing > virtualbox-guest-additions-5.2.12-1.fc28. What am I missing here? yes, please read https://bugzilla.redhat.com/show_bug.cgi?id=1576585#c1
(In reply to Sergio Monteiro Basto from comment #14) > (In reply to Luiz Kill from comment #13) > > It still doesn't work for me, even after installing > > virtualbox-guest-additions-5.2.12-1.fc28. What am I missing here? (*) you are missing this link [1] , please read the way that you have to build vboxsf.ko [1] https://bugzilla.redhat.com/show_bug.cgi?id=1576585#c1
(In reply to Hans de Goede from comment #1) > 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: > https://rpmfusion.org/Configuration > > And then do: > > dnf install akmod-VirtualBox > > And reboot, after that things should work. Thank you very much - installing akmod-VirtualBox works perfect for me :-D