Page MenuHomeSolus

Solus Mate in Virtualbox current kernel issues
Closed, ResolvedPublic

Description

HI all,

I just installed Solus Mate in the latest virtualbox (5.2.8) and updated it fully. I then proceeded to install the virtualbox drivers as per this page: https://solus-project.com/articles/software/virtualbox/en/
At the step of running the guest additions it fails (sorry I can't copy the message out, will try later). But after switching to the lts kernel like this:

sudo clr-boot-manager set-timeout 5 && sudo eopkg it linux-lts && sudo clr-boot-manager update

It does work and I get all the benefits of the guest additions. However, only with LTS kernel as expected. So I set the LTS kernel as default using sudo clr-boot-manager update while having it booted. This works.

However I have tried some reboots and it seems that after two or more reboots, the virtuabox modules are not loaded anymore, resulting in (among others) the login screen as shown here:

image.png (768×1 px, 926 KB)
. This can be fixed by a quick alt-F1 - alt-F7 but still. The benefits of the guest additions are gone. Rebuilding the guest additions helps but again only for 1-2 reboots.

Highest regards,

Freek

Event Timeline

freekvh updated the task description. (Show Details)
freekvh updated the task description. (Show Details)
freekvh updated the task description. (Show Details)

I keep getting this tag "Lacks project", what does that mean? What project should I add? Does adding a project help in getting issues solved faster?

An update: the building of the guest additions for current does work after:

sudo eopkg install -c system.devel

However, two reboots later the additions are gone again.

Next try: I added to the /etc/modules-load.d/virtualbox.conf the following:

vboxdrv
vboxnetadp
vboxnetflt
vboxpci

And yes, it works! However, one reboot later... it's gone again. I can't even:

sudo modprobe vboxdrv

It gives me an error (FATAL modules not found or similar).

The modules seems to disappear upon reboots.

Ok, last update... It is fixed. I also added

vboxvideo

to /etc/modules-load.d/virtualbox.conf and now the scaling display persists over multiple reboots.

So, if you tell me how I can get the helpcenter article (https://solus-project.com/articles/software/virtualbox/en/) changed, I shall do that to include these steps.

Highest regards.

kyrios123 added a subscriber: kyrios123.

Before updating the help center, I'll have a look at this.
Could you please do me a favor @freekvh and check if you have the problem with the lts kernel as well ?

Had these issues for a while and now it works perfect thanks to @freekvh :)

I have tested before with both kernels so both show the problem.

I just now tested the LTS and indeed now the settings also persists over reboots. I'm thinking it is solved by the entries in /etc/modules-load.d/virtualbox.conf, for both kernels.

I remembered this from my time with Arch, actually the wiki tells me I should probably also add vboxguest vboxsf next to vboxvideo, I think vboxdrv is deprecated. See: https://wiki.archlinux.org/index.php/VirtualBox

An update: the building of the guest additions for current does work after:

sudo eopkg install -c system.devel

You don't have to install the whole system.devel.
You probably just miss libelf-develwhich is required since linux-current-4.15.5-57

Perhaps we should build a virtualbox-guest package.
But personally before doing this, I'd like to see first how it will behave with the next kernel.

@kyrios123 I specifically executed that command (sudo eopkg install libelf-devel) twice, first as described here: https://solus-project.com/articles/software/virtualbox/en/ then again after the error message, which referenced indeed specifically libelf-devel (and 3 other variations on that name). Strangely, this was sorted after switching to LTS. Installing the whole system.devel was only necessary for the current kernel. But I must says all the details are a bit hazy, I tried a lot of things in the end.

A virtualbox-guest package (or kernel) is the Solus way, isn't it? Death to DKMS, right??!

For now, I'm completely comfortable and getting work done with the modules loaded by /etc/modules-load.d/virtualbox.conf.

Oh, putting virtualbox-drivers in the kernel.... even better!

@kyrios123 I specifically executed that command (sudo eopkg install libelf-devel) twice, first as described here: https://solus-project.com/articles/software/virtualbox/en/ then again after the error message, which referenced indeed specifically libelf-devel (and 3 other variations on that name). Strangely, this was sorted after switching to LTS. Installing the whole system.devel was only necessary for the current kernel. But I must says all the details are a bit hazy, I tried a lot of things in the end.

A virtualbox-guest package (or kernel) is the Solus way, isn't it? Death to DKMS, right??!

For now, I'm completely comfortable and getting work done with the modules loaded by /etc/modules-load.d/virtualbox.conf.

Oh, putting virtualbox-drivers in the kernel.... even better!

There is also elfutils-devel but it is not installed on my system and the guest addition builds without error so it should be another package.

@freekvh could you let me know if this solves the problem for you :

Create the following file (with sudo) /etc/X11/xorg.conf.d/10-vboxvideo.conf

Section "OutputClass"
	Identifier "VirtualBox Video Device"
	MatchDriver "vboxvideo"
	Driver "vboxvideo"
EndSection

Then reboot your virtual machine

Hi @kyrios123,

Everything works now after loading the modules. Do think you think your solution would be better?

Still trying to figure out how to get a clean fix for this.

I think lubuntu may have faced a similar issue (see comments #24+)
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1443853

But I unfortunately I am not clever enough to figure out how this could be resolved.

kyrios123 claimed this task.

This was fixed with 4c57107f6318