Problems upgrading to VirtualBox 5.1.14

[Lappert]

I'm running Ubuntu 15.10 as my host. Previously I ran Virtualbox 5.0.16. I tried to upgrade to VB 5.1.14 by using "apt-get install virtualbox-5.1."

It seemed to go OK, I can bring up VB manager that lists the virtual machine I ran before (Win7-32).
Help > About VB says I'm running version 5.1.14 r112924 (Qt5.4.2)

But trying to start the Win7-32 gets me two windows:

First window

Code: Select all

VirtualBox - Error

Failed to open a session for the virtual machine Win7-32.

The virtual machine 'Win7-32' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

and the second windows reads:

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.

From the install, here's what the terminal screen said:

Code: Select all

root@mybox:/etc/apt# apt-get install virtualbox-5.1
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following extra packages will be installed:
  libsdl-ttf2.0-0
The following packages will be REMOVED:
  virtualbox-5.0
The following NEW packages will be installed:
  libsdl-ttf2.0-0 virtualbox-5.1
0 upgraded, 2 newly installed, 1 to remove and 160 not upgraded.
Need to get 65.3 MB of archives.
After this operation, 3,847 kB disk space will be freed.
Do you want to continue? [Y/n] y
WARNING: The following packages cannot be authenticated!
  virtualbox-5.1
