Can,t start VirtualBox on F19

[Owen Orakwue]

I am getting the error message below on a Fredora 19 system when attempt to start VirualBox 
Any help will be greatly appreciated :

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.

Thanks.
-Owen

[Reindl Harald]

Am 08.10.2013 16:36, schrieb Owen Orakwue:
> I am getting the error message below on a Fredora 19 system when attempt to start VirualBox
> Any help will be greatly appreciated:
>
> 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'

you did *not* mention if you followed the advise
type "/etc/init.d/vboxdrv setup" in a root terminal

[Owen Orakwue]

I did and it complained that "modprobe vboxdrv" failed. 
And verified that 'vboxdrv' is not in /dev.

-Owen

-----Original Message-----
From: Reindl Harald 
To: Community support for Fedora users ; orakwueo 
Sent: Tue, Oct 8, 2013 10:38 am
Subject: Re: Can,t start VirtualBox on F19

Am 08.10.2013 16:36, schrieb Owen Orakwue:
> I am getting the error message below on a Fredora 19 system when attempt to

start VirualBox
> Any help will be greatly appreciated:
>
> 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'

you did *not* mention if you followed the advise
type "/etc/init.d/vboxdrv setup" in a root terminal

[Reindl Harald]

please do not top-post and use HTML on mailing-lists

Am 08.10.2013 16:55, schrieb Owen Orakwue:
> -----Original Message-----
> From: Reindl Harald 
> To: Community support for Fedora users ; orakwueo 
> Sent: Tue, Oct 8, 2013 10:38 am
> Subject: Re: Can,t start VirtualBox on F19
>
> Am 08.10.2013 16:36, schrieb Owen Orakwue:
> > I am getting the error message below on a Fredora 19 system when attempt to
>
> start VirualBox
> > Any help will be greatly appreciated:
> >
> > 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'
>
> you did *not* mention if you followed the advise
> type "/etc/init.d/vboxdrv setup" in a root terminal
>
> I did and it complained that |"modprobe vboxdrv" failed.
> And verified that 'vboxdrv' is not in /dev

* which vbox version
* package from rpmfusion or upstream

most likely build of the kernel-module failed because too new kernel

[Owen Orakwue]

lI installed VirtualBox-4.2-4.2.18_88780_fedora18-1.x86_64.rpm.
I tried the rpm from Oracle and the one from Virtualbox.org
-Owen

-----Original Message-----
From: Reindl Harald 
To: Owen Orakwue ; users 
Sent: Tue, Oct 8, 2013 10:58 am
Subject: Re: Can,t start VirtualBox on F19

please do not top-post and use HTML on mailing-lists

Am 08.10.2013 16:55, schrieb Owen Orakwue:
> -----Original Message-----
> From: Reindl Harald 
> To: Community support for Fedora users ;

orakwueo
> Sent: Tue, Oct 8, 2013 10:38 am
> Subject: Re: Can,t start VirtualBox on F19
>
> Am 08.10.2013 16:36, schrieb Owen Orakwue:
> > I am getting the error message below on a Fredora 19 system when attempt to
>
> start VirualBox
> > Any help will be greatly appreciated:
> >
> > 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'
>
> you did *not* mention if you followed the advise
> type "/etc/init.d/vboxdrv setup" in a root terminal
>
> I did and it complained that |"modprobe vboxdrv" failed.
> And verified that 'vboxdrv' is not in /dev

* which vbox version
* package from rpmfusion or upstream

most likely build of the kernel-module failed because too new kernel

[Carlos "casep" Sepulveda]

On 8 October 2013 12:13, Owen Orakwue  wrote:
> lI installed VirtualBox-4.2-4.2.18_88780_fedora18-1.x86_64.rpm.
> I tried the rpm from Oracle and the one from Virtualbox.org
> -Owen

You better enable the rpmfusion repo and the install both the
kmod-VirtualBox and VirtualBox using yum.
That should be a lot easier tha installing single rpms.

Regards

[SternData]

On 10/08/2013 10:33 AM, Carlos "casep" Sepulveda wrote:
> On 8 October 2013 12:13, Owen Orakwue  wrote:
> > lI installed VirtualBox-4.2-4.2.18_88780_fedora18-1.x86_64.rpm.
> > I tried the rpm from Oracle and the one from Virtualbox.org
> > -Owen
>
> You better enable the rpmfusion repo and the install both the
> kmod-VirtualBox and VirtualBox using yum.
> That should be a lot easier tha installing single rpms.
>
> Regards

