Cannot run executable in shared folder in Linux/Kali -> Fixed in SVN

[VimExtreme]

I am running two virtual machines in my Debian host: 1 Kali, 1 Windows 10. Both have a shared folder mounted into the guest machines, called "austausch" (= "shared" in English).

In Kali, I start a terminal/bash and try to run an executable bash script like this:

$ cd ~/austausch

$ cat test.sh
#!/bin/bash
echo "Hello world!"

$ ./test.sh
bash: ./test.sh: /bin/bash: Defekter Interpreter: Das Argument ist ungültig (= "broken interpreter: The argument is invalid")

$ bash test.sh
Hello world!

$ cp test.sh ~/
$ cd ~/

$ ./test.sh
Hello world!

$ mount | grep Austausch
Austausch on /media/sf_Austausch type vboxsf (rw,nodev,relatime,iocharset=utf8,uid=0,gid=0)

In Windows 10, there is no such issue and I can run arbitrary exe files from the shared folder.

I am running VirtualBox 6.1.20 on Debian/Host, and it appears to be 6.1.18 in Kali for some reason although I tried to update *now*:

$ apt update
[...]

$ apt install virtualbox-guest-utils virtualbox-guest-x11
[...]
virtualbox-guest-utils ist schon die neueste Version (6.1.18-dfsg-2). (= "is already the newest version")
virtualbox-guest-x11 ist schon die neueste Version (6.1.18-dfsg-2). (= "is already the newest version")

I am not sure when this problem came up initially, but I think it was in VB 6.1.18. I seem to not be the only one with this problem, as a few colleagues of mine have run into this issue, too.

Any ideas what might have gone wrong here?

[VimExtreme]

virtualbox log file for respective kali linux machine

[Klaus Espenlaub]

This is a known issue with the released shared folder code... running things off a shared folder is failing since Linux kernel 5.10. Is it possible that you use an older kernel in your VM for the time until a fix is available?

[VimExtreme]

Replying to klaus:

This is a known issue with the released shared folder code... running things off a shared folder is failing since Linux kernel 5.10. Is it possible that you use an older kernel in your VM for the time until a fix is available?

Oh, that is interesting to hear! I already removed all old kernels from the VM, but will look into this if I can somehow revert to previous versions.

Do you have a clue how long it might take to release an update to Virtualbox, or when this might be fixed in a kernel update?

[galitsyn]

The issue should be fixed in 6.1.22. Could you please give it a try?

[galitsyn]

Fix available since VirtualBox 6.1.24.