Mageia forum

I've run virtualbox on this host previously, I'm sure.

Done a clean mga5.1 install. Installed virtualbox, created a vm, then went to start the install, and it get hit with

Code: Select all

RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

'/sbin/vboxconfig'

may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

So, I checked all my update media were set right, and updated. No change. Left for a few days, no change. I've even reinstalled, but no change.

Strange one, not sure if I'm doing something wrong, or I've hit a bug.

Which virtualbox packages do you have installed?

I am using the desktop kernel and have only:

Code: Select all

$ rpm -qa | grep virtualbox
virtualbox-5.1.22-1.mga5
virtualbox-kernel-4.4.68-desktop-1.mga5-5.1.22-3.mga5
virtualbox-doc-5.1.22-1.mga5
virtualbox-kernel-desktop-latest-5.1.22-3.mga5

You should not have any vbox* packages installed - those are for Mageia guest systems.

Jim

Hey Jim

Code: Select all

rpm -qa | grep virtualbox
virtualbox-doc-5.1.22-1.mga5
virtualbox-kernel-3.19.8-desktop-3.mga5-5.0.2-2.mga5
virtualbox-kernel-desktop-latest-5.1.22-3.mga5
virtualbox-kernel-4.4.65-desktop-1.mga5-5.1.22-2.mga5
virtualbox-5.1.22-1.mga5
virtualbox-kernel-4.4.68-desktop-1.mga5-5.1.22-3.mga5


I tried

Code: Select all

rpm -qa | grep vbox

and nothing was returned.

And you're running what kernel currently?

Thanks Dok

Code: Select all

uname -a
Linux localhost 4.4.68-desktop-1.mga5 #1 SMP Sun May 14 17:56:12 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


Well, that's interesting. I would have thought I should be using

Code: Select all

virtualbox-kernel-4.4.68-desktop-1.mga5

Thoughts?

Well, that's what you have installed, right?

I can only suggest to remove the virtualbox-kernel* packages and instead use dkms-virtualbox, that's what I've been using and never got such a mismatch.

virtualbox-kernel is not a kernel but a kernel module.

The only other possibility I can think of is that if you previously installed a version of virtualbox from their web site, there may be remnants remaining.

Code: Select all

dkms status -m virtualbox

executed as root, may possibly give a clue.

Jim

I uninstalled virtualbox, and all the virtualbox-kernel stuff.

I then reinstalled virtualbox, and hey I could install from a mageia 5.1 iso.

So you'd think it's fixed?

Well, no. I updated the vm during the install, and now the vm will only boot on it's original kernel. If using the updated vm kernels the only clue is it complains of failing to start wait for plymouth boot screen to quit.

This is bizarre...

Jim, no, this was a fresh mga5.1 install, with virtual box from the repos.

Reinstalled the guest VM, but it will only boot with kernel 4.4.30-desktop-2 regardless of how I update it (ie. during or after install).

I tried booting the others with 'quiet and splash' removed from the kernel line, but no luck.

This is the first time I've ever struck a kernel issue like this. Do I try to debug, or wait for next kernel update to see if it sorts it out?

I've set it to boot off the kernel that works, so the vm is at least usable.

You're now talking about an issue within the VM, right? That is usually caused by the vbox additions, or more precisely the graphics part.
If you select a different graphics driver like vesa via drakx11 in failsafe mode it should boot right?

Thanks for you help guys. Up until this point I've had no VB issues, so not sure what I've done different.

Doktor, correct, it is the VM install acting up now. I did have a play with XFdrake but no success. I will have another go, see if I can get past this.

Doktor

I tried both xorg:vesa and vendor:vesa, but it still fails to boot.

It fails to boot or it fails to start the X server? You should be able to switch to a tty and check via journalctl -ab and the content of /var/log/Xorg.0.log

Sorry, yes, it fails to start x server. I can switch to tty, so I'll check that out late.

Thanks Dok

Apologies, I'm not sure best way to get a copy and paste off a vm with no gui

Ok, not 100% sure what to look for here, but in the /var/log/Xorg.0.log towards the end it says screen 0 deleted because no matching config section, unload module vesa, devices detected, but none matching those in config file, no screens found.

So I'm thinking I need to change the display/monitor type?

xboxboy wrote:Apologies, I'm not sure best way to get a copy and paste off a vm with no gui

Do a local portforwarding for the VM for port 22 and then connect via ssh to the VM?

xboxboy wrote:no screens found.

So I'm thinking I need to change the display/monitor type?

No, it's usually about the display driver. Do you have an /etc/X11/xorg.conf ? Remove it if you do. Also try reselecting the virtualbox driver via drakx11.

Thanks Doktor.

I made the mistake of deleting xorg.conf, then running drakx11, but that kept failing to start the x-server (the test in drakx11 also always failed).

So out of frustration, I deleted, xorg.conf and rebooted... and up X-server came... Reset the boot to always use latest kernel, all fixed!

Thank you! This is to be my cauldron VM