﻿id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host
16670,mount.vboxsf symlink broken,chr.moench-tegeder,,"This looks like a regression in 5.1.20.

Guest system is Linux - reproduced with both Debian 8 and openSUSE 42.2.
After upgrading Guest Additions from 5.1.18, the /sbin/mount.vboxsf symlink points to the wrong location:

root@host1:~# ls -l /sbin/mount.vboxsf
lrwxrwxrwx 1 root root 49 Apr 19 10:33 /sbin/mount.vboxsf -> /opt/VBoxGuestAdditions-5.1.20/other/mount.vboxsf
root@host1:~# find /opt/VBoxGuestAdditions-5.1.20/ -name mount\*
/opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf

With previous versions of the Guest Additions (checked 5.1.18 and 5.1.14, that's what I have around currently), /sbin/mount.vboxsf points to /usr/lib{64,/x86_64-linux-gnu}/VBoxGuestAdditions/mount.vboxsf (exact location of the lib64 directory varies per linux distribution, examples taken from CentOS 7 and Debian 8).

A quick test for stale symlinks (find -L / -xdev -type l) shows that mount.vboxsf is the only file affected.
This allows for the simple workaround of fixing the symlink:
root@host1:~# ln -sf /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf

(remember to check the lib64 path for your distribution, e.g. lib64 on Redhat/Centos-based distributions)",defect,closed,guest additions,VirtualBox 5.1.20,fixed,,,Linux,all