Install these packages without verification? [y/N] y
Get:1 http://us.archive.ubuntu.com/ubuntu/ wily/universe libsdl-ttf2.0-0 amd64 2.0.11-3 [15.0 kB]
Get:2 http://download.virtualbox.org/virtualbox/debian/ wily/contrib virtualbox-5.1 amd64 5.1.14-112924~Ubuntu~wily [65.3 MB]
Fetched 65.3 MB in 13s (4,951 kB/s)                                                                                                                                                                                                                                          
Preconfiguring packages ...
(Reading database ... 242214 files and directories currently installed.)
Removing virtualbox-5.0 (5.0.16-105871~Ubuntu~wily) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for mime-support (3.58ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Selecting previously unselected package libsdl-ttf2.0-0:amd64.
(Reading database ... 241448 files and directories currently installed.)
Preparing to unpack .../libsdl-ttf2.0-0_2.0.11-3_amd64.deb ...
Unpacking libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Selecting previously unselected package virtualbox-5.1.
Preparing to unpack .../virtualbox-5.1_5.1.14-112924~Ubuntu~wily_amd64.deb ...
Unpacking virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
Processing triggers for systemd (225-1ubuntu9.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for mime-support (3.58ubuntu1) ...
Setting up libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Setting up virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
vboxdrv.sh: failed: modprobe vboxnetflt failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
Processing triggers for libc-bin (2.21-0ubuntu4.1) ...
root@mybox:/etc/apt#

I'm pretty well lost on how to proceed. I'd very much appreciate any guidance.

Thank you.

[socratis]

apt-get install virtualbox-5.1

This command gets the Ubuntu forked version of VirtualBox. Uninstall/purge all current VirtualBox modules and download the one from the official VirtualBox: https://www.virtualbox.org/wiki/Downloads

Otherwise you can ask at the Ubuntu forums, since it's their fork.

[Lappert]

Sorry for the delay in responding - I was tied up at work.

Thank you for your reply.

I understand the issue, but am still having problems. First step is to wipe away the old virtualbox-5.0 and 5.1 (the latter I tried and failed, and as you point out, it was the Ubuntu fork).

Code: Select all

root@mybox:/etc/apt# apt-get remove virtualbox-5.1
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Package 'virtualbox-5.1' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 158 not upgraded.

root@mybox:/etc/apt# apt-get purge virtualbox-5.1
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Package 'virtualbox-5.1' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 158 not upgraded.

Also removed/purged for virtualbox-5.0. However when I use the command "locate virtualbox," I am still getting many lines for virtualbox-5.0 under the directories:
/usr/src/virtualbox-5.0.14/
/var/lib/dkms/virtualbox/5.0.14
/var/lib/dpkg/info/

So I can't say that the system is completely free of VB files. Can I just delete those files?

I also downloaded and sequestered the deb file from virtualbox.org: virtualbox-5.1_5.1.14-112924-Ubuntu-wily_amd64.deb and will try to install that once I'm confident that the old files are gone. More later.

[Lappert]

Attempting to install. First tried Dolphin > QApt Package Installer. Didn't work.

Code: Select all

Preparing to unpack .../virtualbox-5.1_5.1.14-112924-Ubuntu-wily_amd64.deb ...
Setting up virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
Processing triggers for systemd (225-1ubuntu9.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Done

Then attempted to run and I get this popup:

Code: Select all

KDEInit could not launch 'ksystraycmd':
Could not open library '/usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd'.
Cannot load library /usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd: (/usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd.so: cannot open shared object file: No such file or directory)

So I reboot (just in case that's the issue)

Now I remove/purge again, and then try via the command line and dpkg.

Code: Select all

root@mybox:/mnt/sdc/MX/temp2# dpkg -i virtualbox-5.1_5.1.14-112924-Ubuntu-wily_amd64.deb
Selecting previously unselected package virtualbox-5.1.
(Reading database ... 241439 files and directories currently installed.)
Preparing to unpack virtualbox-5.1_5.1.14-112924-Ubuntu-wily_amd64.deb ...
Unpacking virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
Setting up virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
vboxdrv.sh: failed: modprobe vboxnetflt failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
Processing triggers for systemd (225-1ubuntu9.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for mime-support (3.58ubuntu1) ...
root@mybox:/mnt/sdc/MX/temp2#

So this is perplexing at the least. I'll appreciate any insight. Thank you.

[Lappert]

I could sure use some help on this.
Thank you.

[Perryg]

15.10 has reached end of life and you might consider upgrading it. There could be outdated packages that are conflicting.

Post the /var/log/vbox-install.log ( as an attachment )

[Lappert]

Thanks for the reply.

I have planned on upgrading from 15.10 sometime in the future - when I get other things stable and various backups running in place (most via rsync). Last time I did a major upgrade the entire system was lost and nearly lost all data backups, so I'm being slow and cautious.

The old vbox-install.log was too large to be attached (2.7M), so I deleted it (saved it elsewhere) and performed the cycle again: remove, purge, install (see below). The new smaller vbox-install.log (zipped) is attached.

Code: Select all

root@mybox:/mnt/sdc/MX/temp2# apt-get remove virtualbox-5.1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  virtualbox-5.1
0 upgraded, 0 newly installed, 1 to remove and 158 not upgraded.
After this operation, 159 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 242213 files and directories currently installed.)
Removing virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for mime-support (3.58ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...

root@corsair:/mnt/sdc/MX/temp2# apt-get purge virtualbox-5.1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  virtualbox-5.1*
0 upgraded, 0 newly installed, 1 to remove and 158 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 241437 files and directories currently installed.)
Removing virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
Purging configuration files for virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
root@corsair:/mnt/sdc/MX/temp2# dpkg -l virtualbox-5.1
dpkg-query: no packages found matching virtualbox-5.1

root@corsair:/mnt/sdc/MX/temp2# dpkg -i virtualbox-5.1_5.1.14-112924-Ubuntu-wily_amd64.deb 
Selecting previously unselected package virtualbox-5.1.
(Reading database ... 241439 files and directories currently installed.)
Preparing to unpack virtualbox-5.1_5.1.14-112924-Ubuntu-wily_amd64.deb ...
Unpacking virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
Setting up virtualbox-5.1 (5.1.14-112924~Ubuntu~wily) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
vboxdrv.sh: failed: modprobe vboxnetflt failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
Processing triggers for systemd (225-1ubuntu9.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for mime-support (3.58ubuntu1) ...
root@mybox:/mnt/sdc/MX/temp2# 

[Perryg]

modprobe vboxnetflt failed. Please use 'dmesg' to find out why.

So now we have a module that fails and you were directed to use dmesg to find out why. Can you post the results of dmesg after you try to run the "/sbin/vboxconfig" ?

Something is none too happy with the host for some reason and probably a mixture of outdated packages and left over crud.

[Lappert]

Thanks.

I ran /sbin/vboxconfig, then dmesg (no options or parameters)

The log result was over 200K, too large to be attached, so I zipped it and then attached it.

[Perryg]

Code: Select all

[414859.641361] vboxnetflt: disagrees about version of symbol SUPDrvLinuxIDC
[414859.641364] vboxnetflt: Unknown symbol SUPDrvLinuxIDC (err -22)

Problems with the build usually point to gcc or something left over from a previous install.

You might try installing an older version to see if it will build. Purge what you have now though

http://download.virtualbox.org/virtualbox/5.0.30/

[Lappert]

OK, so I removed and purged v5.1.14, and DLed v5.0.30

Code: Select all

root@corsair:/mnt/sdc/MX/temp2# dpkg -i virtualbox-5.0_5.0.30-112061-Ubuntu-wily_amd64.deb 
Selecting previously unselected package virtualbox-5.0.
(Reading database ... 241439 files and directories currently installed.)
Preparing to unpack virtualbox-5.0_5.0.30-112061-Ubuntu-wily_amd64.deb ...
Unpacking virtualbox-5.0 (5.0.30-112061~Ubuntu~wily) ...
Setting up virtualbox-5.0 (5.0.30-112061~Ubuntu~wily) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...done.
Starting VirtualBox kernel modules ...done.
Processing triggers for systemd (225-1ubuntu9.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for mime-support (3.58ubuntu1) ...
root@corsair:/mnt/sdc/MX/temp2# 

So far looks good.

But I try to start it up and get a box that says:

KDEInit could not launch 'ksystraycmd':
Could not open library '/usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd'.
Cannot load library /usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd: (/usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd.so: cannot open shared object file: No such file or directory)

[Perryg]

Drop Cannot load library /usr/lib/x86_64-linux-gnu/libkdeinit5_ksystraycmd in a search engine. It shows what might be causing this issue and what to do. I looks like you are using KDE and something is not right. Kind of what I have been pointing at but could not tell for sure. Some host package is messing with the build.

[Lappert]

Thanks. Making some progress.

I go to Edit Application, Application, Advanced and deselect 'Place in System Tray' and that gets rid of the "...libkdeinit5_ksystraycmd" message.

So now I can start VB, of course with the message that there are newer versions, but for now that's OK.

It open with my existing Win7-32 virtual machine. I hit Start and then I get:

Code: Select all

Failed to open a session for the virtual machine Win7-32.

Implementation of the USB 2.0 controller not found!
Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings.
Note! This error could also mean that an incompatible version of the 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I remember from the last install I had to install an extension pack. So I try to install the extension pack from within VB. File > Preferences > Extensions

And it appears to be successful.

The extension pack is labeled 5.0.30, but I get a popup that it's really 5.0.16. Still it appears to be working.

So as of now, VB appears to be working. Still having issues with connecting my wireless printer/scanner to the program on the VB guest.

So I guess the question is, what's next? I have no compelling reason to upgrade other than the periodic popup reminder. You seem to think the problem might be tied to the old version 15.10 that I have running. Would it likely clear up once I upgrade to 17.04 (when that comes out) or 16.10?

Yes, I'm running KDE (Kubuntu), but that's never been a problem before.

[Perryg]

If it isn't broken, why fix it? I know the newest and best does come into play, but since you are running an out-date OS I would leave it alone until you do upgrade. You can turn the notification to upgrade off in the preference if you like.

[Lappert]

Thank you for your help