Page 1 of 1
OEL5.6 - VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm
Posted: 16. May 2012, 07:56
by makwanji
Hi Guru,
I am getting below error while installing VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm into OEL5.6 64bit
Please help
[root@sgerp02 ~]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Removing old VirtualBox pci kernel module [ OK ]
Removing old VirtualBox netadp kernel module [ OK ]
Removing old VirtualBox netflt kernel module [ OK ]
Removing old VirtualBox kernel module [ OK ]
Trying to register the VirtualBox kernel modules using DKMS[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [ OK ]
Starting VirtualBox kernel modules [FAILED]
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Re: OEL5.6 - VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm
Posted: 16. May 2012, 14:55
by Perryg
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Have you done this? What did it say?
Re: OEL5.6 - VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm
Posted: 16. May 2012, 15:04
by makwanji
Hi,
Thanks for your response on this.
Here is the message
bnx2 0000:0b:00.0: irq 72 for MSI/MSI-X
bnx2: eth0: using MSIX
bnx2i: iSCSI not supported, dev=eth0
bnx2: eth0 NIC Copper Link is Up, 100 Mbps full duplex, receive & transmit flow control ON
bnx2i: iSCSI not supported, dev=eth0
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
warning: `dbus-daemon' uses 32-bit capabilities (legacy support in use)
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
mtrr: no more MTRRs available
mtrr: no more MTRRs available
mtrr: no more MTRRs available
mtrr: no more MTRRs available
Slow work thread pool: Starting up
Slow work thread pool: Ready
FS-Cache: Loaded
FS-Cache: Netfs 'nfs' registered for caching
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
[root@sgerp02 ~]#
Re: OEL5.6 - VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm
Posted: 16. May 2012, 15:22
by Perryg
I think that you need to run dmesg right after the failure to be able to see what it was.
More than likely your problem is trying to install VBox for 5.1 in OEL 6
Try with the right download from
HERE
Re: OEL5.6 - VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm
Posted: 16. May 2012, 15:44
by makwanji
Hello,
I just re-try by removing software:
Still getting this error....
[root@sgerp02 ~]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! echo
Your kernel headers for kernel 2.6.32-100.26.2.el5 cannot be found at
/lib/modules/2.6.32-100.26.2.el5/build or /lib/modules/2.6.32-100.26.2.el5/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[root@sgerp02 ~]# cat /var/log/vbox-install.log
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.1.14
------------------------------
Deleting module version: 4.1.14
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.1.14/source ->
/usr/src/vboxhost-4.1.14
DKMS: add completed.
Failed to install using DKMS, attempting to install without
Makefile:172: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
[root@sgerp02 ~]#
Re: OEL5.6 - VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm
Posted: 16. May 2012, 15:53
by Perryg
Your kernel headers for kernel 2.6.32-100.26.2.el5 cannot be found at
/lib/modules/2.6.32-100.26.2.el5/build or /lib/modules/2.6.32-100.26.2.el5/source.
This says it all.
You need to install the headers that match you running kernel.