Can't start VM (driver mismatches)

systray · Post by **systray** » 19. Feb 2009, 12:57

Hi,

My Logfile:

piripiri190:~/.VirtualBox# cat Machines/Windows/Logs/VBox.log
00:00:00.078 VirtualBox 2.0.6 r39765 linux.x86 (Nov 21 2008 22:09:57) release log
00:00:00.078 Log opened 2009-02-19T09:55:11.229809000Z
00:00:00.078 OS Product: Linux
00:00:00.078 OS Release: 2.6.18-6-amd64
00:00:00.078 OS Version: #1 SMP Sat Dec 27 11:12:41 UTC 2008
00:00:00.078 Package type: LINUX_32BITS_DEBIAN_4_0
00:00:00.082 VRDP: TCP server listening on port 3389.
00:00:00.083 Support driver version mismatch: DriverVersion=too-old ClientVersion=0x90000
00:00:00.083 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={e3c6d4a1-a935-47ca-b16d-f9e9c496e53e} 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:00.083 VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH)} aWarning=false, preserve=false
00:00:00.089 Power up failed (vrc=VERR_VM_DRIVER_VERSION_MISMATCH, hrc=NS_ERROR_FAILURE (0X80004005))
00:00:00.096 VRDP: TCP server closed.
piripiri190:~/.VirtualBox#

uname:

Code: Select all

piripiri190:~/.VirtualBox# uname -a
Linux piripiri190.******** 2.6.18-6-amd64 #1 SMP Sat Dec 27 11:12:41 UTC 2008 x86_64 GNU/Linux

modinfo:

Code: Select all

piripiri190:~/.VirtualBox# modinfo /lib/modules/2.6.18-6-amd64/misc/vboxdrv.ko
filename:       /lib/modules/2.6.18-6-amd64/misc/vboxdrv.ko
author:         Sun Microsystems, Inc.
description:    VirtualBox Support Driver
license:        GPL
version:        2.0.6 (0x00090000)
vermagic:       2.6.18-6-amd64 SMP mod_unload gcc-4.1
depends:
srcversion:     F0E36FAF24C2CB2D5600483
parm:           force_async_tsc:force the asynchronous TSC mode (int)

start command:

Code: Select all

piripiri190:~/.VirtualBox# VBoxVRDP -startvm "Windows"
VirtualBox Headless Interface 2.0.6
(C) 2008 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..
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH)

EDIT: Oh, I've forgot the dmesg. After "modprobe vboxdrv":

Code: Select all

vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Found 1 processor cores.
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 2.0.6 (interface 0x00090000).
ioctl32(VBoxHeadless:8531): Unknown cmd fd(7) cmd(c0305601){00} arg(ffe14a24) on /dev/vboxdrv

Any ideas?
Greetings

Post by **TerryE** » 19. Feb 2009, 13:26

Something's got out of sync. Have you tried to "correct this by stopping all running instances of VirtualBox and reinstalling the software.. " as the message tells you. Whilst you're about it you may as well upgrade to vitualbox-2.1 (2.1.4)

systray · Post by **systray** » 19. Feb 2009, 13:28

TerryE wrote:Something's got out of sync. Have you tried to "correct this by stopping all running instances of VirtualBox and reinstalling the software.. " as the message tells you. Whilst you're about it you may as well upgrade to vitualbox-2.1 (2.1.4)

I had 2.1.4 before, but I had the same message, that's why I installed an older version of VirtualBox.

Greetings.

frarie · Post by **frarie** » 20. Feb 2009, 11:17

I'm experiencing the exact same problem. This is what happened:

1. I tried to upgrade from 2.1.2 to 2.1.4 by feeding yum the RPM.
2. This partially failed as it said that a scriptlet failed while uninstalling an older version.
3. Removed the older version using rpm -e --noscripts.
4. Removed version 2.1.4 as well as it was complaining about missing files.
5. Re-installed 2.1.4 after which I'm experiencing the same problem as systray does.
6. Tried to remove VB again, did a reboot just to be sure, re-installed again. Still the same problem.

I'm using Fedora Core 9 (and corresponding VB packages).

Ps, my uname:
Linux ACLinLap 2.6.27.12-78.2.8.fc9.x86_64 #1 SMP Mon Jan 19 19:25:03 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

frarie · Post by **frarie** » 20. Feb 2009, 11:34

My modinfo:

Code: Select all

filename:       /lib/modules/2.6.27.12-78.2.8.fc9.x86_64/misc/vboxdrv.ko
version:        2.1.4 (0x000a0009)
license:        GPL
description:    VirtualBox Support Driver
author:         Sun Microsystems, Inc.
srcversion:     48EF041BC70601F4A7D8BC4
depends:        
vermagic:       2.6.27.12-78.2.8.fc9.x86_64 SMP mod_unload 
parm:           force_async_tsc:force the asynchronous TSC mode (int)

And the virtual machine's log:

Code: Select all

00:00:00.719 VirtualBox 2.1.4 r42893 linux.x86 (Feb 16 2009 20:51:23) release log
00:00:00.719 Log opened 2009-02-20T08:58:25.140978000Z
00:00:00.719 OS Product: Linux
00:00:00.719 OS Release: 2.6.27.12-78.2.8.fc9.x86_64
00:00:00.719 OS Version: #1 SMP Mon Jan 19 19:25:03 EST 2009
00:00:00.719 Package type: LINUX_32BITS_GENERIC
00:00:00.722 Support driver version mismatch: DriverVersion=too-old ClientVersion=0xa0009
00:00:00.722 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={e3c6d4a1-a935-47ca-b16d-f9e9c496e53e} 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. (VERR_VM_DRIVER_VERSION_MISMATCH)} aWarning=false, preserve=false
00:00:00.745 Power up failed (vrc=VERR_VM_DRIVER_VERSION_MISMATCH, rc=NS_ERROR_FAILURE (0X80004005))

frarie · Post by **frarie** » 20. Feb 2009, 11:57

Tried the following:

Code: Select all

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

Did not help, still the same problem.

frarie · Post by **frarie** » 20. Feb 2009, 12:16

Argh, just found out that I accidentally installed the i386 version in stead of the 64bit one.

Uninstalled, downloaded and installed x86_64 version, running fine.

Ps. although it's entirely my mistake, maybe VB could detect this and give a bit of a more descriptive error message.