Re: Can,t start VirtualBox on F19

Owen Orakwue <orakwueo@xxxxxxx> · Tue, 8 Oct 2013 12:51:57 -0400 (EDT)

I ran the reinstall and it failed the same way :

Total                                           593 kB/s | 9.3 MB     00:16     

Running transaction check

Running transaction test

Transaction test succeeded

Running transaction

  Installing : kernel-devel-3.11.3-201.fc19.x86_64                          1/3 

  Installing : dkms-2.2.0.3-17.fc19.noarch                                  2/3 

  Installing : kernel-headers-3.11.3-201.fc19.x86_64                        3/3 

  Verifying  : dkms-2.2.0.3-17.fc19.noarch                                  1/3 

  Verifying  : kernel-devel-3.11.3-201.fc19.x86_64                          2/3 

  Verifying  : kernel-headers-3.11.3-201.fc19.x86_64                        3/3 

Installed:

  dkms.noarch 0:2.2.0.3-17.fc19           kernel-devel.x86_64 0:3.11.3-201.fc19

  kernel-headers.x86_64 0:3.11.3-201.fc19

Complete!

Stopping VirtualBox kernel modules                         [  OK  ]

Uninstalling old VirtualBox DKMS kernel modules            [  OK  ]

Trying to register the VirtualBox kernel modules using DKMS[  OK  ]

Starting VirtualBox kernel modules                         [FAILED]

  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

[root@localhost owen]# 

[root@localhost owen]# service vboxdrv status && ls -l /lib/modules/3.1*/extra

VirtualBox kernel module is not loaded.

/lib/modules/3.11.2-201.fc19.x86_64/extra:

total 12

drwxr-xr-x. 11 root root 4096 Oct  2 20:44 drivers

drwxr-xr-x. 14 root root 4096 Oct  2 20:44 fs

drwxr-xr-x. 18 root root 4096 Oct  2 20:44 net

/lib/modules/3.11.3-201.fc19.x86_64/extra:

total 512

drwxr-xr-x. 11 root root   4096 Oct  6 22:25 drivers

drwxr-xr-x. 14 root root   4096 Oct  6 22:25 fs

drwxr-xr-x. 18 root root   4096 Oct  6 22:25 netUninstalling modules from DKMS

  removing old DKMS module vboxhost version  4.2.18

-------- Uninstall Beginning --------

Module:  vboxhost

Version: 4.2.18

Kernel:  3.11.3-201.fc19.x86_64 (x86_64)

-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

Removing any linked weak-modules

vboxdrv.ko:

 - Uninstallation

   - Deleting from: /lib/modules/3.11.3-201.fc19.x86_64/extra/

 - Original module

   - No original module was found for this module on this kernel.

   - Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:

 - Uninstallation

   - Deleting from: /lib/modules/3.11.3-201.fc19.x86_64/extra/

 - Original module

   - No original module was found for this module on this kernel.

   - Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:

 - Uninstallation

   - Deleting from: /lib/modules/3.11.3-201.fc19.x86_64/extra/

 - Original module

   - No original module was found for this module on this kernel.

   - Use the dkms install command to reinstall any previous module version.

vboxpci.ko:

 - Uninstallation

   - Deleting from: /lib/modules/3.11.3-201.fc19.x86_64/extra/

 - 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: 4.2.18

completely from the DKMS tree.

------------------------------

Done.

Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxhost/4.2.18/source ->

                 /usr/src/vboxhost-4.2.18

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:

cleaning build area...

make KERNELRELEASE=3.11.3-201.fc19.x86_64 -C /lib/modules/3.11.3-201.fc19.x86_64/build M=/var/lib/dkms/vboxhost/4.2.18/build.........

cleaning build area...

DKMS: build completed.

vboxdrv:

Running module version sanity check.

 - Original module

   - No original module exists within this kernel

 - Installation

   - Installing to /lib/modules/3.11.3-201.fc19.x86_64/extra/

vboxnetflt.ko:

Running module version sanity check.

 - Original module

   - No original module exists within this kernel

 - Installation

   - Installing to /lib/modules/3.11.3-201.fc19.x86_64/extra/

vboxnetadp.ko:

Running module version sanity check.

 - Original module

   - No original module exists within this kernel

 - Installation

   - Installing to /lib/modules/3.11.3-201.fc19.x86_64/extra/

vboxpci.ko:

Running module version sanity check.

 - Original module

   - No original module exists within this kernel

 - Installation

   - Installing to /lib/modules/3.11.3-201.fc19.x86_64/extra/

Adding any weak-modules

depmod...

DKMS: install completed.

-rw-r--r--.  1 root root 423432 Oct  8 12:40 vboxdrv.ko

-rw-r--r--.  1 root root  12736 Oct  8 12:40 vboxnetadp.ko

-rw-r--r--.  1 root root  33080 Oct  8 12:40 vboxnetflt.ko

-rw-r--r--.  1 root root  31072 Oct  8 12:40 vboxpci.ko

[root@localhost owen]# 

cat /var/log/vbox-install.log :

-----Original Message-----

From: Alchemist <raimiiic@xxxxxxxxx>

To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>

Sent: Tue, Oct 8, 2013 12:27 pm

Subject: Re: Can,t start VirtualBox on F19

2013/10/8 Owen Orakwue <orakwueo@xxxxxxx>

Here is the complete error message :

1)

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

2)

[root@localhost init.d]# ./vboxdrv setup

Stopping VirtualBox kernel modules                         [  OK  ]

Uninstalling old VirtualBox DKMS kernel modules            [  OK  ]

Trying to register the VirtualBox kernel modules using DKMS[  OK  ]

Starting VirtualBox kernel modules                         [FAILED]

  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

[root@localhost init.d]# 

3)

When I ran 'dmesg', this is what I saw that is related to virtualbox :

[  169.857137] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)

 -Owen

Run

yum reinstall kernel-devel kernel-headers dkms -y && service vboxdrv setup

to verify

service vboxdrv status && ls -l /lib/modules/3.1*/extra

cat /var/log/vbox-install.log

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org