Is it 5.0.22 or is it 5.1.8?

[RicV]

Now that I've upgraded my VirtualBox build environment to 5.1.8, and installed it on my Ubuntu 14 test machine, I found something surprising about version numbers.

I had carefully removed all traces of 5.0.22 from /opt and /usr/bin and then rebooted before running my 5.1.8 installer (VirtualBox-5.1.8-r111374.run) and rebooted again. Now both the VBoxManage program and VirtualBox GUI Help/About screen show that it’s version 5.0.22 still. However the user manual pdf says that it's 5.1.8, and the file creation dates match my 5.1.8 build. How can the programs and manual be different versions?

Well I tried to launch one of my VMs anyway, but it failed because the kernel module version does not match the VirtualBox version. It suggested using /sbin/rcvboxdrv setup, which said that it built the kernel modules and services, but the problem remains. I wonder if this version number is related to the one above?

Is there something I missed in the transition from 5.0.22 (standard distribution) to 5.1.8 (my own build)?

[Perryg]

Which installer? You compiled the tarball and this usually runs in user space and normally is not hardened. Explain what you do/did.

[RicV]

Hi Perry,

I used an adaptation of your recommended procedure, found in this topic: viewtopic.php?f=31&t=70118

1. In my top level source directory (from the 518 tarball), renamed from VirtualBox-5.1.8 to ose518, I did kmk all

2. I used the following script which I adapted from your post

Code: Select all

pushd out/linux.amd64/release/bin/src
make
sudo make install
popd

pushd src/VBox
kmk packing
popd

cp out/linux.amd64/release/bin/VirtualBox*.run .
ls -lht *.run

3. This created VirtualBox-5.1.8-r111374.run which I scp over to my test machine where I installed it.

Exact same procedure I have been using with 5.0.x for a year at least.

[Perryg]

OK so how exactly did you remove the previous version?

[RicV]

sudo rm -rf /opt/VirtualBox
sudo rm -rf /usr/bin/vbox*
sudo rm -rf /usr/bin/virtualbox

[Perryg]

Well that might be an issue. Normally you run the old installer with the uninstall tag. This removes all traces of the main program. From the sounds of it you still have something that is playing nasty with the new install. Run VBoxManage and verify the version that is installed and look at the /var/log/vbox-install.log for any errors.

[RicV]

It turns out that the standard distribution of 5.0.22 had been installed on this machine, so I had to remove that package before running my own installer. Now VBoxManage -v reports 5.1.8r111374
, but I can't run the VirtualBox GUI due to a missing symbol

ricv@HP-Z230-Workstation:~/vbox$ VirtualBox
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/opt/VirtualBox/VirtualBox.so",) failed: /opt/VirtualBox/VirtualBox.so: undefined symbol: _ZN7QString15toLatin1_helperERKS_
ricv@HP-Z230-Workstation:~/vbox$ VBoxManage -v
5.1.8r111374

[Perryg]

Did you search for "undefined symbol: _ZN7QString15toLatin1_helperERKS_ ricv" to find a resolve?
Something is not quite right with QT. Maybe the config file.