Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Virtualbox-bin doesn't start any longer.. [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
vespaman
Guru
Guru


Joined: 28 Aug 2002
Posts: 309
Location: Stockholm, Sweden

PostPosted: Tue Aug 01, 2017 4:26 pm    Post subject: Virtualbox-bin doesn't start any longer.. [SOLVED] Reply with quote

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"
Code:
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.


I have rememerged virtualbox-bin without any issues, but since it is bin, maybe this the issue here?

I have not found vboxconfig on my filesystem to try, as per suggested.

I'm sure this is a result from an world update some time ago. What could this be?


Last edited by vespaman on Wed Aug 02, 2017 7:08 am; edited 1 time in total
Back to top
View user's profile Send private message
markisthejob
Tux's lil' helper
Tux's lil' helper


Joined: 04 Aug 2008
Posts: 142
Location: Cork, Republic of Ireland

PostPosted: Tue Aug 01, 2017 6:39 pm    Post subject: Reply with quote

did you
Code:
emerge --ask @module-rebuild
after upgrading the kernel

are you selecting the correct kernel where you rebuilt the modules
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1519
Location: KUUSANKOSKI, Finland

PostPosted: Tue Aug 01, 2017 6:44 pm    Post subject: Reply with quote

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 :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
vespaman
Guru
Guru


Joined: 28 Aug 2002
Posts: 309
Location: Stockholm, Sweden

PostPosted: Wed Aug 02, 2017 5:48 am    Post subject: Reply with quote

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?
Back to top
View user's profile Send private message
vespaman
Guru
Guru


Joined: 28 Aug 2002
Posts: 309
Location: Stockholm, Sweden

PostPosted: Wed Aug 02, 2017 7:08 am    Post subject: Reply with quote

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!
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1519
Location: KUUSANKOSKI, Finland

PostPosted: Wed Aug 02, 2017 8:30 am    Post subject: Reply with quote

vespaman wrote:
@Zucca, I can't see that virtualbox-bin has been masked?
Mine was apparently masked because of LICENSE.
_________________
..: Zucca :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
orionbelt
Apprentice
Apprentice


Joined: 05 Apr 2006
Posts: 166
Location: Brussels, Belgium

PostPosted: Sun Sep 23, 2018 9:47 pm    Post subject: Reply with quote

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?

Code:
% equery l '*virtualbox*'
 * Searching for *virtualbox* ...
[IP-] [  ] app-emulation/virtualbox-5.2.14-r1:0
[IP-] [  ] app-emulation/virtualbox-additions-5.2.14:0
[IP-] [  ] app-emulation/virtualbox-extpack-oracle-5.2.14.123301:0
[IP-] [  ] app-emulation/virtualbox-modules-5.2.14:0

% ls -l /usr/src/linux
lrwxrwxrwx 1 root root 20 Sep 17 01:02 /usr/src/linux -> linux-4.14.14-gentoo

Back to top
View user's profile Send private message
orionbelt
Apprentice
Apprentice


Joined: 05 Apr 2006
Posts: 166
Location: Brussels, Belgium

PostPosted: Tue Oct 09, 2018 9:39 am    Post subject: Reply with quote

No news is bad news? :lol:
Back to top
View user's profile Send private message
Safokoi
n00b
n00b


Joined: 15 Oct 2013
Posts: 2

PostPosted: Fri Nov 23, 2018 8:26 am    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
genterminl
Guru
Guru


Joined: 12 Feb 2005
Posts: 488
Location: Connecticut, USA

PostPosted: Thu Dec 27, 2018 8:03 pm    Post subject: Reply with quote

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.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum