kernel driver mismatch

Discussions related to using VirtualBox on Linux hosts.
Post Reply
linuxsupport
Posts: 5
Joined: 10. Jan 2009, 00:23

kernel driver mismatch

Post by linuxsupport »

I am having the kernel driver mismatch problem on an old RHEL4 (32-bit) system. The kernel driver seems to compile and load find. I can run the /etc/init.d/vboxdrv setup, and it has no error, and successfully reloads the module. But each time I try to start a VM I get the kernel mismatch error in a popup box, and this in my syslog:

Code: Select all

Jan  9 17:29:31 meyerpath101-788-657 kernel: ctl32(VirtualBox:10627):   Unknown cmd fd(29) cmd(c0305601){00} arg(ffffb480) on /dev/vboxdrv
Any suggestions as to where I should start? Everything is 32-bit, and the kernel is freshly compiled by the vboxdrv setup, so I'm not sure what could be wrong.

Thanks,
dale
Last edited by linuxsupport on 10. Jan 2009, 04:35, edited 1 time in total.
linuxsupport
Posts: 5
Joined: 10. Jan 2009, 00:23

Post by linuxsupport »

I forgot to give detailed system information. /proc/version:

Code: Select all

Linux version 2.6.9-5.ELsmp (bhcompile@thor.perf.redhat.com) (gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)) #1 SMP Wed Jan 5 19:29:47 EST 2005
# cat /etc/redhat-release

Code: Select all

Red Hat Enterprise Linux WS release 4 (Nahant)
It is a fresh install of the latest VirtualBox 2.1 for Red Hat Enterprise RHEL4, i386, with no previous VirtualBox on the machine.

Would other information be helpful? Could there be something funny with the kernel? It's possible that this is not a stock kernel, but I'm not sure (I did not set up the machines).

Any hints appreciated.
linuxsupport
Posts: 5
Joined: 10. Jan 2009, 00:23

Post by linuxsupport »

...a bit embarrassing, but further digging has shown that it is in fact a 64-bit kernel. Must have had a kernel upgrade, because the above commands do not show the 64-bit-ness. I assume there was not an official 64-bit version of RHEL4, because there does not seem to be a 64-bit version of VirtualBox for RHEL4.

Guess it is time to upgrade my Linux.

Sorry to bother you all.
Post Reply