VERR_VM_DRIVER_VERSION_MISMATCH on SuSE 11.1 [again !]

[opensuse-717]

This nerve-racking problem had tormented me with the 2.1.2 installation [see previous post of mine]. It had disappeared without me having done anything - it just "decided" to go away one day that I checked.

Unfortunately, right after I upgraded to VirtualBox 2.1.4 and here we are again:

Code: Select all

mimis-10.0@bwv988:~$ VBoxVRDP -startvm "XP.flash-16"
VirtualBox Headless Interface 2.1.4
(C) 2008-2009 Sun Microsystems, Inc.
All rights reserved.

Listening on port 3389
Error: failed to start machine. Error message: The VirtualBox support driver which is running is from a different version of VirtualBox.  You can correct this by stopping all running instances of VirtualBox and reinstalling the software. (VERR_VM_DRIVER_VERSION_MISMATCH)

system data

Code: Select all

mimis-10.0@bwv988:~$ uname -a
Linux bwv988 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux

kernel driver information

Code: Select all

mimis-10.0@bwv988:~$ /sbin/modinfo vboxdrv
filename:       /lib/modules/2.6.27.7-9-default/misc/vboxdrv.ko
version:        2.1.4 (0x000a0009)
license:        GPL
description:    VirtualBox Support Driver
author:         Sun Microsystems, Inc.
srcversion:     48EF041BC70601F4A7D8BC4
depends:        built-in,built-in,built-in,built-in,built-in,built-in,built-in,built-in,built-in
vermagic:       2.6.27.7-9-default SMP mod_unload modversions
parm:           force_async_tsc:force the asynchronous TSC mode (int)

and,

Code: Select all

bwv988:/etc/init.d # modinfo vboxnetflt
filename:       /lib/modules/2.6.27.7-9-default/misc/vboxnetflt.ko
version:        2.1.4 ((0xA2CDe001U))
license:        GPL
description:    VirtualBox Network Filter Driver
author:         Sun Microsystems, Inc.
srcversion:     B631657B96291A70E2BE2E8
depends:        built-in,built-in,built-in,built-in,built-in,built-in,built-in,built-in,built-in,vboxdrv
vermagic:       2.6.27.7-9-default SMP mod_unload modversions

VirtualBox version information

Code: Select all

mimis-10.0@bwv988:~$ rpm -q --whatprovides VirtualBox
VirtualBox-2.1.4_42893_openSUSE111-1

I am at a loss!
where should I be looking into - any ideas? - is it the same with all SuSE users?

mimis

[mkolts@civil.auth.gr]

Code: Select all

Code: Select all

[mehall]

I have not had any problems with VBoxHeadless running on SuSE 11.1 x86_64, with either VB 2.1.2 or 2.1.4, so apparently it is not a generic SuSE 11.1 problem. Unfortunately, I don't have any ideas on what it might be.

[Sasquatch]

Close VB, make sure no other process is running of it (like vboxsvc), then remove VB with it's config (VMs will be kept) then install it again.

[opensuse-717]

Trying what you suggested:

deleted package with yast
run updatedb afresh
made sure that vbox remnants did not exist anywhere but /usr/share/doc
checked for traces of "*vbox*" in /lib/modules with "find"
installed the VirtualBox-2.1.4_42893_openSUSE111-1.i586.rpm via yast
compiled the kernel driver (/etc/init.d/vboxdrv setup)
made sure that all *vbox* modules in /lib/modules share the 2.1.4 version

!!! problem persists !!!

any ideas?

mimis koltsakis

[Sasquatch]

Did you also make sure that there are no remains in /var/lib/dkms? You might want to remove all those modules, and run the vboxdrv setup command manually.

[frarie]

Are you sure you want to use the 32 bits version (i586) on your 64bit kernel? If your previous version of VB was the 64bit one, I think you should upgrade using the x86_64 version.

At least that's what I did wrong and I got the same error message as you did (on Fedore 9 64bit).

[opensuse-717]

thank you, thank you, it was so simple!

I was misled by the tagging of the rpm's in download-for-linux page:

they give you two options: i586 and AMD64 - it is not straightforward that you need the AMD64 for an x86_64 system because AMD is a brand of microprocessors and my PC uses Intel. It may be silly of me but I chose the i586 as the thought occured to me that installing something specific for AMD might be unwise!

Anyway, it runs perfect, at least at first glance!

mimis

[Sasquatch]

It's called AMD64 because AMD was the first processor for consumers that had 64 bit capabilities. Intel had their own, but only for Servers (the Itanium series). For the consumers, they used the AMD instruction set, for better support with programs. Thus packages are called AMD64 by default.