Ask Your Question

Revision history [back]

Virtualbox Guest Additions (Fedora 29 as Guest on Windows Host)

Hi,

I'm using the latest virtualbox version ( v6.0.4 r128413 ). Host is Windows 7 Ent. Fedora 29 guest with all packages updated.

Two following scenarios occur:

Scenario 1

If I try to use the virtualbox guest additions from repo, (6.0.4-1) then I get the following error output from systemctl status vboxservice.

‚óŹ vboxservice.service - VirtualBox guest services
   Loaded: loaded (/usr/lib/systemd/system/vboxservice.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-03-14 10:10:54 GMT; 5min ago
  Process: 1043 ExecStart=/usr/sbin/VBoxService -f (code=exited, status=1/FAILURE)
 Main PID: 1043 (code=exited, status=1/FAILURE)

Mar 14 10:10:54 localhost.localdomain VBoxService[1043]: 10:10:54.639313 main     6.0.4_Fedora r128164 started. Verbose level = 0
Mar 14 10:10:54 localhost.localdomain VBoxService[1043]: 10:10:54.641816 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
Mar 14 10:10:54 localhost.localdomain VBoxService[1043]: 10:10:54.646834 main     Error: Failed to become guest control master: VERR_VERSION_MISMATCH
Mar 14 10:10:54 localhost.localdomain VBoxService[1043]: 10:10:54.647097 main     Error: Service 'control' failed to initialize: VERR_VERSION_MISMATCH
Mar 14 10:10:54 localhost.localdomain VBoxService[1043]: 10:10:54.647177 main     Session 0 is about to close ...
Mar 14 10:10:54 localhost.localdomain VBoxService[1043]: 10:10:54.647188 main     Stopping all guest processes ...
Mar 14 10:10:54 localhost.localdomain VBoxService[1043]: 10:10:54.647261 main     Closing all guest files ...
Mar 14 10:10:54 localhost.localdomain VBoxService[1043]: 10:10:54.647291 main     Ended.
Mar 14 10:10:54 localhost.localdomain systemd[1]: vboxservice.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 10:10:54 localhost.localdomain systemd[1]: vboxservice.service: Failed with result 'exit-code'.

First things I note from this output is: - Repo version is 6.0.4 with revision 128164. But I would imagine this shouldn't be the cause of the problem despite the reversion being slightly different. I know in the past I've had no issues with slight differences of reversions, only major build numbers. - VERR_VERSION_MISMATCH - I'm not sure what it believes is mismatched.

At this stage, this is a clean install trying to opt for the use of guest additions rpm from fedora repos.

Scenario 2

Since scenario 1 was a flop, I've then proceeded to install guest additions from the virtualbox guest additions cdrom by compilation.

For clarity, I remove the OS package virtualbox-guest-additions and reboot before proceeding to compile the included package from CD.

Once compiled, I reboot to let modules take effect.

Here's the problem, upon reboot things are looking promising until a point when the Vboxservice starts to load. Then it hangs for considerable amounts of time (4 minutes most of the time). It will then proceed to boot and provide all features.

Obviously the boot up time is a problem here for me.

Oddly, and without understanding why, if I change the grub parameters to remove rhgb from the boot statement it will boot much quicker and not hang at the point of Vboxservice.

To conclude,

I'd prefer to go with OS packages, I don't understand the VERR_MISMATCH_VERSION specifically and to what it's mismatched against.

However, if I use the ones included with virtualbox - Again I don't mind doing this and manually recompiling the modules when kernel is upgraded, however I don't understand why it would hang for such a delay on boot when rhgb is on. Maybe a change to plymouth (or whatever the splash screen is nowadays) is causing the issue.

Note: I'm trying to get the boot logs, but what I can say from observation myself is there's no notable log from vboxservice, after the delay it will just continue to boot normally with chronyd being the next to log.

My work around at the moment is I'm running without rhgb in the boot options.

Conclude

I have a workaround, but I'm quite the fan of fedora and like it to work as it should and preferable to use repo updated packages where possible for simplicity and to allow me to use the system for productivity and not be overly sysadmin.

Any advice, or thoughts would be appreciated as I've hit a bit of a brick wall currently for ideas.

This has worked in the past on 6.0.4, I'm unable to establish what changed as I've tried older kernels and doesn't change the situation.

Many thanks,

JD