ValueError: mount.vboxsf already defined

[DonC]

I am running Oracle Linux 8.2 using VB Version 6.1.12 r139181 (Qt5.6.2). When I run the install of the guest additions, I get the following:

Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.12 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 6.1.12 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel 
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 
5.4.17-2011.3.2.1.el8uek.x86_64.
ValueError: File context for /opt/VBoxGuestAdditions-6.1.12/other/mount.vboxsf already defined
VirtualBox Guest Additions: Running kernel modules will not be replaced until 
the system is restarted
Press Return to close this window...

The ValueError error kind of stands out but unsure if it effects anything or not. I have attached the full log file.

[DonC]

Machine log file

[DonC]

Added vboxadd-install.log and vbox-setup.log to the report. They don't seem to show anything but just in case you wanted to see them.

[Frank Batschulat (Oracle)]

This does not constitute a problem per-se. The installer attempts to create a SELinux file context for the mount.vboxsf file, but one already exists. Presumably from a previous installation or the Linux distribution in question did deliver it with some distro specific GAs already.

in Detail the error comes from execution of:
trunk/src/VBox/Additions/linux/installer/vboxadd.sh

384 shared_folder_setup()
385 {
386     # Add a group "vboxsf" for Shared Folders access
387     # All users which want to access the auto-mounted Shared Folders have to
388     # be added to this group.
389     groupadd -r -f vboxsf >/dev/null 2>&1
390 
391     # Put the mount.vboxsf mount helper in the right place.
392     ## @todo It would be nicer if the kernel module just parsed parameters
393     # itself instead of needing a separate binary to do that.
394     ln -sf "${INSTALL_DIR}/other/mount.vboxsf" /sbin
395     # SELinux security context for the mount helper.
396     if test -e /etc/selinux/config; then
397         # This is correct.  semanage maps this to the real path, and it aborts
398         # with an error, telling you what you should have typed, if you specify
399         # the real path.  The "chcon" is there as a back-up for old guests.
400         command -v semanage > /dev/null &&
401             semanage fcontext -a -t mount_exec_t "${INSTALL_DIR}/other/mount.vboxsf"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^6
402         chcon -t mount_exec_t "${INSTALL_DIR}/other/mount.vboxsf" 2>/dev/null
403     fi
404 }

You can cleanup before the installation using the following commands and then rerun the installation.

# semanage fcontext -d /opt/VBoxGuestAdditions-<VERSION>/other/mount.vboxsf
# restorecon /opt/VBoxGuestAdditions-<VERSION>/other/mount.vboxsf

This is the result of the SELinux user interface itself, see:

Bug 1609488 - semanage fcontext should not fail when adding the same entry ​https://bugzilla.redhat.com/show_bug.cgi?id=1609488

and a such this is a benign error we can ignore.