Virtual Box not loading vboxdrv on Clean install of Fedora 31

[Michael D. Setzer II]

Setting up a new system with Fedora 31, but run into a problem with 
VirtualBox
On running Virtual Box I get this message??

WARNING: The vboxdrv kernel module is not loaded. Either there is no 
module
         available for the current kernel (5.5.13-200.fc31.x86_64) or it failed to
         load. Please try load the kernel module by executing as root

dnf install akmod-VirtualBox kernel-devel-5.5.13-200.fc31.x86_64
           akmods --kernels 5.5.13-200.fc31.x86_64 && systemctl restart 
systemd-modules-load.service

You will not be able to start VMs until this problem is fixed.

I do the recommended options.
dnf packages are already installed
The akmods builds the moduals, and they are in the location
But restarting the systemd-modules-load results in error.

Running what it recommends for getting results with this, but can't find any 
recommendations??
On exact same machine with Fedora 29, this was working. This is a clean 
install on a new hard disk.
Any ideals?

● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; 
static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2020-04-05 00:49:35 ChST; 25s 
ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 196212 ExecStart=/usr/lib/systemd/systemd-modules-load 
(code=exited, status=1/FAILURE)
 Main PID: 196212 (code=exited, status=1/FAILURE)
      CPU: 23ms

Apr 05 00:49:35 localhost.localdomain systemd[1]: Starting Load Kernel 
Modules...
Apr 05 00:49:35 localhost.localdomain systemd[1]: 
systemd-modules-load.service: Main process exited, code=exited, 
status=1/FAILURE
Apr 05 00:49:35 localhost.localdomain systemd[1]: 
systemd-modules-load.service: Failed with result 'exit-code'.
Apr 05 00:49:35 localhost.localdomain systemd[1]: Failed to start Load 
Kernel Modules.

Hi

On Sun, 05 Apr 2020 01:12:04 +1000 "Michael D. Setzer II via users" wrote:
> On running Virtual Box I get this message??
> WARNING: The vboxdrv kernel module is not loaded. Either there is no
> module available for the current kernel (5.5.13-200.fc31.x86_64) or
> it failed to load. Please try load the kernel module by executing as
> root
> dnf install akmod-VirtualBox kernel-devel-5.5.13-200.fc31.x86_64
> akmods --kernels 5.5.13-200.fc31.x86_64 && systemctl restart > systemd-modules-load.service
> I do the recommended options.
> dnf packages are already installed
> The akmods builds the moduals, and they are in the location
> But restarting the systemd-modules-load results in error.

Does a simple "modprobe vboxdrv" also fails ?

What gives: modinfo vboxdrv

Also, double check that the modules have been build with:

dnf list installed kmod-VirtualBox*
> On exact same machine with Fedora 29, this was working. This is a clean
> install on a new hard disk.
> Any ideals?

With Fedora 31 you have newer kernels: the Virtualbox sources may
become incompatile with them.

[Michael D. Setzer II]

> Hi
>
> On Sun, 05 Apr 2020 01:12:04 +1000 "Michael D. Setzer II via users" wrote:
> > On running Virtual Box I get this message??
> > WARNING: The vboxdrv kernel module is not loaded. Either there is no
> > module available for the current kernel (5.5.13-200.fc31.x86_64) or
> > it failed to load. Please try load the kernel module by executing as
> > root
> > dnf install akmod-VirtualBox kernel-devel-5.5.13-200.fc31.x86_64
> > akmods --kernels 5.5.13-200.fc31.x86_64 && systemctl restart >
> > systemd-modules-load.service
> > I do the recommended options.
> > dnf packages are already installed
> > The akmods builds the moduals, and they are in the location
> > But restarting the systemd-modules-load results in error.
>
> Does a simple "modprobe vboxdrv" also fails ?
>
> What gives: modinfo vboxdrv

# modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted

# modinfo vboxdrv
filename:      
/lib/modules/5.5.13-200.fc31.x86_64/extra/VirtualBox/vboxdrv.ko
version:        6.1.4_RPMFusion r136177 (0x002d0001)
license:        GPL
description:    Oracle VM VirtualBox Support Driver
author:         Oracle Corporation
srcversion:     1339FC9C1EAAA355E78EDA5
depends:
retpoline:      Y
name:           vboxdrv
vermagic:       5.5.13-200.fc31.x86_64 SMP mod_unload
parm:           force_async_tsc:force the asynchronous TSC mode (int)
> Also, double check that the modules have been build with:
>
> dnf list installed kmod-VirtualBox*

dnf list installed kmod-VirtualBox*
Installed Packages
kmod-VirtualBox.x86_64                        6.1.4-3.fc31
@rpmfusion-free-updates
kmod-VirtualBox-5.5.13-200.fc31.x86_64.x86_64 6.1.4-3.fc31 @@commandline
> > On exact same machine with Fedora 29, this was working. This is a clean
> > install on a new hard disk.
> > Any ideals?
>
> With Fedora 31 you have newer kernels: the Virtualbox sources may
> become incompatile with them.
>
> --
> francis

Thanks. Don't know if that gives any more info.

On Sun, 05 Apr 2020 01:55:13 +1000 "Michael D. Setzer II via users" wrote:
> > Does a simple "modprobe vboxdrv" also fails ?
> # modprobe vboxdrv
> modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted

This happens if you are not root. Is it the case?
> # modinfo vboxdrv
> filename:

OK
> > Also, double check that the modules have been build with:
> > dnf list installed kmod-VirtualBox*
> dnf list installed kmod-VirtualBox*
> Installed Packages
> kmod-VirtualBox.x86_64                        6.1.4-3.fc31
> @rpmfusion-free-updates
> kmod-VirtualBox-5.5.13-200.fc31.x86_64.x86_64 6.1.4-3.fc31 @@commandline

OK.

That shows also that you are using VirtualBox from rpmfusion like me.

[Michael D. Setzer II]

> On Sun, 05 Apr 2020 01:55:13 +1000 "Michael D. Setzer II via users" wrote:
> > > Does a simple "modprobe vboxdrv" also fails ?
> > # modprobe vboxdrv
> > modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted
>
> This happens if you are not root. Is it the case?

Am root (su) when done.
Ran command with strace, and it ends with this?
openat(AT_FDCWD, "/sys/module/vboxdrv/initstate", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
stat("/sys/module/vboxdrv", 0x7ffffbbe9ac0) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/sys/module/vboxdrv/initstate", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
stat("/sys/module/vboxdrv", 0x7ffffbbe9ac0) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD,
"/lib/modules/5.5.13-200.fc31.x86_64/extra/VirtualBox/vboxdrv.ko",
O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1", 6)               = 6
lseek(3, 0, SEEK_SET)                   = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=731744, ...}) = 0
mmap(NULL, 731744, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc9e915f000
finit_module(3, "", 0)                  = -1 EPERM (Operation not permitted)
write(2, "modprobe: ERROR: could not inser"..., 69modprobe: ERROR: could
not insert 'vboxdrv': Operation not permitted
) = 69
munmap(0x7fc9e915f000, 731744)          = 0
close(3)                                = 0
munmap(0x7fc9e93b2000, 577066)          = 0
munmap(0x7fc9e92a3000, 1109184)         = 0
munmap(0x7fc9e9212000, 593336)          = 0
munmap(0x7fc9e9995000, 10752)           = 0
exit_group(1)                           = ?
+++ exited with 1 +++

So, it seems to be looking for directory and files that don't exist.
sys does not show write access for root, but that is the same for my
Fedora 30 notebook that is running VirtualBox with no issue.

Thanks for the time. Is 3:10am here in Guam, so going to bed..
> > # modinfo vboxdrv
> > filename:
>
> OK
> > > Also, double check that the modules have been build with:
> > > dnf list installed kmod-VirtualBox*
> > dnf list installed kmod-VirtualBox*
> > Installed Packages
> > kmod-VirtualBox.x86_64                        6.1.4-3.fc31
> > @rpmfusion-free-updates
> > kmod-VirtualBox-5.5.13-200.fc31.x86_64.x86_64 6.1.4-3.fc31 @@commandline
>
> OK.
>
> That shows also that you are using VirtualBox from rpmfusion like me.
>
> --
> francis

[Bob Marcan]

On Sat, 04 Apr 2020 18:10:17 +0200
[e-mail] wrote:
> On Sun, 05 Apr 2020 01:55:13 +1000 "Michael D. Setzer II via users" wrote:
> > > Does a simple "modprobe vboxdrv" also fails ?
> > # modprobe vboxdrv
> > modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted
>
> This happens if you are not root. Is it the case?
> > # modinfo vboxdrv
> > filename:
>
> OK
> > > Also, double check that the modules have been build with:
> > > dnf list installed kmod-VirtualBox*
> > dnf list installed kmod-VirtualBox*
> > Installed Packages
> > kmod-VirtualBox.x86_64                        6.1.4-3.fc31
> > @rpmfusion-free-updates
> > kmod-VirtualBox-5.5.13-200.fc31.x86_64.x86_64 6.1.4-3.fc31 @@commandline
>
> OK.
>
> That shows also that you are using VirtualBox from rpmfusion like me.

Is there any particular reason you don't use KVM?
It is Linux native virtualization.

[Samuel Sieb]

On 4/4/20 8:55 AM, Michael D. Setzer II via users wrote:
> > On Sun, 05 Apr 2020 01:12:04 +1000 "Michael D. Setzer II via users" wrote:
> > Does a simple "modprobe vboxdrv" also fails ?
> >
> > What gives: modinfo vboxdrv
>
> # modprobe vboxdrv
> modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted

Do you have secure boot enabled?  If you do, you can't use self-compiled 
modules unless you add a key to the EFI key storage.

[Michael D. Setzer II]

> On 4/4/20 8:55 AM, Michael D. Setzer II via users wrote:
> > > On Sun, 05 Apr 2020 01:12:04 +1000 "Michael D. Setzer II via users"
> > > wrote:
> > > Does a simple "modprobe vboxdrv" also fails ?
> > >
> > > What gives: modinfo vboxdrv
> >
> > # modprobe vboxdrv
> > modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted
>
> Do you have secure boot enabled?  If you do, you can't use self-compiled
> modules unless you add a key to the EFI key storage.

The old hard disk was not EFI setup, but this clean install did do and EFI
setup? So, didn't change any settings in bios about secure boot, but
perhaps it was set, and didn't matter since it was non-EFI.
How would one add an EFI key??
Currently accessing machine remotely, so hard to check the BIOS.
Thanks.
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Michael D. Setzer II]

> On Sat, 04 Apr 2020 18:10:17 +0200
> [e-mail] wrote:
> > On Sun, 05 Apr 2020 01:55:13 +1000 "Michael D. Setzer II via users"
> > wrote:
> > > > Does a simple "modprobe vboxdrv" also fails ?
> > > # modprobe vboxdrv
> > > modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted
> >
> > This happens if you are not root. Is it the case?
> > > # modinfo vboxdrv
> > > filename:
> >
> > OK
> > > > Also, double check that the modules have been build with:
> > > > dnf list installed kmod-VirtualBox*
> > > dnf list installed kmod-VirtualBox*
> > > Installed Packages
> > > kmod-VirtualBox.x86_64                        6.1.4-3.fc31
> > > @rpmfusion-free-updates
> > > kmod-VirtualBox-5.5.13-200.fc31.x86_64.x86_64 6.1.4-3.fc31
> >
> > @@commandline
> >
> > OK.
> >
> > That shows also that you are using VirtualBox from rpmfusion like me.
>
> Is there any particular reason you don't use KVM?
> It is Linux native virtualization.

Have been maintaining the G4L project since 2004, and don't recall exactly
when I started using VirtualBox with it. Originally, had a 32bit separate
machine, but found that creating a 32bit virtual machine was faster
process. Don't know if it was before KVM or if VirtualBox just came up
first.

Might have to take a look at it, or it might be some issue with secure
boot. The clean install used EFI boot setup, which the previous setup did
not use.
Thanks for the info.
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Samuel Sieb]

