VB 5.2.4 Guest Additions error: shared folder ownership

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Mandu
Posts: 10
Joined: 22. Sep 2012, 19:25

VB 5.2.4 Guest Additions error: shared folder ownership

Post by Mandu »

I tried running the Guest Additions for Linux (Mint 18.3) and received the following error about modprobe vboxsf.
$ sudo sh ./VBoxLinuxAdditions.run
[sudo] password for chap:
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.4 Guest Additions for Linux........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted
VirtualBox Guest Additions: Starting.

==> VirtualBox Guest Additions: modprobe vboxsf failed

You may need to restart the Window System (or just restart the guest system)
to enable the Guest Additions.
After restarting, the GAs appear to be mostly working (shared clipboard, better display management) but my shared folders, although successfully mounted in /media, have ownerships that exclude me:

Code: Select all

drwxr-x---+ 2 charrison charrison   4096 Jan  3 14:58 chap/
drwxr-x---+ 3 root      root        4096 Jan  3 18:11 charrison/
drwxrwx---  1 root      vboxsf    163840 Jan  3 13:59 sf_L_DRIVE/
drwxrwx---  1 root      vboxsf      8192 Oct 12 08:25 sf_charrison/
I suspect this is related to the earlier error. Any thoughts?

(VBox 5.2.4 running on Windows 7.)
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VB 5.2.4 Guest Additions error: shared folder ownership

Post by Perryg »

If you are using the auto-mount feature you need your guests user in the guests vboxsf group followed with a reboot of the guest.
Mandu
Posts: 10
Joined: 22. Sep 2012, 19:25

Re: VB 5.2.4 Guest Additions error: shared folder ownership

Post by Mandu »

Is this the way it has always been? I don't remember ever having to add myself to a group in order to have read/write access to the Windows folders (either on the local disk, or on network drives) that I specified in the VM settings under shared folders.

Nor do I recall seeing the error message "VirtualBox Guest Additions: modprobe vboxsf failed" before while installing the guest additions. In the past, this process has been completely smooth, as I recall.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VB 5.2.4 Guest Additions error: shared folder ownership

Post by Perryg »

We could go on all day about what and when but just to make it faster post the guests log file ( as an attachment ) so I can see exactly what you did.
Mandu
Posts: 10
Joined: 22. Sep 2012, 19:25

Re: VB 5.2.4 Guest Additions error: shared folder ownership

Post by Mandu »

Perryg wrote:We could go on all day about what and when but just to make it faster [Please] post the guests log file ( as an attachment ) so I can see exactly what you did.
Attached is a zipfile with two log files covering VBox creation, Mint installation, GA installation, and reboot with shared folders.
Attachments
vboxlog.tgz
Logs covering installation on forward
(52.87 KiB) Downloaded 63 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VB 5.2.4 Guest Additions error: shared folder ownership

Post by Perryg »

00:00:02.686138 Host path '/Users/chap', map name 'chap', writable, automount=true, create_symlinks=false, missing=false
VBox Users Manual wrote: Note: Access to auto-mounted shared folders is only granted to the user group vboxsf ,
which is created by the VirtualBox Guest Additions installer. Hence guest users have to
be member of that group to have read/write access or to have read-only access in case
the folder is not mapped writable.
This has been a requirement every since the automount feature was introduced. Manual mount does not require this but you need to do additional steps to mount and to make it permanent.
Post Reply