(In reply to Sergio Monteiro Basto from comment #18) Now I'm going build new release on Fedora and I will check if we should include. > 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). > (and Manjaro even ships almost all kernels found on :O). > only Linux 4.16 has to be supported, but we also ship the latest LTS kernel Seems like it was an easy decision for Fedora 28 since > supporting option strings for mounting), then we might as well roll with > If the upstream solution is going to be in line with Fedora's (only

> I can see) to disable the helper from within fstab entries. A problem with this approach, however, is that there's no way (that > my hacky patch linked below, I just print a message to use `mount -cit` > (current Arch Linux workaround at ), but mount.vboxsf is more tricky. > Supporting both in VBoxServiceAutoMount seems somewhat straightforward > going to support mainline vboxsf only.) > vboxsf.mount will support both pre-4.16 and current kernels? (Or if it's > Do you know if the upstream fix for VBoxServiceAutoMount and (In reply to Evangelos Foutras from comment #76) The shared folder should be mounted to /media//sf_ if a logged in user belongs to vboxsf group On host, in the VM's log there is the following line:Ġ0:00:02.814077 SharedFolders host service: Adding host mappingĠ0:00:02.814097 Host path '/mnt/SSD02e/home/pasiasty', map name 'pasiasty', writable, automount=true, create_symlinks=false, missing=false May 10 15:10:15 localhost.localdomain VBoxService: 00:00:00.525649 automount Error: vbsvcAutoMountWorker: Could not mount shared folder 'pasiasty' to '/media/sf_pasiasty': No such device (19) In guest system log there is the following error message:

on a host configure a permanent shared folder to a Fedora 28 guest Version-Release number of selected component (if applicable): VirtualBox Guest Addition does not mount a permanent shared folder exported by the host

Fedora 23 virtualbox guest additions