Page 1 of 2

Shared folder problems

Posted: 26. May 2019, 16:19
by Larvae
Hi

I recently installed VirtualBox 6.0.8 (including the extension pack) on my Win10 and made a new VM running Ubuntu 19.04. I installed the GuerstAdditions and made a shared folder. I could only access the folder as root, and inside I could only create new files, but not open or delete anything. So I added myself to vboxsf. It didnt't change anything. I also tried changing the owner, which didn't work either.

Then I tried mounting the shared folder manually, but I always get

Code: Select all

/sbin/mount.vboxsf: mounting failed with the error: No such device
I googled how to solve that, but nothing I found worked.

So, for now, I set the folders to auto-mount again. But now the folders are still locked, but when I open them as root they are just empty.

Now I don't know what to do next to get this to work.

Any advice?

Re: Shared folder problems

Posted: 27. May 2019, 02:49
by Raspero
You need to be a member of vboxusers as well.

Richard

Re: Shared folder problems

Posted: 27. May 2019, 11:01
by Larvae
I have never seen that group before. On my old pc I never had to do that.

Anyway, since it didn't exist I created it, with me as a member, but it didn't help. I still need my root pw to get into the folders, which are still empty.

edit: Of cource I logged out/in again.

Re: Shared folder problems

Posted: 28. May 2019, 04:28
by socratis
Raspero wrote:You need to be a member of vboxusers as well.
No, you don't. That group only exists if you're running VirtualBox on a Linux host, not if you're running a Linux guest.
Larvae wrote:I have never seen that group before
That's because you're on a Windows host, not a Linux host. See above.

I need to see the output of the "id" command in the guest.

Re: Shared folder problems (vboxsf)

Posted: 28. May 2019, 11:28
by ksomov
== Enviroment
Host: MS Windows 10 x86_64
Guest: SuSE Linux 12SP3 x86_64
VBox: Version 6.0.8 r130520 (Qt5.6.2)
== Problem: Error mount of shared folders:
ROUTER01:~ # cat /etc/SuSE-release 
SUSE Linux Enterprise Server 12 (x86_64)
VERSION = 12
PATCHLEVEL = 3
# This file is deprecated and will be removed in a future service pack or release.
# Please check /etc/os-release for details about this release.
ROUTER01:~ # uname -a              
Linux ROUTER01 4.4.92-6.18-default #1 SMP Fri Oct 20 18:58:48 UTC 2017 (a69df70) x86_64 x86_64 x86_64 GNU/Linux
ROUTER01:~ #
ROUTER01:~ # mount -t vboxsf BACKUP /mnt/backup
/sbin/mount.vboxsf: mounting failed with the error: No such device
ROUTER01:~ # ls -l /sbin/mount.vboxsf
lrwxrwxrwx 1 root root 48 May 28 11:49 /sbin/mount.vboxsf -> /opt/VBoxGuestAdditions-6.0.8/other/mount.vboxsf
ROUTER01:~ # ls -l /opt/VBoxGuestAdditions-6.0.8/other/mount.vboxsf
-rwxr-xr-x 1 root root 19152 May 13 16:50 /opt/VBoxGuestAdditions-6.0.8/other/mount.vboxsf
== During Installation VBoxLinuxAdditions v.6.0.8 in log /var/log/vboxadd-setup.1.log - (last 12 string) error:
/tmp/vbox.0/regops.c:3780:5: warning: (near initialization for ‘vbsf_reg_aops.direct_IO’) [enabled by default]
/usr/src/linux-4.4.92-6.18/scripts/Makefile.build:259: recipe for target '/tmp/vbox.0/regops.o' failed
make[4]: *** [/tmp/vbox.0/regops.o] Error 1
/usr/src/linux-4.4.92-6.18/Makefile:1431: recipe for target '_module_/tmp/vbox.0' failed
make[3]: *** [_module_/tmp/vbox.0] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[2]: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make[1]: *** [__sub-make] Error 2
/tmp/vbox.0/Makefile-footer.gmk:111: recipe for target 'vboxsf' failed
make: *** [vboxsf] Error 2
Could not find the X.Org or XFree86 Window System, skipping.
Full Logs see in attachment.
It is observed in versions 6.0.6 & 6.0.8
Somebody knows as to win against it?

