Description of problem:
Host system: 64-bit Mageia 6 Plasma, using 64-bit VirtualBox 5.2.22 as installed from the Mageia 6 repositories, with the 5.2.22 extension pack installed.
Guest system: Mageia 7 Plasma system, as installed from the test Round 1 of the Beta 2 LiveDVD iso.
The guest system is not auto-mounting shared folders from the host, or if it is I can't find them.
The guest user is part of the vboxsf group, and the host user belongs to the vboxusers group. Shared folders do work in other guests, including Mageia 6 and Windows XP.
virtualbox-guest-additions was installed by the iso. dkms-vboxadditions was not.
I first saw this after an install from the beta 1 iso, but attributed it to /media, where shared folders are typically mounted, not being created. That has been corrected in the beta 2 isos.
Assigning to tmb.
I believe this is the same as:
Summary: Timing of the nfs mount not working?
We've seen this before in previous releases.
Tested in 7beta3 - still now working properly. I see the following message:
Feb 18 12:11:55 localhost VBoxService: 18:11:55.281434 automount vbsvcAutoMountWorker: Shared folder 'vmshared' already is mounted!
I go out to /media/vmshared on the VM and it is empty.
The hosted folder has quite a few files in it. This isn't resolved.
What's the output of:
(In reply to Kristoffer Grundström from comment #4)
> What's the output of:
> groups $USER
In the host, or the guest? Or both?
On VM guest:
$ groups $USER
brian : brian vboxsf
This works fine on the same host and MGA6.
Problem confirmed. M6 x86_64 host, M7 x86_64 guest.
Host has Oracle_VM_VirtualBox_Extension_Pack-5.2.24.vbox-extpack installed.
In guest, user is member of vboxsf group (logged out/in after adding).
Comparing the journal on an m6 guest where it's working, to the m7 guest
where it isn't, m7 has the following error message ...
kernel: vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.
As per https://forums.virtualbox.org/viewtopic.php?f=3&t=89187,
I also tried following the instruction in the error message with
# mv /sbin/mount.vboxsf /root
and rebooting. No change.
I noticed that on m6 VBoxService is running, but not on m7. On m7 I ran
# VBoxService -l VBoxService.log
# tail -n 3 VBoxService.log
21:10:03.575104 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Not supported (#3)
21:10:03.587668 automount vbsvcAutoMountWorker: Shared folder 'ROOT' already is mounted!
21:10:03.588564 automount vbsvcAutoMountWorker: Shared folder 'dave' already is mounted!
Searching on the not supported message, I think it may be this patch ...
Not sure where they got it from as I can't find it on virtualbox.org
I did find https://github.com/torvic9/virtualbox/blob/master/012-vbglR3GuestCtrlDetectPeekGetCancelSupport.patch
has the same patch
See also https://ml.mageia.org/l/arc/qa-discuss/2019-01/msg00065.html. Removing the obsolete /sbin/mount.vboxsf lets you manually mount a shared filesystem. VBoxService needs to be updated to fix auto-mounting.
Problem also exists with a Mageia 7 host, VirtualBox 6.0.4. Even fully updated, as of today, Mageia 7 guests do not automount any shared folders.
Shared folders ARE automounted in Mageia 6 guests.