Mixing the repos is a sure way to frack things up.  I'm using only the
virtualbox.org repos and it works just fine.

[SternData]

On 10/08/2013 09:55 AM, Owen Orakwue wrote:
> I did and it complained that |"modprobe vboxdrv" failed.
> And verified that 'vboxdrv' is not in /dev.
>
> -Owen
> |
>
> -----Original Message-----
> From: Reindl Harald 
> To: Community support for Fedora users ;
> orakwueo 
> Sent: Tue, Oct 8, 2013 10:38 am
> Subject: Re: Can,t start VirtualBox on F19
>
> Am 08.10.2013 16:36, schrieb Owen Orakwue:
> > I am getting the error message below on a Fredora 19 system when attempt to
>
> start VirualBox
> > Any help will be greatly appreciated:
> >
> > 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'
>
> you did *not* mention if you followed the advise
> type "/etc/init.d/vboxdrv setup" in a root terminal

Have you installed DKMS?

[Owen Orakwue]

Yes, I installed DKMS before I ran '/etc/vboxdrv setup'.
-Owen

-----Original Message-----
From: Steven Stern 
To: Community support for Fedora users 
Sent: Tue, Oct 8, 2013 11:07 am
Subject: Re: Can,t start VirtualBox on F19

On 10/08/2013 09:55 AM, Owen Orakwue wrote:
> I did and it complained that |"modprobe vboxdrv" failed.
> And verified that 'vboxdrv' is not in /dev.
>
> -Owen
> |
>
> -----Original Message-----
> From: Reindl Harald 
> To: Community support for Fedora users ;
> orakwueo 
> Sent: Tue, Oct 8, 2013 10:38 am
> Subject: Re: Can,t start VirtualBox on F19
>
> Am 08.10.2013 16:36, schrieb Owen Orakwue:
> > I am getting the error message below on a Fredora 19 system when attempt to
>
> start VirualBox
> > Any help will be greatly appreciated:
> >
> > 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'
>
> you did *not* mention if you followed the advise
> type "/etc/init.d/vboxdrv setup" in a root terminal

Have you installed DKMS?

[Carlos "casep" Sepulveda]

On 8 October 2013 11:36, Owen Orakwue  wrote:
> '/etc/init.d/vboxdrv setup'

Hi:
Did you ran the
/etc/init.d/vboxdrv setup
script as root?

[Owen Orakwue]

..yes I did.
-Owen

-----Original Message-----
From: Carlos "casep" Sepulveda 
To: Community support for Fedora users 
Sent: Tue, Oct 8, 2013 10:41 am
Subject: Re: Can,t start VirtualBox on F19

On 8 October 2013 11:36, Owen Orakwue  wrote:
> '/etc/init.d/vboxdrv setup'

Hi:
Did you ran the
/etc/init.d/vboxdrv setup
script as root?

[Carlos "casep" Sepulveda]

And what's the complete error ?
Looks like you don't have the kernel-headers / devel packeges so the
module isn't being properly compiled.... we need the complete log to
confirm it.

On 8 October 2013 11:56, Owen Orakwue  wrote:
> ..yes I did.
> -Owen
>
> -----Original Message-----
> From: Carlos "casep" Sepulveda 
> To: Community support for Fedora users 
> Sent: Tue, Oct 8, 2013 10:41 am
> Subject: Re: Can,t start VirtualBox on F19
>
> On 8 October 2013 11:36, Owen Orakwue  wrote:
> > '/etc/init.d/vboxdrv setup'
>
> Hi:
> Did you ran the
> /etc/init.d/vboxdrv setup
> script as root?
>
> --
> "My name is Ozymandias, king of kings:
> Look on my works, ye Mighty, and despair!"
> Percy Bysshe Shelley
> http://sites.google.com/site/carlossepulveda
> --
> users mailing list
> [e-mail]
> 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

[Owen Orakwue]

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

-----Original Message-----
From: Carlos "casep" Sepulveda 
To: Owen Orakwue 
Cc: Community support for Fedora users 
Sent: Tue, Oct 8, 2013 11:04 am
Subject: Re: Can,t start VirtualBox on F19

And what's the complete error ?
Looks like you don't have the kernel-headers / devel packeges so the
module isn't being properly compiled.... we need the complete log to
confirm it.

