0

I am on Ubuntu:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:    20.04
Codename:   focal

Kernel version:

uname -r
5.13.0-23-generic

The issue is I am trying to run Vagrant (vagrant up) and get the following output:

The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The reason
is shown below:

VirtualBox is complaining that the kernel module is not loaded. Please run VBoxManage --version or open the VirtualBox GUI to see the error message which should contain instructions on how to fix this error.

So, when I run VBoxManage --version I get:

WARNING: The vboxdrv kernel module is not loaded. Either there is no
 module
        available for the current kernel (5.13.0-23-generic) or it failed to
         load. Please recompile the kernel module and install it by
        sudo /sbin/vboxconfig

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

6.0.24r139119

When I run sudo /sbin/vboxconfigre I get:

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-generic linux-headers-5.13.0-23-generic
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-generic linux-headers-5.13.0-23-generic

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.

So basically, I end up with a suggestion of running the same command (/sbin/vboxconfig).

UPDATE: As requested, here is the output for command dpkg -l | grep virtualbox

ii  virtualbox-6.0                                  6.0.24-139119~Ubuntu~eoan                                                       amd64        Oracle VM VirtualBox

So since the Linux headers seem to be the issue, I tried to download the headers like so:

sudo apt install linux-headers-$(uname -r)

And I get this:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies. linux-headers-5.13.0-23-generic : Depends: libc6 (>= 2.34) but 2.31-0ubuntu9.2 is to be installed E: Unable to correct problems, you have held broken packages.

So, I had a look, and it turns out that for my version Linux version, I should be running headers with version: 5.4.0.91.95 or so

but instead I am running linux-headers-5.13.0-23-generic which apparently are the headers for the Linux version 21.10 (Impish Indri) as it can be seen in this link:

https://pkgs.org/download/linux-headers-generic

So, somehow I am running headers for version 21.10 which is not compatible with libc6 of my actual Linux version 20.04.

I tried to update the libc6, but Ubuntu warned me that many things could go wrong by doing that so I did not proceed with that.

I am relatively new to Linux so apologies if am saying no sense stuff.

All I want to do is get Vagrant running, but it looks like to get that I first need to get a lot of other stuff sorted out. Thank you all!

Andres
  • 1

1 Answers1

0

I get a try. You have focal-proposed enabled. Bad Idea.

Please try this solution to revert packages to normal sources. Pay attention you have to change precise of curse to focal in the file for apt pinning.

nobody
  • 5,792