[SOLVED] Debian Bullseye: Trouble running virtual machine in VirtualBox 5.2.44 32-bit

stameni · 09-18-2022, 12:25 PM

I installed VirtualBox 5.2.44 32-bit using offline installer, accordingly to the advice I got at the other link (https://www.linuxquestions.org/quest...ye-4175716671/). Operating system installed is Debian Bullseye 32-bit. I created new virtual machine using the same disk image (Debian 32-bit).

However, when I try to start the guest, attempting to install it, I get the following error message:

Quote:

Kernel driver not installed (rc=-1908)

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 have executed this as root, however I always get this error:

Quote:

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
linux-headers-686-pae linux-headers-5.10.0-18-686-pae
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
linux-headers-686-pae linux-headers-5.10.0-18-686-pae

There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may 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.

The VirtualBox itself allways reports the following:

Quote:

The virtual machine 'Debian' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

I am not sure what to try next. Is something wrong about "EFI Secure Boot"? I didn't use something similar during installation.

Emerson · 09-18-2022, 03:22 PM

Is your system really so weak it can't run 64 bit Debian? You need some extra RAM for VM, 32 bit system really can't offer this RAM in an efficient way. Note, you can run 32 bit guests on 64 bit VirtualBox.

descendant_command · 09-19-2022, 08:00 AM

Did you install the header files as it tells you?

enigma9o7 · 09-19-2022, 10:23 AM

Install the headers and the other tools you'll need, you should:

Code:

sudo apt install build-essential

Not sure where you installed virtualbox from, but the recommended source for virtualbox on debian is the fasttrack repository and it has a much newer version 6.1.38.
https://fasttrack.debian.net/
edit: but it appears only to have amd64 version anyway http://fasttrack.debian.net/debian-f.../v/virtualbox/ and the other thread you linked explains where and why you're using that version, which makes sense.

stameni · 09-20-2022, 10:21 AM

Quote:

Originally Posted by enigma9o7

Install the headers and the other tools you'll need, you should:

Code:

sudo apt install build-essential

I have tried this, but there seems to be no updates:

Code:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
build-essential is already the newest version (12.9).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

There is no change with VirtualBox when trying to start the actual virtual machine, after executing the command you proposed.

Quote:

Not sure where you installed virtualbox from, but the recommended source for virtualbox on debian is the fasttrack repository and it has a much newer version 6.1.38.
https://fasttrack.debian.net/
edit: but it appears only to have amd64 version anyway

That is true. I installed the latest 32-bit version (5.2.44) for all distributions.

It seems that problem might be within the VBox kernel, because of the error saying "Kernel driver not installed (rc=-1908)". I get the similar error while rebooting the system. I can't quote nor photograph it because it scrolls out too fast. (If there was a log, I might found and copy/paste it?)

computersavvy · 09-20-2022, 06:28 PM

Quote:

Originally Posted by stameni

It seems that problem might be within the VBox kernel, because of the error saying "Kernel driver not installed (rc=-1908)". I get the similar error while rebooting the system. I can't quote nor photograph it because it scrolls out too fast. (If there was a log, I might found and copy/paste it?)

Quite possibly you may be able to find that message in either the output of the 'dmesg' command or in the system message logs.

When a kernel driver fails to load, it may possibly have some other error. For example, on a uefi booting system with secure boot enabled the module for virtualbox will not load unless it was signed and the bios recognizes the signature, even if the module is otherwise perfect. The point to find out why the module is not loading and operational is to look at the logs, in detail. The vbox module is required before you can create or load a VM with vbox.

descendant_command · 09-21-2022, 06:53 AM

Quote:

I have tried this, but there seems to be no updates:

Code:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
build-essential is already the newest version (12.9).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Doesn't mean you have the correct headers for the running kernel.

stameni · 09-26-2022, 01:42 PM

I think I am going to solve this (and other similar) problem the easier way, by replacing 32-bit CPU with 64-bit one.

Nevertheless, I am very grateful to LQ's forum members who tried to help me.