The solution is described in this GitHub Gist by Fortunato Estorgio. While this works, the mount is not permanent and is lost after a reboot. Sudo mount -t vboxsf shared /home//Shared To mount the shared folder manually (you know the drill, replace with your login): mkdir /home//Shared My Shared Folder was configured as below:īut, the KDE File Manager, Dolphin, displays an error banner: Could not enter folder /home//Shared: Now the VirtualBox Shared Clipboard is working, as is the display driver (I guess), but not the VirtualBox Shared Folder. Install VirtualBox additions via the virtual CD per normal.Īlternatively sudo apt-get install virtualbox-guest-utils virtualbox-guest-x11 virtualbox-guest-dkms Sudo apt install build-essential kde-plasma-desktop I’m also installing KDE using SDDM as the display manager, which you don’t have to! sudo apt upgrade Install a brand new VirtualBox VM using, with on-line installer and security updates.Īfter login, upgrade and install build-essentials and reboot.

Initially I thought that is needed is to install the build-essential package. Please install the gcc make perl packages from your distribution.

This time however, I got errors during the install - though it’s not very clear that there was a problem: This system is currently not set up to build kernel modules. In previous experience installing Ubuntu Server on a VirtualBox VM, I simply installed VirtualBox additions from the Devices > Install Guest Additions CD image. I had issues with VirtualBox guest additions, and this is how I solved it.

I recently installed Ubuntu 20.04 LTS (Focal Fossa) (dated 23 April 2020), with the intention of creating a VM using VirtualBox 6.0.22 (released ).

Virtualbox guest additions iso ubuntu