1.6.4 install funny stuff on Fedora 7

[mic]

Hi, thanks in advance for your help .

Trying to install 1.6.4 from RPM package (VirtualBox-1.6.4_33808_fedora7-1.x86_64.rpm) downloaded off the vbox homepage.

Did as root:

Code: Select all

yum install kernel-headers kernel-devel

Installed package as root via :

Code: Select all

rpm --install VirtualBox-1.6.4_33808_fedora7-1.x86_64.rpm

Getting the following output in /var/log/vbox-install.log:

Code: Select all

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=2.6.21-7.fc7xen -C /lib/modules/2.6.21-7.fc7xen/build M=/var/lib/dkms/vboxdrv/1.6.4/build.......
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.21-7.fc7xen/extra/
Adding any weak-modules

depmod....

DKMS: install Completed.

and

Code: Select all

Stopping VirtualBox kernel module                          [FAILED]
  (Cannot unload module vboxdrv)

adding user via root to vboxusers group:

Code: Select all

usermod -a -G vboxusers mic

Then logging out and back in again.
logging in as root.

Code: Select all

/etc/init.d/vboxdrv setup

results in

Code: Select all

Stopping VirtualBox kernel module                          [FAILED]
  (Cannot unload module vboxdrv)

Information:

installed kernel: 2.6.21-7.fc7xen
on AMD 64 box


I went through this exercise a couple of times, after each time removing any trace of the previous installation.
Each attempt resulted in the same result.

What am I missing? Where did I go wrong? Where else can I dig?

I also searched for answers in the forum, but was not successful in digging up anything that looked promising to me.
If I missed it, apologies, and thanks for any pointers!

mic

[frank]

Please check if the vboxdrv module is actually loaded:

/sbin/lsmod | grep vboxdrv

If so, make sure that no application uses this module. That is, as long as any VirtualBox VM is running, you will not be able to unload this module.

[mic]

Frank,

Code: Select all

# lsmod |grep vboxdrv
vboxdrv              1668691  1

Not sure how to test whether another application uses this module.
Any pointers?
But it's kind of strange that this problem happened after the first install, too.

Thanks!

[mic]

Could this shed more light on what's up:
From dmesg, close to the end

Code: Select all

...
...
Code: 8b 04 25 30 d0 5f ff a8 f0 74 3c c1 e8 10 3c 03 76 35 8b 14 
RIP  [<ffffffff8818c032>] :vboxdrv:VBoxDrvLinuxInit+0x32/0x323
 RSP <ffff8800cc37be28>
CR2: ffffffffff5fd030
...
...

[Sasquatch]

installed kernel: 2.6.21-7.fc7xen

It seems you run your F7 on the Xen kernel. That kernel is not supported by VB. Please install a different kernel so VB can work properly.

This has been mentioned before by one of the devvers (Frank I think, but could be Sander) that VB will not run on Xen kernels. AFAIK, this has not been changed.