On Tue, 2021-09-14 at 16:16 -0500, David C. Rankin wrote: > On 9/13/21 10:26 PM, David C. Rankin wrote: > > On 9/13/21 5:40 AM, Vadim Galitsin wrote: > > > Hi David, > > > > > > Additions r146688 should have support for 5.14 kernels. Have you > > > tried to > > > rebuild Additions with "sudo rcvboxadd setup"? > > > > > > Best regards, > > > Vadim > > > > Okay, > > > > Here is/was the deal. Archlinux had issues with it's dkms package. > > There > > were multiple updates upstream and Arch follows upstream. The > > packages updated > > and dates were: > > > > [2021-08-31T02:51:33-0500] [ALPM] upgraded dkms (2.8.4-1 -> 2.8.5-1) > > [2021-09-05T20:29:01-0500] [ALPM] upgraded dkms (2.8.5-1 -> 2.8.6-1) > > [2021-09-12T23:13:51-0500] [ALPM] upgraded dkms (2.8.6-1 -> 2.8.6-2) > > > > The dkms 2.8.6-1 package was acting odd, leaving old folders for > > drivers for > > vbox versions that no longer existed on the system. When I updated to > > 5.14.2 > > with dkms-2.8.6-1 the vboxsf module failed to build for whatever > > reasons. (I > > forced a rebuild on the guest twice but it still didn't build > > correctly) > > > > Today I updated to the Arch package dkms-2.8.6-2 and updated the > > kernel to > > 5.14.3. With the new dkms, the vboxsf module built just like it was > > supposed > > to and everything is working fine on 5.14. > > > > So while I don't know exactly why vboxsf didn't build correctly > > with 5.14.2, > > but I strongly suspect it was due to the issue with the dkms package. > > > > You are correct, the testbuild ver. r146688 support the 5.14 kernel > > just fine. > > > > Let me qualify this a bit. > > I have another Arch server with the same setup. However, I had not > updated > dkms or the kernel on that box until after I succeeded with getting > shared > folders working directly on the first. So yesterday, after I sent this > reply, > I updated that box directly to vbox testbuild r146688, dkms 2.8.6-2 and > Linux > 5.14.3. After updating the kernel, allowing the modules to build and > rebooting > I started the Archlinux guest on the server and updated the kernel to > 5.14.3,, > rebooted, ran the new guest addition install from the .iso and rebooted > expecting the shared folders to work just as they had on the first > server I > migrated. But no, the vboxsf device is found, but the contents of the > directory is empty. > > I re-ran the guest additions install again, rebooted, same problem. > There > seems to be something still going on with the 5.14 update. I'll double- > check > for old dkms folders on this second box, but don't expect any (dkms > status ran > and reported correctly). I'll report back after further investigation. >
Linux kernel may already have the modules (in-tree) https://www.virtualbox.org/ticket/20055?cversion=0&cnum_hist=10#comment:14 ( when we enable CONFIG_DRM_VBOXVIDEO=m, CONFIG_VBOXGUEST=m and CONFIG_VBOXSF_FS=m in kernel, we don't need drm and shared folder patches ) -- Sérgio M. B. _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
