Bug 25819

Summary:	Running the suggested command '/sbin/vboxconfig" fails to install the vboxdrv kernel module after reinstalling Virtualbox
Product:	Mageia	Reporter:	Kristoffer Grundström <lovaren>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, lewyssmith, tmb, yvesbrungard, zen25000
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
See Also:	https://bugs.mageia.org/show_bug.cgi?id=31483
Whiteboard:
Source RPM:	virtualbox	CVE:
Status comment:

Description Kristoffer Grundström 2019-12-04 05:55:43 CET

Description of problem: I got the following error when I tried to start my Windows VM in Virtualbox:

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.


I opened a terminal window and logged in as root and ran /sbin/vboxconfig and I got the result:

-bash: /sbin/vboxconfig: File or directory does not exist

Version-Release number of selected component (if applicable): 6.0.14

How reproducible: All the time.

Steps to Reproduce:
1. Open Virtualbox.
2. Click to start a Windows VM.
3. See the error above.
4. Open a terminal and login as root.
5. Run /sbin/vboxconfig
6. File or directory does not exist is the result.

Comment 1 Kristoffer Grundström 2019-12-04 12:36:03 CET

I know I have disabled Secure Boot in my BIOS as well.

Comment 2 Barry Jackson 2019-12-04 13:29:33 CET

What is the output of:
rpm -qa|grep virtualbox

CC: (none) => zen25000

Comment 3 Kristoffer Grundström 2019-12-04 21:19:44 CET

virtualbox-kernel-desktop-latest-6.0.14-18.mga8
virtualbox-kernel-5.4.1-desktop-2.mga8-6.0.14-18.mga8
virtualbox-kernel-5.3.13-desktop-2.mga8-6.0.14-16.mga8
virtualbox-6.0.14-2.mga8

Comment 4 Thomas Backlund 2019-12-04 21:44:59 CET

Yeah,
I really should patch virtualbox to not suggest using /sbin/vboxconfig as we dont (and wont) ship that, we provide prebuilt kmods for core kernel

We also provide a dkms package that builds/installs the needed kmods as long as the running kernel has a matching kernel-devel package installed

CC: (none) => tmb

Comment 5 Lewis Smith 2019-12-10 21:36:38 CET

What do you want to do with this bug? Leave it open - assigned to kernel?

CC: (none) => lewyssmith

Comment 6 Kristoffer Grundström 2019-12-11 10:38:28 CET

(In reply to Lewis Smith from comment #5)
> What do you want to do with this bug? Leave it open - assigned to kernel?

It's a little bit unclear as to whom you're addressing your question to. Are you asking me or Thomas Backlund?

Comment 7 Lewis Smith 2019-12-11 12:18:13 CET

(In reply to Kristoffer Grundström from comment #6)
> It's a little bit unclear as to whom you're addressing your question to. Are
> you asking me or Thomas Backlund?
Sorry; to Thomas re comment 4. I should have said so. That was the previous comment.

Comment 8 Thomas Backlund 2019-12-11 12:30:13 CET

(In reply to Lewis Smith from comment #5)
> What do you want to do with this bug? Leave it open - assigned to kernel?

I'll assingn it to myself

Assignee: bugsquad => tmb

Comment 9 papoteur 2023-02-01 08:54:12 CET

'/sbin/vboxconfig' is still suggested today
virtualbox 7.0.6

CC: (none) => yves.brungard_mageia

Morgan Leijström 2023-02-01 10:32:40 CET

CC: (none) => fri
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=31483