Hello,
I was running Solus as a guest within Virtualbox with no problem, until lately I noticed vboxservice cannot start anymore in Solus.
I guess something has changed after an update, though I cannot tell which update, neither if root cause is on host or guest. FYI, my host (running VirtualBox) is OpenSuSE Tumbleweed.
Guest and host OS last upgraded on 2019-04-26.
Guest tools installed via eopkg
So, guest tools have been installed with eopkg it virtualbox-guest-common and virtualbox-guest-current command.
Versions of VirtualBox are consistant between host and guest.
I can then mount vboxfs shared folders, and opt for any display resolution... but none of other additional features are available (e.g. shared clipboard) !
And indeed, systemctl status vboxservice.service raises an error :
Process: 734 ExecStart=/usr/sbin/VBoxService -f (code=exited, status=1/FAILURE)
...
Apr 29 20:28:56 su105 VBoxService[734]: 18:28:56.874780 main 6.0.4_Solus r128164 started. Verbose level = 0
Apr 29 20:28:56 su105 VBoxService[734]: 18:28:56.875435 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
Apr 29 20:28:57 su105 VBoxService[734]: 18:28:57.012580 main Error: Failed to become guest control master: VERR_VERSION_MISMATCH
Apr 29 20:28:57 su105 VBoxService[734]: 18:28:57.012907 main Error: Service 'control' failed to initialize: VERR_VERSION_MISMATCH
Apr 29 20:28:57 su105 VBoxService[734]: 18:28:57.013019 main Session 0 is about to close ...
Apr 29 20:28:57 su105 VBoxService[734]: 18:28:57.013034 main Stopping all guest processes ...
Apr 29 20:28:57 su105 VBoxService[734]: 18:28:57.013042 main Closing all guest files ...
Apr 29 20:28:57 su105 VBoxService[734]: 18:28:57.013054 main Ended.
Apr 29 20:28:57 su105 systemd[1]: vboxservice.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 20:28:57 su105 systemd[1]: vboxservice.service: Failed with result 'exit-code'.
I tried to un-/re-install. No success.
Guest tools installed manually from VirtualBox CD
I decided to uninstall eopkg packages. And opted for manual installation with VirtualBox Guest Additions CD - as I used to do with old versions of Solus, btw...
Good news is that my previous issues were fixed 👍️
rao 1285 1 0 21:11 ? 00:00:00 /usr/bin/VBoxClient --clipboard
rao 1286 1285 0 21:11 ? 00:00:00 /usr/bin/VBoxClient --clipboard
rao 1298 1 0 21:11 ? 00:00:00 /usr/bin/VBoxClient --display
rao 1300 1298 0 21:11 ? 00:00:00 /usr/bin/VBoxClient --display
rao 1308 1 0 21:11 ? 00:00:00 /usr/bin/VBoxClient --seamless
rao 1309 1308 0 21:11 ? 00:00:00 /usr/bin/VBoxClient --seamless
rao 1320 1 0 21:11 ? 00:00:00 /usr/bin/VBoxClient --draganddrop
rao 1321 1320 0 21:11 ? 00:00:00 /usr/bin/VBoxClient --draganddrop
but to the cost of a new problem : loss of vboxfs 👎️
Apr 29 21:11:26 su105 systemd[1]: Starting vboxadd.service...
Apr 29 21:11:26 su105 vboxadd[744]: VirtualBox Guest Additions: Starting.
Apr 29 21:11:30 su105 useradd[924]: failed adding user 'vboxadd', data deleted
Apr 29 21:11:30 su105 useradd[925]: failed adding user 'vboxadd', data deleted
Apr 29 21:11:30 su105 vboxadd[744]: VirtualBox Guest Additions: modprobe vboxsf failed
Apr 29 21:11:30 su105 systemd[1]: Started vboxadd.service.
Last words
Manual installation of guest tool is definitely not my choice, as I don't intend to install them again and again after Solus upgrade. And also because I do need vboxfs more than any other feature.
So, for now, back on reliable Solus packages for this guest tool...
Any suggestion would be grantly appreciated ^^