On 4/4/20 8:56 PM, Michael D. Setzer II via users wrote:
> > On 4/4/20 8:55 AM, Michael D. Setzer II via users wrote:
> > > > On Sun, 05 Apr 2020 01:12:04 +1000 "Michael D. Setzer II via users"
> > > > wrote:
> > > > Does a simple "modprobe vboxdrv" also fails ?
> > > >
> > > > What gives: modinfo vboxdrv
> > >
> > > # modprobe vboxdrv
> > > modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted
> >
> > Do you have secure boot enabled?  If you do, you can't use self-compiled
> > modules unless you add a key to the EFI key storage.
>
> The old hard disk was not EFI setup, but this clean install did do and EFI
> setup? So, didn't change any settings in bios about secure boot, but
> perhaps it was set, and didn't matter since it was non-EFI.
> How would one add an EFI key??
> Currently accessing machine remotely, so hard to check the BIOS.

Look up "mokutil".  You would have to sign the kernel module with your 
key.  And you need physical access to the computer to enroll the key. 
Secure boot is enabled by default in EFI systems.  Your easiest solution 
would be to get to the computer or get someone else to disable secure 
boot in the BIOS.
The best solution would be to switch to kvm, especially if you can't get 
physical access.

[Greg Woods]

On Sat, Apr 4, 2020 at 12:32 PM Bob Marcan  wrote:
> Is there any particular reason you don't use KVM?
> It is Linux native virtualization.

I can't speak for anyone else, but any time I have tried to use any kind of
Windows on a VM under KVM, the performance has been horrible. This is why I
still use VirtualBox.

--Greg

[Bob Marcan]

On Sun, 5 Apr 2020 08:30:13 -0600
Greg Woods  wrote:
> On Sat, Apr 4, 2020 at 12:32 PM Bob Marcan  wrote:
> > Is there any particular reason you don't use KVM?
> > It is Linux native virtualization.
>
> I can't speak for anyone else, but any time I have tried to use any kind of
> Windows on a VM under KVM, the performance has been horrible. This is why I
> still use VirtualBox.
>
> --Greg

Not brilliant, but i can't say so for my configuration: 
 Win 7, Win 10 in KVM
     *-memory
          description: System memory
          physical id: 0
          size: 8GiB
     *-cpu
          product: Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz
          vendor: Intel Corp.
          physical id: 1
          bus info: cpu@0
          size: 2239MHz
          capacity: 2667MHz
          width: 64 bits

BR,  B.Marčan

[Michael D. Setzer II]

On 5 Apr 2020 at 0:50, Samuel Sieb wrote:

Subject:        	Re: Virtual Box not loading vboxdrv on Clean 
install of Fedora 31
To:             	[e-mail]
From:           	Samuel Sieb 
Date sent:      	Sun, 5 Apr 2020 00:50:50 -0700
Send reply to:  	Community support for Fedora users 
> On 4/4/20 8:56 PM, Michael D. Setzer II via users wrote:
> > > On 4/4/20 8:55 AM, Michael D. Setzer II via users wrote:
> > > > > On Sun, 05 Apr 2020 01:12:04 +1000 "Michael D. Setzer II via users"
> > > > > wrote:
> > > > > Does a simple "modprobe vboxdrv" also fails ?
> > > > >
> > > > > What gives: modinfo vboxdrv
> > > >
> > > > # modprobe vboxdrv
> > > > modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted
> > >
> > > Do you have secure boot enabled?  If you do, you can't use self-compiled
> > > modules unless you add a key to the EFI key storage.
> >
> > The old hard disk was not EFI setup, but this clean install did do and EFI
> > setup? So, didn't change any settings in bios about secure boot, but
> > perhaps it was set, and didn't matter since it was non-EFI.
> > How would one add an EFI key??
> > Currently accessing machine remotely, so hard to check the BIOS.
>
> Look up "mokutil".  You would have to sign the kernel module with your 
> key.  And you need physical access to the computer to enroll the key. 
> Secure boot is enabled by default in EFI systems.  Your easiest solution 
> would be to get to the computer or get someone else to disable secure 
> boot in the BIOS.
> The best solution would be to switch to kvm, especially if you can't get 
> physical access.

Went by house where machine is, and went into BIOS. Shows that secure 
boot was enabled and loaded, but it showed no option to disable it. Going 
into details, it showed it had a windows OS setup, and had various options to 
remove the keys, but wasn't clear if that would just disable the secure boot, 
or would make the machine not boot any OS??

