Virtualbox-bin doesn't start any longer.. [SOLVED]

vespaman · Last edited by vespaman on Wed Aug 02, 2017 7:08 am; edited 1 time in total

Since a week or so, I can no longer start a virtual machine. The actual UI of VB starts up, but once selecting a virtual machine, I get a dialog ;

Window header: "Error in supR3HardenedMainInitRuntime"

markisthejob · Posted: Tue Aug 01, 2017 6:39 pm Post subject:

did you

Zucca · Posted: Tue Aug 01, 2017 6:44 pm Post subject:

First try to update app-emulation/virtualbox-modules.
If that doesn't help, then try to emerge app-emulation/virtualbox instead.
It seems that virtualbox-bin has been masked...
_________________
..: Zucca :..
Gentoo IRC channels reside on Libera.Chat.
--

vespaman · Posted: Wed Aug 02, 2017 5:48 am Post subject:

Sorry, I have alreay tried to re-emerge virtualbox-modules, I even unmerged it to make virtualbox-bin pull it in again.
I have not updated my kernel since May 2016 (4.6.0-gentoo), could this be an issue? Will try to update to something newer..

@Zucca, I can't see that virtualbox-bin has been masked?

vespaman · Posted: Wed Aug 02, 2017 7:08 am Post subject:

OK, upgrading kernel did it!

I actually think something was broken in the older kernel folder, but I anyway needed to update, since it was getting a bit old.

Thanks guys for steering me in that direction!

Zucca · Posted: Wed Aug 02, 2017 8:30 am Post subject:

orionbelt · Apprentice Joined: 05 Apr 2006 Posts: 178

I am experiencing the exact same problem mentioned in the first posting. I re-emerged both virtualbox and virtualbox-modules (in that order), and there was no kernel change since then. However, the same error still happens.

But i noticed that "emerge --ask @module-rebuild" wants to re-emerge virtualbox-modules even though it was just re-emerged. Furthermore, if i let "emerge --ask @module-rebuild" do its job (it concludes without errors), and then i rerun "emerge --ask @module-rebuild", it still wants to re-emerge virtualbox-modules! Does anyone have any idea why this is happening? Could it mean that some modules are not placed where they should be, and therefore virtualbox does not find them and produces the error message in question?

orionbelt · Apprentice Joined: 05 Apr 2006 Posts: 178

No news is bad news? :lol:

Safokoi · n00b Joined: 15 Oct 2013 Posts: 2

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.

(O_o)

equery l "*virtualbox*"
* Searching for *virtualbox* ...
[IP-] [ ] app-emulation/virtualbox-5.2.14-r1:0
[IP-] [ ] app-emulation/virtualbox-modules-5.2.14:0

genterminl · Posted: Thu Dec 27, 2018 8:03 pm Post subject:

check (lsmod) whether any of the vbox modules are already loaded. If so, you need to rmmod them, then load the newly compiled ones. This would happen if you ever ran VirtualBox since booting, or if you have those modules automatically loaded every boot. Just compiling the new ones does not replace modules already loaded to the running kernel. A reboot would also fix it, IF this is the problem.

eNca · Posted: Sat Jan 09, 2021 8:50 pm Post subject:

figueroa · Posted: Sun Jan 10, 2021 3:32 am Post subject:

Also: