[Solved] Support driver version mismatch

[ripat]

I am trying to upgrade from 5.0 to 5.1 on a Debian Stretch host but I ran into a "Support driver version mismatch" error when starting a guest machine. The previous version (5.0) was totally purged before installing 5.1.

Code: Select all

00:09:19.787077 Watcher  ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={b2547866-a0a1-4391-8b86-6952d82efaa0} aComponent={MachineWrap} aText={The virtual machine 'Win10' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0
00:09:19.792575 nspr-3   Support driver version mismatch: DriverVersion=0x240000 ClientVersion=0x2a0000 rc=VERR_VERSION_MISMATCH

Installed VB version from the Debian repo's (I have also tried the 5.1 from virtualbox dot org - same error)

Code: Select all

ii  virtualbox-5.1      5.1.26-117224~Debian~str amd64          Oracle VM VirtualBox

lsmod | grep vbox

Code: Select all

vboxpci                24576  0
vboxnetadp             28672  0
vboxnetflt             28672  0
vboxdrv               450560  3 vboxnetadp,vboxnetflt,vboxpci

# modinfo vboxdrv

Code: Select all

filename:       /lib/modules/4.9.0-3-amd64/updates/dkms/vboxdrv.ko
version:        5.0.40 r115130 (0x00240000)
license:        GPL
description:    Oracle VM VirtualBox Support Driver
author:         Oracle Corporation
srcversion:     3AFDBBC6FDA2CE8CF253D33
depends:        
vermagic:       4.9.0-3-amd64 SMP mod_unload modversions 
parm:           force_async_tsc:force the asynchronous TSC mode (int)

systemctl status vbox*

Code: Select all

* vboxdrv.service - VirtualBox Linux kernel module
   Loaded: loaded (/usr/lib/virtualbox/vboxdrv.sh; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2017-08-03 10:47:17 CEST; 19min ago
  Process: 9791 ExecStop=/usr/lib/virtualbox/vboxdrv.sh stop (code=exited, status=0/SUCCESS)
  Process: 10048 ExecStart=/usr/lib/virtualbox/vboxdrv.sh start (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/vboxdrv.service

Aug 03 10:47:17 albin systemd[1]: Starting VirtualBox Linux kernel module...
Aug 03 10:47:17 albin vboxdrv.sh[10048]: vboxdrv.sh: Starting VirtualBox services.
Aug 03 10:47:17 albin systemd[1]: Started VirtualBox Linux kernel module.

* vboxautostart-service.service
   Loaded: loaded (/usr/lib/virtualbox/vboxautostart-service.sh; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2017-08-03 10:27:08 CEST; 39min ago
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/vboxautostart-service.service

Aug 03 10:27:08 albin systemd[1]: Starting vboxautostart-service.service...
Aug 03 10:27:08 albin systemd[1]: Started vboxautostart-service.service.

* vboxballoonctrl-service.service
   Loaded: loaded (/usr/lib/virtualbox/vboxballoonctrl-service.sh; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2017-08-03 10:27:08 CEST; 39min ago
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/vboxballoonctrl-service.service

Aug 03 10:27:08 albin systemd[1]: Starting vboxballoonctrl-service.service...
Aug 03 10:27:08 albin systemd[1]: Started vboxballoonctrl-service.service.

* vboxweb-service.service
   Loaded: loaded (/usr/lib/virtualbox/vboxweb-service.sh; enabled; vendor preset: enabled)

[socratis]

The previous version (5.0) was totally purged before installing 5.1.

I'm not so sure about that...

According to the error:

00:09:19.792575 nspr-3   Support driver version mismatch: DriverVersion=0x240000 ClientVersion=0x2a0000 rc=VERR_VERSION_MISMATCH

And then you have your VirtualBox version:

ii  virtualbox-5.1      5.1.26-117224~Debian~str amd64          Oracle VM VirtualBox

and your driver version:

filename:       /lib/modules/4.9.0-3-amd64/updates/dkms/vboxdrv.ko
version:        5.0.40 r115130 (0x00240000)

Try to clean the system again. And please use only the official VirtualBox installation, if you'd like support in these forums.

[ripat]

You are right. The vboxdrv module loaded in the kernel by dkms is an old version (5.0.40 r115130). I just copied the new one supplied from the deb package (5.1.26 r117224) to the /lib/modules/4.9.0-3-amd64/updates/dkms/ directory the and everything was up and running again.

Thanks.

BTW how can I re-register a module in dkms in order to point to an updated version of it?

[socratis]

Great, thanks for the feedback. I marked the thread as [Solved].