#3115 closed defect (fixed)
VirtualBox 2.1.2 installation fails (no symbol version for SUPDrvLinuxIDC) => Fixed in SVN
Reported by: | Volker Bause | Owned by: | |
---|---|---|---|
Component: | installer | Version: | VirtualBox 2.1.2 |
Keywords: | SUPDrvLinuxIDC | Cc: | |
Guest type: | other | Host type: | Linux |
Description (last modified by )
Tried Upgrading, Un-installing and then Re-Installing Virtualbox 2.1.2 on OpenSUSE 11.1 x86_64. Installing VirtualBox 2.1.0 works flawlessly before and after.
The installation is done from KDE4 Terminal using su. I also tried logging in as root which does the same.
De-Installation and Re-Installation is as follows: ================================================== linux-fa23:/setups # rpm -ivh VirtualBox-2.1.2_41885_openSUSE111-1.x86_64.rpm Preparing... ########################################### [100%] 1:VirtualBox ########################################### [100%] Creating group 'vboxusers'. VM users must be member of that group! ..failed
My System Information is as follows:
linux-fa23:/setups # uname -a Linux linux-fa23 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux
Kernel Buffer Ring Reports the following information:
linux-fa23:/setups # dmesg ... vboxdrv: Trying to deactivate the NMI watchdog permanently... vboxdrv: Successfully done. vboxdrv: Found 2 processor cores. VBoxDrv: dbg - g_abExecMemory=ffffffffa043b960 vboxdrv: fAsync=0 offMin=0x276 offMax=0xbb4 vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. vboxdrv: Successfully loaded version 2.1.0 (interface 0x000a0008). vboxdrv: Trying to deactivate the NMI watchdog permanently... vboxdrv: Successfully done. vboxdrv: Found 2 processor cores. VBoxDrv: dbg - g_abExecMemory=ffffffffa043b960 vboxdrv: fAsync=0 offMin=0x245 offMax=0xd97 vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. vboxdrv: Successfully loaded version 2.1.2 (interface 0x000a0009). vboxnetflt: no symbol version for SUPDrvLinuxIDC vboxnetflt: Unknown symbol SUPDrvLinuxIDC
Change History (10)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Description: | modified (diff) |
---|---|
Keywords: | VirtualBox 2.1.2 - critical installation error - no symbol version for removed |
Summary: | VirtualBox 2.1.2 install fails on OpenSUSE 11.1 x86_64 → VirtualBox 2.1.2 installation fails (no symbol version for SUPDrvLinuxIDC) |
comment:3 by , 16 years ago
I am having a similar issue.
Ubuntu 8.04 LTS 2.6.28.2 SMP Tue Jan 27 12:00:18 CST 2009 x86_64 GNU/Linux
After running '/etc/init.d/vboxdrv setup', the process reports:
... Starting VirtualBox kernel module ...failed! (modprobe vboxnetflt failed. Please use 'dmesg' to find out why)
The following messages are in the kernel ring buffer:
[ 4108.931827] vboxdrv: Trying to deactivate the NMI watchdog permanently... [ 4108.931829] vboxdrv: Successfully done. [ 4108.931830] vboxdrv: Found 2 processor cores. [ 4108.931922] VBoxDrv: dbg - g_abExecMemory=ffffffffa0943660 [ 4108.931934] vboxdrv: fAsync=0 offMin=0x178 offMax=0x8f0 [ 4108.931965] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 4108.931967] vboxdrv: Successfully loaded version 2.1.2 (interface 0x000a0009).
(Initially I received the error message regarding no symbol version for SUPDrvLinuxIDC).
comment:4 by , 16 years ago
dturner, the kernel log does not show any problem. What happens if you do
sudo modprobe vboxnetflt
? Which VBox package are you using, I assume the 2.1.2 package for Ubuntu 8.04 (just to make sure)?
comment:5 by , 16 years ago
Summary: | VirtualBox 2.1.2 installation fails (no symbol version for SUPDrvLinuxIDC) → VirtualBox 2.1.2 installation fails (no symbol version for SUPDrvLinuxIDC) => Fixed in SVN |
---|
The openSUSE problem should be fixed definitely. Still waiting for feedback of the Ubuntu problem.
comment:6 by , 16 years ago
The resolution was to reboot and run after the reboot:
etc/init.d/vboxdrv setup
This type of behaviour is not expected for a Linux system. It is also not the behaviour when the packaged installer is used. If it is necessary, it would be helpful to put the step in the README.
comment:7 by , 16 years ago
All this shouldn't be necessary. The file /var/log/vbox-install.log would probably tell us more.
comment:8 by , 16 years ago
Here is the log. (As posted above, a reboot solved the problem and allowed installation of the module).
<contents of /var/log/vbox-install.log>
Attempting to install using DKMS removing old DKMS module vboxdrv version 2.1.2 -------- Uninstall Beginning -------- Module: vboxdrv Version: 2.1.2 Kernel: 2.6.28.2 (x86_64) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/2.6.28.2/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod.... DKMS: uninstall Completed. ------------------------------ Deleting module version: 2.1.2 completely from the DKMS tree. ------------------------------ Done. Creating symlink /var/lib/dkms/vboxdrv/2.1.2/source -> /usr/src/vboxdrv-2.1.2 DKMS: add Completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area.... make KERNELRELEASE=2.6.28.2 -C /lib/modules/2.6.28.2/build M=/var/lib/dkms/vboxdrv/2.1.2/build...... Running the post_build script: cleaning build area.... DKMS: build Completed. Running module version sanity check. vboxdrv.ko: - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.28.2/updates/dkms/ depmod.... DKMS: install Completed. Attempting to install using DKMS removing old DKMS module vboxnetflt version 2.1.2 -------- Uninstall Beginning -------- Module: vboxnetflt Version: 2.1.2 Kernel: 2.6.28.2 (x86_64) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/2.6.28.2/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod.... DKMS: uninstall Completed. ------------------------------ Deleting module version: 2.1.2 completely from the DKMS tree. ------------------------------ Done. Creating symlink /var/lib/dkms/vboxnetflt/2.1.2/source -> /usr/src/vboxnetflt-2.1.2 DKMS: add Completed. Kernel preparation unnecessary for this kernel. Skipping... Running the pre_build script: Building module: cleaning build area.... make KERNELRELEASE=2.6.28.2 -C /lib/modules/2.6.28.2/build M=/var/lib/dkms/vboxnetflt/2.1.2/build...... cleaning build area.... DKMS: build Completed. Running module version sanity check. vboxnetflt.ko: - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.28.2/updates/dkms/ depmod.... DKMS: install Completed.
comment:9 by , 16 years ago
Thanks, but next time please attach the file (there is a Attach button).
Unfortunately, this file contains the log of your last successful recompilation of the modules. If you would like to help to debug this problem you could uninstall (dpkg --purge) the virtualbox-2.1 package again and install it. The original error should show again. The resulting vbox-install.log file would be interesting. Note: Uninstalling the virtualbox-2.1 package would not harm your VMs.
Please execute
This should fix the kernel modules.