Symbolic links suddenly rejected as Shared folders => fixed in svn

[isobot]

While I understand why a VM is not allowed to set or change symbolic links inside a shared folder, there is no good reason why the shared folder itself cannot be set by a symbolic link, since that’s completely outside of the guest system’s control. The check should only look into the content of a shared folder which can be accessed by the guest, but not on the shared folder itself. With previous VirtualBox versions it was easy to change the environment of a VM via just changing the soft link on the host side. Now we need to move or copy complete directories around or change the VM configuration itself, which negatively affects runtime, space or data safety and flash write cycles.

[isobot]

host type is Debian Bullseye 11.1.0 Can't update that in the field itself any more.

[JP95]

"Same" here.

I am using RDP to connect to a Windows 10 machine (the host) and share a folder with RDP. This shared folder is available in the host as

\\tsclient\data

I can access it from the host and can add it as shared folder (which I did). But since 6.1.30 the shared folder is empty when accessed from the guest. The content is still visible from the host so the error is in VirtualBox. Guest is Windows 7.

[galitsyn]

Hi guys,

Thank you for pointing out. One of the "Latest 6.1.x test builds" from https://www.215389.xyz/wiki/Testbuilds should have the problem fixed (any revision starting from r151934).