I'm assuming the Fedora 31 install setup the EFI boot using a windows 
compatible option. Other than selected a standard partition setup instead of 
LVM, I did the defaults on the install.

Will have to do some more research. It is an ASUS motherboard with quad 
processor.

Thanks.
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:[e-mail]                            
 mailto:[e-mail]
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS

ROSETTA      66311323.990119 | ABC          16613838.513356
SETI        109804121.703177 | EINSTEIN    141859222.999240

[Samuel Sieb]

On 4/6/20 10:10 AM, Michael D. Setzer II wrote:
> Went by house where machine is, and went into BIOS. Shows that secure
> boot was enabled and loaded, but it showed no option to disable it. Going
> into details, it showed it had a windows OS setup, and had various options to
> remove the keys, but wasn't clear if that would just disable the secure boot,
> or would make the machine not boot any OS??

Don't remove any keys, that won't help.  There are a few EFI systems 
that don't seem to let you disable secure boot, although I think that's 
actually one of the requirements to be compliant.  I have also seen some 
where you have to set an admin password first before it will let you 
change those settings.  Try that.  You might be able to remove the 
password after.

[Fernando Cassia]

On Sat, Apr 4, 2020, 15:32 Bob Marcan  wrote:
> Is there any particular reason you don't use KVM?
> It is Linux native virtualization.

Look, we're here to make Virtualbox better. Not to encourage users to stop
using it.

Thanks for your understanding.

FC

[Bob Marcan]

On Mon, 6 Apr 2020 16:22:20 -0300
Fernando Cassia  wrote:
> On Sat, Apr 4, 2020, 15:32 Bob Marcan  wrote:
> > Is there any particular reason you don't use KVM?
> > It is Linux native virtualization.
> Look, we're here to make Virtualbox better. Not to encourage users to stop
> using it.
>
> Thanks for your understanding.
>
> FC

OK. 
Are you Oracle employee involved in development of VirtualBox? :-)

BM

[Michael D. Setzer II]

On 7 Apr 2020 at 16:39, Bob Marcan wrote:

Date sent:      	Tue, 7 Apr 2020 16:39:56 +0200
From:           	Bob Marcan 
To:             	[e-mail]
Subject:        	Re: Virtual Box not loading vboxdrv on Clean install of 
Fedora 31
Send reply to:  	Community support for Fedora users 
> On Mon, 6 Apr 2020 16:22:20 -0300
> Fernando Cassia  wrote:
> > On Sat, Apr 4, 2020, 15:32 Bob Marcan  wrote:
> > > Is there any particular reason you don't use KVM?
> > > It is Linux native virtualization.
> > Look, we're here to make Virtualbox better. Not to encourage users to stop
> > using it.
> >
> > Thanks for your understanding.

Just wondering, why couldn't the Virtualbox moduals be signed with the 
same configuration as the regular Fedora kernels?  Since the EFI boots the 
linux kernels, that system is already working, so why would one need to 
create a completely different setup for moduals that are suppose to work with 
the kernel?

Thanks.
> > FC
>
> OK. 
> Are you Oracle employee involved in development of VirtualBox? :-)
>
> BM
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:[e-mail]                            
 mailto:[e-mail]
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS

ROSETTA      66311323.990119 | ABC          16613838.513356
SETI        109804121.703177 | EINSTEIN    141859222.999240

[stan]

On Wed, 08 Apr 2020 16:23:49 +1000
"Michael D. Setzer II via users"  wrote:
> Just wondering, why couldn't the Virtualbox moduals be signed with
> the same configuration as the regular Fedora kernels?  Since the EFI
> boots the linux kernels, that system is already working, so why would
> one need to create a completely different setup for moduals that are
> suppose to work with the kernel?

The kernel is signed with Fedora's private key for that release.  So,
the virtualbox module would also need to be signed with that key.  But
it isn't a Fedora module, so Fedora will not sign it.  That is, whoever
created the virtualbox module would need to have Fedora's private key
in order to sign it and have it accepted.

A virtualbox module thus needs to be signed with a different private
key, and the public key for that private key has to be available to the
kernel / system that is loading that module in order for it to be
validated and successfully load.