How to Fix Error "No Usable Default Provider" Error in Vagrant on Rocky Linux 9.4

If you're encountering the frustrating "no usable default provider could be found for your system" error while attempting to run vagrant up on Rocky Linux 9.4, you're not alone. This error typically arises from missing dependencies required to build VirtualBox kernel modules, or because VirtualBox isn't being recognized by Vagrant. This guide will walk you through the most common solutions to resolve this issue.

1. Installing the Essential Build Dependencies

VirtualBox needs specific development tools and kernel headers to construct its kernel modules. Without these, Vagrant won't be able to detect VirtualBox correctly.

1.1. Update Your System

First, ensure your system packages are up-to-date:

      sudo dnf update -y
    

1.2. Installing Development Tools and Kernel Headers

Next, install the necessary packages for building VirtualBox kernel modules. This includes gcc, make, perl, kernel-devel, and kernel-headers:

      sudo dnf install -y gcc make perl kernel-devel kernel-headers
    

Important Note: It's crucial to ensure that the kernel-devel and kernel-headers versions match your currently running kernel. To check your kernel version, use:

      uname -r
    

If your current kernel version is, for example, 5.14.0-427.13.1.el9_4.x86_64, install the matching kernel headers and development package:

      sudo dnf install -y kernel-devel-$(uname -r) kernel-headers-$(uname -r)
    

2. Rebuilding VirtualBox Kernel Modules

Once the required dependencies are installed, you must rebuild the VirtualBox kernel modules. This is a crucial step to ensure VirtualBox can run properly:

      sudo /sbin/vboxconfig
    

Possible Outcomes:

• Success: You'll see messages indicating that VirtualBox services have been stopped and restarted, and the kernel modules are being built successfully.

• Failure: If errors occur, especially related to Secure Boot, proceed to the next section.

3. Addressing Secure Boot Issues (If Applicable)

If your system utilizes EFI Secure Boot, it might prevent the loading of unsigned kernel modules, including those required by VirtualBox. Here are two solutions:

3.1. Disabling Secure Boot

The simplest and most common solution is to disable Secure Boot, although it's important to remember that this may reduce the security of your system.

Steps to Disable Secure Boot:

1. Reboot Your System:

         sudo reboot
       

   
   

2. Enter BIOS/UEFI Settings: During the boot process, press keys like F2, F10, Del, or Esc (the specific key depends on your hardware).

3. Disable Secure Boot: Navigate to the Secure Boot settings and change the setting to Disabled.

4. Save and Reboot: Save the changes and reboot your system.

5. Rebuild VirtualBox Kernel Modules: After rebooting, run:

         sudo /sbin/vboxconfig
       

   
   

3.2. Signing VirtualBox Kernel Modules

If you prefer to keep Secure Boot enabled, you'll need to manually sign the VirtualBox kernel modules. This process involves generating and enrolling your own signing keys into the system's MOK (Machine Owner Key). For detailed instructions, consult the VirtualBox documentation.

4. Verifying VirtualBox Installation

To ensure that VirtualBox is properly installed and recognized, verify its version:

      VBoxManage --version
    

Expected Output: You should see a version number, for example, 7.0.6r137139, confirming that VirtualBox is installed.

By following these steps, you should be able to resolve the "no usable default provider" error and get Vagrant up and running on your Rocky Linux 9.4 system. Remember to consult the VirtualBox documentation for any specific instructions related to Secure Boot or other potential error scenarios.