Jonners59 wrote:I don’t agree.
That's fine. I too have found places where instructions and the manual were hard to understand.
Jonners59 wrote: Even the download page is a mess of confusion, especially when it comes to understanding and finding the correct Guest Additions.
This is because users of official Virtualbox don't have to find the Guest Additions. They're bundled with the download of the official Virtualbox installer, so they don't need to be downloaded separately. The reason why you may have had to try to find the GAs ISO is because of this:
Jonners59 wrote:I am running Virtual Box Version 6.1.26_Ubuntu
You're running a forked version of Virtualbox, which we don't support on this forum, and which may require a separate download of forked GAs. You'd need to get the forked GAs from the fork's repository, not from
http://www.virtualbox.org.
Jonners59 wrote:It was because I had sorted the “VERR_PDM_MEDIA_LOCKED” in the previous reply
No you didn't. You worked around the problem by adding another CD drive, not by solving the original problem by getting the VM OS to release the CD. If your installed OS does require the OS installer CD to still be present you would need another CD drive to load other ISOs. But adding CD drives to get around VERR_PDM_MEDIA_LOCKED is not the solution. It's a work-around, and may cause trouble later on.
Jonners59 wrote:I couldn’t recall ever doing all these steps when I installed GA the various times in the past
You hadn't got stopped with VERR_PDM_MEDIA_LOCKED before, apparently. The solution is to release the OS's hold on the mounted CD so it can be ejected from the VM's OS, or shut down the VM so the OS is not longer holding the CD.
Jonners59 wrote:reloaded the log file as txt. No need to zip it as it was very small. The *.vbox file I re-uploaded but it was the same as the previous so not really necessary, but done just the same. I simply zipped it though it was small.
Note to other readers, Jonners59 edited the earlier post to have the log and .vbox file uploaded.
Regrettably, the log is incomplete. This part was not followed:
scottgus1 wrote:Run until you see the problem happen, then shut down the VM from within the VM's OS.
The portion of log has some interesting issues showing up:
00:00:16.892735 VMMDev: Guest Log: 10:26:16.384848 main Error: Failed to become guest control master: VERR_VERSION_MISMATCH
00:00:16.893257 VMMDev: Guest Log: 10:26:16.385376 main Error: Service 'control' failed to initialize: VERR_VERSION_MISMATCH
My guess is that the Guest Additions are not installed correctly inside the VM OS. This can happen if the VM OS has "helpfully" pre-installed the GAs from their fork, then these preinstalled GAs are not completely uninstalled before new GAs are installed.
Or it could be the really old Guest Additions. 5.2.0 GAs is really long in the tooth from a 6.1.26 host Virtualbox standpoint.
Failed Guest Additions would not allow shared folders or display to work properly.
I would recommend these steps:
Take a complete host disk image to ensure restorability
Uninstall both the Ubuntu fork Virtualbox and the GAs in the VM. Use the typical Linux methods to ensure that Virtualbox and GAs are completely gone. Official non-forked Virtualbox does not use dkms, so no need to install that.
Run the prerequisites in both the host and the VM.
https://www.virtualbox.org/manual/ch02. ... nux-prereq The same prerequisites apply for both Virtualbox on the host and GAs in the VM.
Install correct Virtualbox from
https://www.virtualbox.org/wiki/Linux_Downloads. Guest Additions will come bundled with the installer. Use the Devices menu, Insert Guest Additions CD Image command to load the GAs ISO in the VM, then run the GAs installer in the VM's CD drive.