I'm not able to mount VirtualBox shared folders in Rawhide since kernel-6.5 began. Works fine up to kernel-6.4.0-59.fc39.x86_64. Reproducible: Always Steps to Reproduce: 1. Boot a VirtualBox VM Rawhide guest using kernel-6.5.0 2. Try to mount a host shared folder. 3. Actual Results: Nothing happens, also there is no error message from the mount command. Expected Results: Should mount the share. I mount using this sort of syntax from a bash script: sudo mount -t vboxsf -o rw,uid=$UID,gid=$(id -g) share_name local_mnt This worked fine through kernel-6.4 in Rawhide (and the test week kernel-6.4.3 in a Fedora 38 VM can also mount shares). Host is Fedora 38 (now running test week kernel-6.4.3) and VirtualBox is VirtualBox-7.0.8-1.fc38.x86_64 from RPMFusion. Rawhide is using virtualbox-guest-additions-7.0.8-1.fc39.x86_64.
for reference fix for kernel 6.4 ( which is not the 6.5 reported here ) from OpenSuse in around shared folders , I don't konw if it is related https://build.opensuse.org/package/view_file/Virtualization/virtualbox/fixes_for_kernel_6.4.patch?expand=1
The release notes for VirtualBox 7.0.10 indicate that their Guest Additions are not yet compatible with kernel-6.5, presumably that applies to the drivers in the kernel also. I'm guessing they are the upstream maintainers.
It looks like there is a patch to fix the problem that's not yet merged: https://www.virtualbox.org/pipermail/vbox-dev/2023-July/010208.html
This is fixed by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=a8f014ec6a21 Which should get merged into a future 6.5-rc# soon.
I see that Linux next-20230728 now contains the patch but our build from the same day https://koji.fedoraproject.org/koji/buildinfo?buildID=2265541 doesn't seem to fix the problem. I don't know the mechanism to determine if the patch is in our local build or not though.
It looks like our local Fedora build kernel-6.5.0-0.rc5.20230809git13b937206866.38.fc40 here https://koji.fedoraproject.org/koji/buildinfo?buildID=2271715 has the patch that fixes this issue.
(In reply to Ian Laurie from comment #6) > It looks like our local Fedora build > kernel-6.5.0-0.rc5.20230809git13b937206866.38.fc40 here > https://koji.fedoraproject.org/koji/buildinfo?buildID=2271715 has the patch > that fixes this issue. Right, the patch was merged upstream, so lets close this now.