Re: Shared folder problems

Posted: 28. May 2019, 11:43
by socratis
Try the latest test build. The whole package, not just the GAs. Also, what is this?
ksomov wrote:Could not find the X.Org or XFree86 Window System, skipping.
Are you running a CLI version, no X Windows?

Re: Shared folder problems (vboxsf)

Posted: 28. May 2019, 12:07
by ksomov
Yes, I use CLI version. Tell what means [... not just the GAs.]?

Re: Shared folder problems

Posted: 28. May 2019, 12:09
by socratis
ksomov wrote:Yes, I use CLI version.
Then you need to run "VBoxLinuxAdditions.run --nox11".
ksomov wrote:Tell what means [... not just the GAs.]?
In the Test Build page that I linked, there is the full package (Windows) and there are the standalone Guest Additions. Go for the full package.

Re: Shared folder problems (vboxsf)

Posted: 28. May 2019, 12:37
by ksomov
Something terrible happened... after installation of the test VirtualBox 6.0.9 version...
At start of any guest vm given now is the message is, see screenshot 2019-05-28_13-26-36.png.
The status of service (sc.exe query vboxdrv) - see screenshot 2019-05-28_13-32-04.png.
The full log of start of the virtual mashine see in file VBoxHardening.log.
Reset Host does not help.
Reason: The vboxdrv driver is not signed for Windows.

Re: Shared folder problems (vboxsf)

Posted: 28. May 2019, 13:22
by ksomov
Total:
== It is too much problems with VirtualBox version 6.0.*.
== Therefore VirtualBox 6.0.9 is removed and cleaned.
== The latest version VirtualBox 5.2.30 is installed.
== These problems are not here yet, i.e. there are no problems with the shared folders.

Re: Shared folder problems

Posted: 28. May 2019, 16:06
by socratis
ksomov wrote:Reason: The vboxdrv driver is not signed for Windows.
You need to start paying closer attention to what's written, the notes. Otherwise, you're going to go with the wrong conclusion, just like you did.

From the test builds page, paragraph "Installing Windows test builds":
The Windows test build packages are working precisely like a usual VirtualBox installer packages, with one difference: they will not work (the error message will point to unsigned drivers) if you install them on Windows 10 if your system has UEFI secure boot enabled. To make these test build work you need to disable UEFI secure boot in the system's UEFI config.
See? No mystery here...

So Total:
== I don't want to deal with it, going back.

Re: Shared folder problems

Posted: 28. May 2019, 16:14
by Larvae
Hi,

I don't know, what ksomov is talking about, but when I use "id" in the guest I get

Code: Select all

thorsten@thorsten-VirtualBox:~$ id
uid=1000(thorsten) gid=1000(thorsten) Gruppen=1000(thorsten),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),118(lpadmin),129(sambashare),999(systemd-coredump)

Re: Shared folder problems

Posted: 28. May 2019, 16:19
by socratis
@Larvae
You're not part of the 'vboxsf' group (VirtualBox Shared Folders). You need to add yourself to that group and reboot the guest.

Re: Shared folder problems

Posted: 28. May 2019, 16:34
by Larvae
I am a member, at least according to /etc/group:

Code: Select all

thorsten:x:1000:
sambashare:x:129:thorsten
systemd-coredump:x:999:
vboxsf:x:999:thorsten
vboxusers:999:thorsten
rdma:x:130:
I also added myself via terminal an rebooted. Or am I reading the file wrong?

Re: Shared folder problems

Posted: 28. May 2019, 16:52
by socratis
From the manual, ch. 4.3.2 Automatic Mounting:
Access to an automatically mounted shared folder is granted to everyone in a Windows guest, including the guest user. For Linux and Oracle Solaris guests, access is restricted to members of the group vboxsf and the root user.
And as "id" showed, you're not a member of the 'vboxsf' group. Did you reboot the guest after adding yourself to the group?