Upgrade from 2.1.0 to 2.1.2 vboxdrv issues

[chazsheen]

Here's my scenario:
OpenSuse 11.1 host. Vbox 2.1.0 was installed from binary. Upgraded to 2.1.2 earlier today (tried several times using rpm command-line and Yast). Yast doesn't report errors, but rpm on cli does. Error on install is "Stopping VirtualBox kernel module failed (Cannot unload module vboxdrv)."

Dmesg reveals:
vboxnetflt: no symbol version for SUPDrvLinuxIDC
vboxnetflt: Unknown symbol SUPDrvLinuxIDC

VirtualBox boots, but if I attempt to start a VM I get the following 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).


Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {e3c6d4a1-a935-47ca-b16d-f9e9c496e53e}

I have a feeling it's something fairly simple (deleting links or something) and re-running /etc/init.d/vboxdrv setup, but I'm new to OpenSuse and its software managers. Any help would be greatly appreciated.

[hsch]

Salü

I've the same problem with OpenSuse 11.1

Entry in /var/log/message

Code: Select all

Jan 22 21:59:06 nb-5 shadow[26687]: group already exists - group=vboxusers, by=0
Jan 22 21:59:07 nb-5 kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently...
Jan 22 21:59:07 nb-5 kernel: vboxdrv: Successfully done.
Jan 22 21:59:07 nb-5 kernel: vboxdrv: Found 2 processor cores.
Jan 22 21:59:07 nb-5 kernel: vboxdrv: fAsync=1 offMin=0x11fa62 offMax=0x11fa62
Jan 22 21:59:07 nb-5 kernel: vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'.
Jan 22 21:59:07 nb-5 kernel: vboxdrv: Successfully loaded version 2.1.2 (interface 0x000a0009).
Jan 22 21:59:07 nb-5 kernel: vboxnetflt: no symbol version for SUPDrvLinuxIDC
Jan 22 21:59:07 nb-5 kernel: vboxnetflt: Unknown symbol SUPDrvLinuxIDC

[chazsheen]

Got it.

I uninstalled everything. Rebuilt it from the rpm via command line. Restarted. Rebuilt the vboxdrv via "/etc/init.d/vboxdrv setup" (this time it works). Started the service with "/etc/init.d/vboxdrv start". Then made it permanent on reboot with "insserv vboxdrv"

What ever happened to the days of not having to reboot Linux?

[wilkerj]

Installed 2.11 on openSuse 11.1 via *.rpm. Will not start running as user. Error when trying to start from command line as user:

/usr/bin/VirtualBox: line 72: /usr/lib/virtualbox/VirtualBox: Permission denied
/usr/bin/VirtualBox: line 72: exec: /usr/lib/virtualbox/VirtualBox: cannot execute: Success

user is a member of vboxusers, 2.1.0 worked fine.

Will run as root.

From /var/log/messages:

Jan 22 18:41:46 linux shadow[12637]: group already exists - group=vboxusers, by=0
Jan 22 18:41:47 linux kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently...
Jan 22 18:41:47 linux kernel: vboxdrv: Successfully done.
Jan 22 18:41:47 linux kernel: vboxdrv: Found 2 processor cores.
Jan 22 18:41:47 linux kernel: vboxdrv: fAsync=0 offMin=0x14d offMax=0x7f1
Jan 22 18:41:47 linux kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Jan 22 18:41:47 linux kernel: vboxdrv: Successfully loaded version 2.1.2 (interface 0x000a0009).
Jan 22 18:42:10 linux kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently...
Jan 22 18:42:10 linux kernel: vboxdrv: Successfully done.
Jan 22 18:42:10 linux kernel: vboxdrv: Found 2 processor cores.
Jan 22 18:42:10 linux kernel: vboxdrv: fAsync=0 offMin=0x15f offMax=0x7b8
Jan 22 18:42:10 linux kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Jan 22 18:42:10 linux kernel: vboxdrv: Successfully loaded version 2.1.2 (interface 0x000a0009)

OS Info:

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux linux 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686
Build Date: 03 December 2008 09:21:06AM

[chazsheen]

Give this a shot:

http://vavai.net/2009/01/08/solved-virt ... rmal-user/

[rawswift]

@wilkerj

This is a permission issue and here’s a quick fix:

1. Open YaST
2. Under 'Security and Users' category, click 'User and Group Management'
3. Edit your user profile
4. Click 'Details' tab
5. on 'Additional Groups' frame, check 'root'
6. Click 'Ok' to save

Hope this helps.

[Sasquatch]

@wilkerj

This is a permission issue and here’s a quick fix:

1. Open YaST
2. Under 'Security and Users' category, click 'User and Group Management'
3. Edit your user profile
4. Click 'Details' tab
5. on 'Additional Groups' frame, check 'root'
6. Click 'Ok' to save

Hope this helps.

DON'T DO THIS!!
This will make yourself ROOT, something that goes against the security set in Linux. Windows already made this mistake by making every user Administrator and look what kind of mess came from that.

[trippinnik]

Just ran into the problem. The execute bit is not set right!
Do this:

Code: Select all

sudo chmod +x /usr/lib/virtualbox/VirtualBox

as stated above DO NOT ADD YOURSELF TO THE ROOT GROUP. You should never login to the GUI as root, browse the web as root ... etc.

[wilkerj]

The permissions on /usr/lib/virtualbox/VirtualBox was the prob. I set the execute bit as you suggested and working fine! Thanks so much.

[rawswift]

Oopps! My bad! That was stupid. I should'nt have posted that. Anyway, I tried trippinnik's solution and IT WORK!

Thanks