2018-09-19 15:20 UTC

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004304Kali Linux[All Projects] General Bugpublic2018-07-28 15:39
Assigned Torhertzog 
Product Version2017.2 
Target VersionFixed in Version 
Summary0004304: virtualbox shared folder
DescriptionAfter the last update to the virtualbox guest additions v.5.1.28 it is no more accessible the content on the shared folder which always is showed as empty folder.
Steps To ReproduceIn a guest kali OS in virtualbox, after the update to the guest additions v.5.1.28 you will verify that the configured shared folder appear always empty.
Additional InformationIn the machine settings, I tried to delete the configured shared folder and to add a new shared folder again. Restarted the Kali VM, any change in the behavior: the new shared folder appear always empty.
Attached Files




erasmo52 (reporter)

Why this issue still not assigned?
I tried to manually install manually (because not offered in the automatic update) the three packets (virtualbox-guest-utils, virtualbox-guest-x11, virtualbox-guest-dkms) v.5.1.30 present on the kali repository. And after restarted the problem persist.
After that I installed manually the three packets (virtualbox-guest-utils, virtualbox-guest-x11, virtualbox-guest-dkms) v.5.1.26 present on the kali repository. And after restarted the kali guest work perfectly and the shared folder in correctly mounted in /media/
After upgraded to the 5.1.28 release (the last offered by the automatic update) and restarted, the kali guest again doesn't mount the shared folder in /media/ folder.
Here we are
Do something to correct the bug, please.
Thank you


erasmo52 (reporter)

Could you resolve the problem releasing a correct version of guest additions for the new virtualbox 5.2.0 release?
Thank you


rhertzog (administrator)

I don't understand what you are requesting. Virtualbox 5.2.0 will come in Kali once it reaches Debian Testing. It just landed in Debian Unstable so you still have a few days to wait. I'm sorry if you have a bug with 5.1.28 but your pet-feature is certainly not critical for Kali. We can't manually handle all the bugs that appear and disappear. That's why we are based on Debian...


erasmo52 (reporter)

Finally the virtualbox-guest- utils v.5.2.0 arrived in the repository and was installed by the last upgrade, but ... but not resolved the problem originating my post, this post.
The Kali virtual machine continue to not see and access the shared folder.
This problem persist from the v.5.1.26, the last release which worked fine with shared folders.
It is very annoying for a good work the impossibility of access shared folders.
Hope the problem will be solved soon
Thank you


erasmo52 (reporter)

Today released in the repository and was installed by the last upgrade the virtualbox-guest- utils v.5.2.2 , but ... but not resolved the problem originating my post, this post.
Where is the problem? Why the Kali guest virtual machine can't see the shared folder?
There is somebody else experiencing the same issue?
Thanks to everybody


mike386 (reporter)

After examining some logs I've just resolved this issue by doing:

apt update && \
apt install dh-exec && \
apt install --reinstall virtualbox-guest-dkms && \

Hope it helps.


rhertzog (administrator)

We have had multiple new version of virtualbox in the mean time. I guess the issues are gone.


erasmo52 (reporter)

No dear friend the problem is not resolved.
I am now operating under virtualbox 5.2.16 with the last kali virtualbox guest additions updated to the last release 5.2.16 too.
Well, the shared folder is configured as automount but it is not automatically mounted and each time under the guest kali I am obliged to execute the command: mount.vboxsf VMshare /home/[username]/VMshare to access the content of the shared folder.
Ok, it is a minor bug. But it is a bug anyway. Constantly present from the release 5.1.28 of the virtualbox guest additions, until now.
Here we are.
Good job and Best Regards.

-Issue History
Date Modified Username Field Change
2017-10-11 09:51 erasmo52 New Issue
2017-10-24 11:55 erasmo52 Note Added: 0007555
2017-10-26 07:19 erasmo52 Note Added: 0007564
2017-10-26 08:03 rhertzog Note Added: 0007565
2017-10-26 08:03 rhertzog Assigned To => rhertzog
2017-10-26 08:03 rhertzog Status new => assigned
2017-11-13 08:22 erasmo52 Note Added: 0007594
2017-12-01 11:57 erasmo52 Note Added: 0007651
2018-01-29 17:11 mike386 Note Added: 0008538
2018-06-22 06:19 g0tmi1k Severity major => minor
2018-07-27 10:31 rhertzog Status assigned => resolved
2018-07-27 10:31 rhertzog Resolution open => fixed
2018-07-27 10:31 rhertzog Note Added: 0009395
2018-07-28 15:39 erasmo52 Status resolved => feedback
2018-07-28 15:39 erasmo52 Resolution fixed => reopened
2018-07-28 15:39 erasmo52 Note Added: 0009402
+Issue History