It will be my pleasure! I'll try and sort it out:scottgus1 wrote:fth0, I wonder if you'd mind explaining this again, please.
VirtualBox Guest Additions (GA) for Linux guests
1. The VirtualBox Guest Additions (GA) for Linux guests consist of
- kernel modules (e.g. vboxguest, vboxsf),
- services (e.g. VBoxService),
- applications (e.g. VBoxClient, VBoxControl) and
- scripts (e.g. vboxadd).
a) ... contains the services and applications as already built executables and copies the files to their destination folders (e.g. /opt/VBoxGuestAdditions-6.1.44/...).
b) ... copies the (also ready-made) scripts to their respective destination folders (presumably dependent on the Linux distribution).
c) ... contains the kernel modules as source code. In order to build the kernel modules, some pre-requisites are needed, which depend on the Linux distribution and the Linux kernel (e.g. compiler and tools, Linux kernel headers). The basic reason is that the kernel modules have to match the current Linux kernel; whenever the Linux kernel is updated (typically every few weeks), the kernel modules are also built anew.
3. The potentially problematic combination (visualized by the underlines and strike-throughs):
a) If the GA installer is unable to build the kernel modules, it only installs the services, applications and scripts.
b) Some Linux distributions pre-install an older version of the VirtualBox kernel modules, as part of a large collection of kernel modules, but not the VirtualBox services, applications and scripts. Technically speaking, this is not a pre-installation of the GA, BTW.
c) The implementation of many of the GA' functionalities (e.g. Shared Clipboard, Shared Folders) is distributed on the GA' services, the GA' kernel modules and VirtualBox host-side parts. In consequence, those functionalities work best when the necessary components have the same version number.
The "Guest Additions information report" log message shows the version of the vboxguest kernel module, and the "VBoxService" ... is an easy guess. There is no need to uninstall the pre-installed kernel modules (and it's usually difficult anyway): They work better than having no kernel module, and when the prerequisites (especially the Linux kernel headers) are available, the next rebuild of the VirtualBox kernel modules should succeed.scottgus1 wrote:If "Guest Additions information report" and "VBoxService" versions don't match, is this an indication of mismatched kernel headers requiring a purge and reinstall of prerequisites and Guest Additions? I seem to remember you may have mentioned that mismatched version numbers wasn't necessarily a problem, but I may not remember correctly?
On a Linux host, the situation is quite similar to the situation on a Linux guest: VirtualBox consists of ... and kernel modules (e.g. vboxdrv). The main difference is that Linux distributions do not pre-install the VirtualBox host-side kernel modules, and if the VirtualBox installer cannot build its kernel modules, you cannot successfully run a VM afterwards.scottgus1 wrote:O maybe we were discussing Virtualbox on the host last time?
Please let me know if you have further questions or if I can improve my explanations above.