On 8 October 2013 11:56, Owen Orakwue  wrote:
> ..yes I did.
> -Owen
>
> -----Original Message-----
> From: Carlos "casep" Sepulveda 
> To: Community support for Fedora users 
> Sent: Tue, Oct 8, 2013 10:41 am
> Subject: Re: Can,t start VirtualBox on F19
>
> On 8 October 2013 11:36, Owen Orakwue  wrote:
> > '/etc/init.d/vboxdrv setup'
>
> Hi:
> Did you ran the
> /etc/init.d/vboxdrv setup
> script as root?
>
> --
> "My name is Ozymandias, king of kings:
> Look on my works, ye Mighty, and despair!"
> Percy Bysshe Shelley
> http://sites.google.com/site/carlossepulveda
> --
> users mailing list
> [e-mail]
> 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

[Alchemist]

2013/10/8 Owen Orakwue
> Here is the complete error message :
>
> 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.
>
> [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]#
>
> 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

[Owen Orakwue]

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 
To: Community support for Fedora users 
Sent: Tue, Oct 8, 2013 12:27 pm
Subject: Re: Can,t start VirtualBox on F19

2013/10/8 Owen Orakwue

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

[Alchemist]

2013/10/8 Owen Orakwue
> 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]#

As we see modules successfully compiled.
Try systemctl status dkms.service && systemctl restart dkms.service ||
systemctl start dkms.service

and then service vboxdrv setup

[Owen Orakwue]

I tried it and still got the same failure. Thanks.

[root@localhost owen]# systemctl status dkms.service && systemctl restart dkms.service
dkms_autoinstaller.service - LSB: DKMS kernel modules installer service
   Loaded: loaded (/etc/rc.d/init.d/dkms_autoinstaller)
   Active: active (exited) since Tue 2013-10-08 17:04:02 EDT; 7min ago
  Process: 591 ExecStart=/etc/rc.d/init.d/dkms_autoinstaller start (code=exited, status=0/SUCCESS)

[root@localhost owen]# service 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 owen]#

-Owen

-----Original Message-----
From: Alchemist 
To: Community support for Fedora users 
Sent: Tue, Oct 8, 2013 12:59 pm
Subject: Re: Can,t start VirtualBox on F19

2013/10/8 Owen Orakwue

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]#

As we see modules successfully compiled.

Try systemctl status dkms.service && systemctl restart dkms.service || systemctl start dkms.service

and then service vboxdrv setup

[Alchemist]

2013/10/9 Owen Orakwue
> I tried it and still got the same failure. Thanks.
>
> [root@localhost owen]# systemctl status dkms.service && systemctl restart
> dkms.service
> dkms_autoinstaller.service - LSB: DKMS kernel modules installer service
>    Loaded: loaded (/etc/rc.d/init.d/dkms_autoinstaller)
>    Active: active (exited) since Tue 2013-10-08 17:04:02 EDT; 7min ago
>   Process: 591 ExecStart=/etc/rc.d/init.d/dkms_autoinstaller start
> (code=exited, status=0/SUCCESS)
>
> [root@localhost owen]# service 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 owen]#
>
> -Owen
>
> Well, problem is about loading module. Try to manually load theese

modprobe -v vboxdrv && modprobe -v vboxnetadp && modprobe -v vboxnetflt &&
modprobe -v vboxpci

[Owen Orakwue]

Manuall loading failed :

[root@localhost owen]# modprobe -v vboxdrv && modprobe -v vboxnetadp && modprobe -v vboxnetflt && modprobe -v vboxpci
insmod /lib/modules/3.11.3-201.fc19.x86_64/extra/vboxdrv.ko 
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
[root@localhost owen]#

-Owen

-----Original Message-----
From: Alchemist 
To: Community support for Fedora users 
Sent: Tue, Oct 8, 2013 5:39 pm
Subject: Re: Can,t start VirtualBox on F19

2013/10/9 Owen Orakwue

I tried it and still got the same failure. Thanks.

[root@localhost owen]# systemctl status dkms.service && systemctl restart dkms.service
dkms_autoinstaller.service - LSB: DKMS kernel modules installer service
   Loaded: loaded (/etc/rc.d/init.d/dkms_autoinstaller)
   Active: active (exited) since Tue 2013-10-08 17:04:02 EDT; 7min ago
  Process: 591 ExecStart=/etc/rc.d/init.d/dkms_autoinstaller start (code=exited, status=0/SUCCESS)

[root@localhost owen]# service 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 owen]#

-Owen

Well, problem is about loading module. Try to manually load theese

modprobe -v vboxdrv && modprobe -v vboxnetadp && modprobe -v vboxnetflt && modprobe -v vboxpci

[Ed Greshko]

