[Solved] VirtualBox 5.1 to 5.2 on CentOS 7.4

Discussions related to using VirtualBox on Linux hosts.
Post Reply
adrian_vg
Posts: 12
Joined: 18. Mar 2015, 10:36

[Solved] VirtualBox 5.1 to 5.2 on CentOS 7.4

Post by adrian_vg »

Hello all,

Just now updated VirtualBox 5.1 to 5.2 on my CentOS 7.4 host.

Running Virtualbox from the apps menu does nothing - nothing happens.
So next I tried starting it from a terminal. Nothing happens there either. Same thing whether I try to start it as root or regular user.

Got the below:

Code: Select all

[root@lanfear Downloads]# yum install VirtualBox-5.2
...
Installed:
  VirtualBox-5.2.x86_64 0:5.2.0_118431_el7-1                                                                                    

Complete!
[root@lanfear Downloads]# VirtualBox
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: <NULL>

VirtualBox: Tip! It may help to reinstall VirtualBox.
[root@lanfear Downloads]#
Tried uninstalling, then installing again, and still have the same problem.
After doing some google searching I ran into the below.

From https://wiki.centos.org/Manuals/Release ... ce807eee7c.
VirtualBox (5.1.26 or older) is not fully compatible with CentOS-7 (1708). Use 5.1.28 or later.

So what gives, seeing as I did use a later version than the recommended 5.1.28?

All necessary users are members of the virtualbox group.

Hints or comments greatly appreciated.
Thanks.
Last edited by adrian_vg on 23. Oct 2017, 10:00, edited 1 time in total.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VirtualBox 5.1 to 5.2 on CentOS 7.4

Post by Perryg »

Was this an inplace upgrade? If so I would remove the install, reboot, and then try to install again. Sometimes when major upgrades come out it requires that you remove what you have first to offset conflicts. I built my personal install script to always remove before install. It does not take that much longer and eliminate these conflicts.
adrian_vg
Posts: 12
Joined: 18. Mar 2015, 10:36

Re: VirtualBox 5.1 to 5.2 on CentOS 7.4

Post by adrian_vg »

I always remove the current release first, in this case the 5.1, before installing the new 5.2.
IIRC you can't have two virtualbox-releases installed at the same time, as the install of the newer version fails.

Just after posting the original question, I tried what you describe with no success.
Last edited by socratis on 23. Oct 2017, 21:00, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VirtualBox 5.1 to 5.2 on CentOS 7.4

Post by Perryg »

The error you are receiving indicates a few things. From left over packages that conflict to version conflicts of older packages that are needed to work properly. Really hard to say since there are so many things that the host can have out of date or wrong.

Search for "supR3HardenedMainInitRuntime" in your favorite search engine and see if you find something. Especially search "supR3HardenedMainInitRuntime site:virtualbox.org" since it would narrow down your search parameter.
adrian_vg
Posts: 12
Joined: 18. Mar 2015, 10:36

Re: VirtualBox 5.1 to 5.2 on CentOS 7.4

Post by adrian_vg »

Yum should handle those dependency problems.
It has always done so.

Thanks though, I'll look around.
I was kinda' hoping it was a simple fix. :-)
Last edited by socratis on 23. Oct 2017, 21:00, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
adrian_vg
Posts: 12
Joined: 18. Mar 2015, 10:36

Re: VirtualBox 5.1 to 5.2 on CentOS 7.4

Post by adrian_vg »

Spot on!

Searched https://www.google.se/search?q=supR3Har ... BdjpX9FA9I.

Found https://www.virtualbox.org/ticket/16759.

For some reason the folders /usr and /usr/lib had perms set to a non-root user, ie to my own regular user-account. I've no idea why this happened, but there it is.
After changing the permissions, Virtualbox starts properly.

Thanks!

OP changed to Solved for posterity.
Post Reply