VERR_VM_DRIVER_VERSION_MISMATCH on start

[jim spurlin]

i have a dell core duo latptop m90 with several version of linux installed.

when i try to start a new/first windows session.

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.. VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).

[root@localhost ~]# find /lib/modules -name vboxdrv*
/lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko
/lib/modules/2.6.22.9-91.fc7/misc/vboxdrv.ko
/lib/modules/2.6.22.7-85.fc7/misc/vboxdrv.ko

[root@localhost ~]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module                          [  OK  ]
Recompiling VirtualBox kernel module                       [  OK  ]
Starting VirtualBox kernel module                          [  OK  ]
[root@localhost ~]# VirtualBox &

 modprobe -l vbox*

/lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko

help? what next or what am i doing wrong?

[Frank Mehnert]

What shows

modinfo /lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko

?

[jim spurlin]

Replying to frank:

What shows

modinfo /lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko

?

[root@localhost ~]# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module [ OK ] Recompiling VirtualBox kernel module [ OK ] Starting VirtualBox kernel module [ OK ]

[root@localhost ~]# modprobe -l vbox* /lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko

[root@localhost ~]# modinfo /lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko filename: /lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko version: 1.5.2 (0x00050002) license: GPL description: VirtualBox Support Driver author: innotek GmbH srcversion: 9C5615A08FF124FEB2BD906 depends: vermagic: 2.6.22.5-76.fc7 SMP mod_unload

[root@localhost ~]# VirtualBox [root@localhost ~]# FAILS as above with below

Result Code: 0x80004005 Component: Console Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

thanks, jim

[Frank Mehnert]

Ok, please, what shows

VBoxManage -v

and

rpm -q -i VirtualBox

Thanks

[jim spurlin]

[root@localhost ~]# VBoxManage -v 1.5.2r25433 [root@localhost ~]# rpm -q -i VirtualBox Name : VirtualBox Relocations: (not relocatable) Version : 1.5.2_25433_fedora7 Vendor: innotek GmbH Release : 1 Build Date: Thu 18 Oct 2007 04:59:48 AM MDT Install Date: Thu 25 Oct 2007 11:04:33 AM MDT Build Host: tinderdeb.intra-innotek.de Group : Applications/System Source RPM: VirtualBox-1.5.2_25433_fedora7-1.src.rpm Size : 37848640 License: VirtualBox Personal Use and Evaluation License (PUEL) Signature : (none) URL : ​http://www.virtualbox.org/ Summary : Powerful PC virtualization solution Description : VirtualBox is a powerful PC virtualization solution allowing you to run a wide range of PC operating systems on your Linux system. This includes Windows, Linux, FreeBSD, DOS, OpenBSD and others. VirtualBox comes with a broad feature set and excellent performance, making it the premier virtualization software solution on the market.

[Frank Mehnert]

Please could you post the VBox.log file for your VM session (main window, menu, Machine => Show Log ...)

Thanks.

[jim spurlin]

Replying to frank:

Please could you post the VBox.log file for your VM session (main window, menu, Machine => Show Log ...)

Thanks.

00:00:03.184 VirtualBox 1.5.2 r25433 linux.x86 (Oct 18 2007 12:54:47) release log 00:00:03.184 Log opened 2007-10-29T18:08:26.072763000Z 00:00:03.186 Support driver version mismatch: DriverVersion=0x0 ClientVersion=0x50002 00:00:03.203 ERROR [COM]: aRC=0x80004005 aIID={1dea5c4b-0753-4193-b909-22330f64ec45} aComponent={Console} aText={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.. 00:00:03.203 VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH)} aPreserve=false 00:00:03.219 Power up failed (vrc=VERR_VM_DRIVER_VERSION_MISMATCH, hrc=0x80004005)

[Frank Mehnert]

Interesting, the driver reports a version of 0. Please could you attach /lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko? Thanks.

[Frank Mehnert]

And please could you do the following as well:

strace -f -o ~/LOG -s256 VirtualBox -startvm <your vm name>

The same error message should appear. Please attach the file ~/LOG here as well. Thanks again.

[Frank Mehnert]

Thanks for the LOG file (I didn't recognize it yesterday because the trac system does not send a notification if an attachment was made). Please could you also attach your vboxdrv.ko module (/lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko)? Thanks.

[Frank Mehnert]

jimspurlin, is it possible that you are running the x86 version of VirtualBox on a Linux kernel which is compiled for AMD64?

[jim spurlin]

i have a dell core2 duo laptop m90. i have 64 bits extensions. but i am certain this is not an amd processor. everything else works fine. how do i check?

[Frank Mehnert]

What is the output of uname -a?

[Frank Mehnert]

I'm quite sure you are running a 64-bit kernel as I saw your kernel module. Please install the 64-bit version of VirtualBox for Fedora7 from our website. You can savely remove the 32-bit version with 'rpm -e VirtualBox'. I will try to add a check to VBox which prevents this trouble in the future.

Can you acknowledge that the 64-bit version is working for you?

[jim spurlin]

uname -a

Linux localhost.localdomain 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

# SUSE Linux Enterprise Server 10 (SLES10) i386 | AMD64 # Fedora 7 ("Moonshine") i386 | AMD64 # Fedora 6 ("Zod") i386

i can only find one version of i386. i do not see any x86_64. i downloaded

VirtualBox-1.5.2_25433_fedora7-1.i586.rpm

[Frank Mehnert]

Please download the AMD64-version (​http://www.virtualbox.org/download/1.5.2/VirtualBox-1.5.2_25433_fedora7-1.x86_64.rpm). AMD64 does not mean that you need an AMD processor but it denotes the CPU architecture AMD invented (in contrast to IA64 by Intel).

[jim spurlin]

yes it mow working. thank for you help and sorry that i did not understand than amd64=x86_64

i tried

VBoxManage internalcommands createrawvmdk -filename /home/jim/fat32x.vmdk -rawdisk /dev/sda -partitions 3 -relative

but when i mounted this under a window guest. had all three partitions as separate devices. with sda3=fat32 mounted correctly but the other ntfs not mounted. i thought that i should only get the third partitions? 1 is dell test and 2 is ntfs windows partition, 3 is fat32.

do i need to mount these under host linux systems first? should i start another ticket?

thanks again.

[Frank Mehnert]

Please open another bug report for your virtual disk problem. Regarding the original problem: We will add more checks to VirtualBox to prevent installing the 32-bit version on 64-bit systems.