On 10/09/13 07:28, Owen Orakwue wrote:
> Manuall loading failed :
>
> [root@localhost owen]# modprobe -v vboxdrv && modprobe -v vboxnetadp && modprobe -v vboxnetflt && modprobe -v vboxpci
> insmod /lib/modules/3.11.3-201.fc19.x86_64/extra/vboxdrv.ko
> modprobe: ERROR: could not insert 'vboxdrv': Required key not available
> [root@localhost owen]#

Are you using "UEFI Secure Boot" on your system?

[Alchemist]

2013/10/9 Owen Orakwue

Manuall loading failed :
> [root@localhost owen]# modprobe -v vboxdrv && modprobe -v vboxnetadp &&
> modprobe -v vboxnetflt && modprobe -v vboxpci
> insmod /lib/modules/3.11.3-201.fc19.x86_64/extra/vboxdrv.ko
> modprobe: ERROR: could not insert 'vboxdrv': Required key not available
> [root@localhost owen]#
>
> -Owen
>
> Wow. Are you using Secboot? Looks, so modprobe will not be able to load unsigned

Oracle's modules.

[Owen Orakwue]

How can I tell if I am using secure boot...I never explicitly chose it at install.
-Owen
> On Oct 8, 2013, at 7:44 PM, Alchemist  wrote:
>
> 2013/10/9 Owen Orakwue
> > Manuall loading failed :
> >
> > [root@localhost owen]# modprobe -v vboxdrv && modprobe -v vboxnetadp && modprobe -v vboxnetflt && modprobe -v vboxpci
> > insmod /lib/modules/3.11.3-201.fc19.x86_64/extra/vboxdrv.ko 
> > modprobe: ERROR: could not insert 'vboxdrv': Required key not available
> > [root@localhost owen]#
> >
> > -Owen
> Wow. Are you using Secboot? Looks, so modprobe will not be able to load unsigned Oracle's modules.
>
> users mailing list
> [e-mail]
> 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

[Alchemist]

2013/10/9 Owen Orakwue
> How can I tell if I am using secure boot...I never explicitly chose it at
> install.
> -Owen
>
> On Oct 8, 2013, at 7:44 PM, Alchemist  wrote:
>
> 2013/10/9 Owen Orakwue
>
> Manuall loading failed :
> > [root@localhost owen]# modprobe -v vboxdrv && modprobe -v vboxnetadp &&
> > modprobe -v vboxnetflt && modprobe -v vboxpci
> > insmod /lib/modules/3.11.3-201.fc19.x86_64/extra/vboxdrv.ko
> > modprobe: ERROR: could not insert 'vboxdrv': Required key not available
> > [root@localhost owen]#
> >
> > -Owen
> >
> > Wow. Are you using Secboot? Looks, so modprobe will not be able to load unsigned
>
> Oracle's modules.
>
> --
> users mailing list
> [e-mail]
> 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

Check BIOS option to disable it or if Win8 is pre-installed in dual boot?
Then you have to choose.
Good resources
http://www.rodsbooks.com/efi-bootloaders/secureboot.html
https://docs.fedoraproject.org/en-US/Fedora/18/html-single/UEFI_Secure_Boot_...

[Owen Orakwue]

Thanks everyone...disabling secure boot fixed it.
-Owen

-----Original Message-----
From: Alchemist 
To: Community support for Fedora users 
Sent: Wed, Oct 9, 2013 10:46 am
Subject: Re: Can,t start VirtualBox on F19

2013/10/9 Owen Orakwue

How can I tell if I am using secure boot...I never explicitly chose it at install.
-Owen

On Oct 8, 2013, at 7:44 PM, Alchemist  wrote:

2013/10/9 Owen Orakwue

Manuall loading failed :

[root@localhost owen]# modprobe -v vboxdrv && modprobe -v vboxnetadp && modprobe -v vboxnetflt && modprobe -v vboxpci
insmod /lib/modules/3.11.3-201.fc19.x86_64/extra/vboxdrv.ko 
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
[root@localhost owen]#

-Owen

Wow. Are you using Secboot? Looks, so modprobe will not be able to load unsigned Oracle's modules.

[Reindl Harald]

Am 08.10.2013 23:16, schrieb Owen Orakwue:
> I tried it and still got the same failure. Thanks.
>
> [root@localhost owen]# systemctl status dkms.service && systemctl restart dkms.service
> dkms_autoinstaller.service - LSB: DKMS kernel modules installer service
>    Loaded: loaded (/etc/rc.d/init.d/dkms_autoinstaller)
>    Active: active (exited) since Tue 2013-10-08 17:04:02 EDT; 7min ago
>   Process: 591 ExecStart=/etc/rc.d/init.d/dkms_autoinstaller start (code=exited, status=0/SUCCESS)
>
> [root@localhost owen]# service 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 owen]#

