For as long as I have been using it, installing VirtualBox from the .run file "for all distributions" first removes the old installation from /opt/VirtualBox and that has not changed. Moreover, it unconditionally uninstalls it, whether upgrading or downgrading, it runs the uninstaller.

What the advice is probably trying to cover is VirtualBox installed from another source. You wouldn't want to have, say, a clever distro package (or their rpms or debs) installed then use their .run file to install the official binaries to /opt.

If you have shares to access them easily don't forget to

sudo adduser <username> vboxsf

If it fails the guest additions are not in place do

shutdown -r 0

If adduser works also do a shutdown -r 0 This needs to be done.

This will fix your shares, screen resolution, mouse integration <copy/paste>

Ken

I registered to give a big Thank You to the OP. I had the issue that the 6.0.14 virtualbox kernel modules would not build for Linux kernel 5.4.10 on Artix Linux (Arch without systemd). While the kernel modules would build for Virtualbox 6.1.0, this is a no-go for me as the new VboxSVGA driver simply does not work for my Windows 7 virtual machines (3D acceleration completely broken for me).

The patch here worked like a charm!

@rahrah
Thanks for this post.

This patch works for me.