why don't you ever what output of errors suggest and post the
results too -> "Please use 'dmesg' to find out why"?

[SternData]

On 10/08/2013 11:16 AM, Owen Orakwue wrote:
> Here is the complete error message :
>
> 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.
>
> [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]#
>
> 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
>
> -----Original Message-----
> From: Carlos "casep" Sepulveda 
> To: Owen Orakwue 
> Cc: Community support for Fedora users 
> Sent: Tue, Oct 8, 2013 11:04 am
> Subject: Re: Can,t start VirtualBox on F19
>
> And what's the complete error ?
> Looks like you don't have the kernel-headers / devel packeges so the
> module isn't being properly compiled.... we need the complete log to
> confirm it.
>
> On 8 October 2013 11:56, Owen Orakwue <[e-mail] > wrote:
> > ..yes I did.
> > -Owen
> >
> > -----Original Message-----
> > From: Carlos "casep" Sepulveda <[e-mail] >
> > To: Community support for Fedora users <[e-mail] >
> > Sent: Tue, Oct 8, 2013 10:41 am
> > Subject: Re: Can,t start VirtualBox on F19
> >
> > On 8 October 2013 11:36, Owen Orakwue <[e-mail] > wrote:
> > > '/etc/init.d/vboxdrv setup'
> >
> > Hi:
> > Did you ran the
> > /etc/init.d/vboxdrv setup
> > script as root?
> >
> > --
> > "My name is Ozymandias, king of kings:
> > Look on my works, ye Mighty, and despair!"
> > Percy Bysshe Shelley
> > http://sites.google.com/site/carlossepulveda
> > --
> > users mailing list
> > [e-mail] 
> > 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

Make sure you are in the vboxusers user group.  Edit /etc/group and put
your ID there. For example:

vboxusers:x:1001:sdstern

You may have to logout/login after doing so to get the change picked up.

[Owen Orakwue]

I added

vboxusers:x:1001:owen to /etc/group and it still failed.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)

Thanks.
-Owen

-----Origvboxusers:x:1001:oweninal Message-----
From: Steven Stern 
To: Community support for Fedora users 
Sent: Tue, Oct 8, 2013 12:50 pm
Subject: Re: Can,t start VirtualBox on F19

On 10/08/2013 11:16 AM, Owen Orakwue wrote:
> Here is the complete error message :
>
> 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.
>
> [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]#
>
> 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
>
> -----Original Message-----
> From: Carlos "casep" Sepulveda 
> To: Owen Orakwue 
> Cc: Community support for Fedora users 
> Sent: Tue, Oct 8, 2013 11:04 am
> Subject: Re: Can,t start VirtualBox on F19
>
> And what's the complete error ?
> Looks like you don't have the kernel-headers / devel packeges so the
> module isn't being properly compiled.... we need the complete log to
> confirm it.
>
> On 8 October 2013 11:56, Owen Orakwue <[e-mail] >

wrote:
> > ..yes I did.
> > -Owen
> >
> > -----Original Message-----
> > From: Carlos "casep" Sepulveda <[e-mail] >
> > To: Community support for Fedora users <[e-mail]

>
> > Sent: Tue, Oct 8, 2013 10:41 am
> > Subject: Re: Can,t start VirtualBox on F19
> >
> > On 8 October 2013 11:36, Owen Orakwue <[e-mail] >

wrote:
> > > '/etc/init.d/vboxdrv setup'
> >
> > Hi:
> > Did you ran the
> > /etc/init.d/vboxdrv setup
> > script as root?
> >
> > --
> > "My name is Ozymandias, king of kings:
> > Look on my works, ye Mighty, and despair!"
> > Percy Bysshe Shelley
> > http://sites.google.com/site/carlossepulveda
> > --
> > users mailing list
> > [e-mail] 
> > 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

Make sure you are in the vboxusers user group.  Edit /etc/group and put
your ID there. For example:

vboxusers:x:1001:sdstern

You may have to logout/login after doing so to get the change picked up.

[SternData]

On 10/08/2013 04:32 PM, Owen Orakwue wrote:
> I added
> vboxusers:x:1001:owen to /etc/group and it still failed.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)

No, no, no.  There should have been a vboxusers group in your group file.

If you added one manually, take it out.