How to Install VirtualBox on Debian

VirtualBox lets you run multiple operating systems on a single machine without repartitioning or dual-booting. Whether you need to test software across different Linux distributions, run Windows applications in isolation, or experiment with new Debian releases before committing to an upgrade, VirtualBox provides a straightforward way to create and manage virtual machines. For running Linux applications in sandboxed environments without full virtualization, Flatpak provides a lighter-weight alternative. By the end of this guide, you will have VirtualBox installed on Debian with the Extension Pack configured for USB 3.0, disk encryption, and remote display support.

Choose Your VirtualBox Installation Method

You can install VirtualBox through two methods on Debian. The extrepo method simplifies repository management by handling GPG keys and configuration automatically, while manual repository configuration provides more control for advanced users or scripted deployments.

Method	Channel	Version	Updates	Best For
extrepo (Recommended)	Oracle Repository	7.1, 7.2	Automatic via apt upgrade	Most users; quick setup with automatic GPG handling
Manual Repository	Oracle Repository	7.1, 7.2	Automatic via apt upgrade	Scripted deployments, custom configurations, or learning APT internals

For most users, we recommend the extrepo method because it handles GPG key management automatically and detects your Debian version to configure the correct repository URL. Use manual configuration only when you need explicit control over the repository setup or when deploying in automated environments.

Method 1: Install VirtualBox with extrepo (Recommended)

The extrepo tool is Debian’s official method for managing external repositories. It downloads GPG keys, configures the repository, and handles version detection automatically.

Install extrepo and Enable Contrib Policy

First, install the extrepo package and enable the contrib policy required for the VirtualBox repository:

sudo apt update
sudo apt install extrepo -y

By default, extrepo only enables repositories with free software. VirtualBox uses the contrib component, so you need to enable it in the extrepo configuration:

sudo sed -i 's/# - contrib/- contrib/' /etc/extrepo/config.yaml

Enable the VirtualBox Repository

With the contrib policy enabled, add the VirtualBox repository:

sudo extrepo enable virtualbox
sudo apt update

As a result, the extrepo tool automatically downloads the Oracle GPG key and creates a properly configured repository file at /etc/apt/sources.list.d/extrepo_virtualbox.sources.

Install VirtualBox and Kernel Headers

Now, install VirtualBox along with the kernel headers required to build the VirtualBox kernel modules:

sudo apt install virtualbox-7.2 linux-headers-$(uname -r) -y

VirtualBox 7.1 is also available if you need it for compatibility reasons. Install it with sudo apt install virtualbox-7.1 instead.

During installation, the system compiles and loads the VirtualBox kernel modules automatically. This process requires the kernel headers matching your running kernel.

Verify the Installation

To confirm the installation succeeded, run the following command to check that VirtualBox came from the Oracle repository:

apt-cache policy virtualbox-7.2

You should see output similar to this:

virtualbox-7.2:
  Installed: 7.2.4-170995~Debian~bookworm
  Candidate: 7.2.4-170995~Debian~bookworm
  Version table:
 *** 7.2.4-170995~Debian~bookworm 500
        500 https://download.virtualbox.org/virtualbox/debian bookworm/contrib amd64 Packages
        100 /var/lib/dpkg/status

The version number and Debian codename (bullseye, bookworm, or trixie) in your output will reflect your specific installation.

Next, verify the VirtualBox kernel driver service is running:

systemctl status vboxdrv --no-pager

Expected output:

● vboxdrv.service - VirtualBox Linux kernel module
     Loaded: loaded (/lib/systemd/system/vboxdrv.service; enabled; preset: enabled)
     Active: active (exited) since Fri 2025-12-20 10:30:00 UTC; 5min ago
    Process: 1234 ExecStart=/sbin/vboxconfig (code=exited, status=0/SUCCESS)
   Main PID: 1234 (code=exited, status=0/SUCCESS)
        CPU: 2.500s

An active (exited) status indicates the kernel modules loaded successfully. However, if the service shows as inactive, enable and start it with the following command:

sudo systemctl enable vboxdrv --now

If you used extrepo, skip to the Launch VirtualBox section. The following method covers manual repository configuration for users who prefer explicit control.

Method 2: Install VirtualBox with Manual Repository Configuration

Manual repository configuration gives you direct control over the GPG key placement and repository file format. This approach is useful for scripted deployments or when you need to customize the repository configuration.

Install Prerequisite Packages

Before adding the repository, install the packages required to download the GPG key and configure the repository:

sudo apt update
sudo apt install ca-certificates curl gnupg lsb-release -y

Specifically, these packages provide SSL certificate validation (ca-certificates), file downloading (curl), GPG key handling (gnupg), and release detection (lsb-release) needed to securely add the VirtualBox repository.

Import the VirtualBox GPG Key

Next, download and convert the Oracle GPG key to binary format in a single command:

curl -fsSL https://www.virtualbox.org/download/oracle_vbox_2016.asc | sudo gpg --dearmor -o /usr/share/keyrings/virtualbox.gpg

This command fetches the ASCII-armored key, converts it to the binary format APT requires, and saves it directly to the keyrings directory with proper ownership.

Add the VirtualBox Repository

After importing the key, create the repository configuration using the modern DEB822 .sources format:

cat <<EOF | sudo tee /etc/apt/sources.list.d/virtualbox.sources
Types: deb
URIs: https://download.virtualbox.org/virtualbox/debian
Suites: $(lsb_release -cs)
Components: contrib
Architectures: $(dpkg --print-architecture)
Signed-By: /usr/share/keyrings/virtualbox.gpg
EOF

This guide uses DEB822 .sources files for repository configuration, which provides a more explicit and readable format than legacy .list files. For format details, see the DEB822 format reference.

Once you add the repository, refresh the package index:

sudo apt update

Install VirtualBox and Kernel Headers

With the repository configured, install VirtualBox along with the kernel headers required for building the kernel modules:

sudo apt install virtualbox-7.2 linux-headers-$(uname -r) -y

During this process, the installer compiles and loads the VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp) automatically.

Verify the Installation

To verify the installation, confirm that VirtualBox came from the Oracle repository:

apt-cache policy virtualbox-7.2

Expected output:

virtualbox-7.2:
  Installed: 7.2.4-170995~Debian~bookworm
  Candidate: 7.2.4-170995~Debian~bookworm
  Version table:
 *** 7.2.4-170995~Debian~bookworm 500
        500 https://download.virtualbox.org/virtualbox/debian bookworm/contrib amd64 Packages
        100 /var/lib/dpkg/status

Additionally, verify that the VirtualBox kernel driver service is running:

systemctl status vboxdrv --no-pager

If the service shows as inactive, enable and start it:

sudo systemctl enable vboxdrv --now

Launch VirtualBox

With VirtualBox installed and the kernel modules loaded, you can start creating virtual machines.

Launch from Terminal

Alternatively, start VirtualBox from the command line by running:

virtualbox

Launch from Applications Menu

For desktop environments, launch VirtualBox through the graphical interface. If you use GNOME and want to customize how applications appear in your menu, GNOME Tweaks provides additional configuration options:

1. Search for “Terminal” in Activities and open it, or use your application menu
2. Search for “VirtualBox” or navigate to Applications → System Tools → Oracle VirtualBox
3. Click the VirtualBox icon to launch the application

Install the VirtualBox Extension Pack

The Extension Pack adds USB 2.0/3.0 support, VirtualBox Remote Desktop Protocol (VRDP), disk encryption, and PXE boot for Intel network cards. Oracle does not include these features in the base VirtualBox package due to licensing restrictions.

Licensing: The Extension Pack is licensed under the Personal Use and Evaluation License (PUEL), which permits free use for personal, educational, and evaluation purposes. Commercial use requires a paid license from Oracle. Review the PUEL license terms before deployment.

Download the Extension Pack

The Extension Pack version must match your installed VirtualBox version exactly. If wget is not installed on your system, install it first:

sudo apt install wget -y

Next, check your VirtualBox version to download the matching Extension Pack:

VBOX_VERSION=$(vboxmanage -v | cut -dr -f1)
echo "VirtualBox version: $VBOX_VERSION"

Expected output:

VirtualBox version: 7.2.4

Then, download the matching Extension Pack:

wget "https://download.virtualbox.org/virtualbox/${VBOX_VERSION}/Oracle_VirtualBox_Extension_Pack-${VBOX_VERSION}.vbox-extpack"

Install the Extension Pack

Once the download completes, install the Extension Pack:

sudo vboxmanage extpack install --replace Oracle_VirtualBox_Extension_Pack-${VBOX_VERSION}.vbox-extpack

When prompted to accept Oracle’s license terms, type y and press Enter.

Verify Extension Pack Installation

Finally, confirm the Extension Pack installed correctly:

vboxmanage list extpacks

Expected output:

Extension Packs: 1
Pack no. 0:   Oracle VirtualBox Extension Pack
Version:      7.2.4
Revision:     170995
Edition:      
Description:  Oracle Cloud Infrastructure integration, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe, full VM encryption.
VRDE Module:  VBoxVRDP
Crypto Module: VBoxPuelCrypto
Usable:       true 
Why unusable:

Add Your User to the vboxusers Group

To use USB devices and other VirtualBox features, add your user account to the vboxusers group:

sudo usermod -aG vboxusers $USER

After adding your user to the group, log out and log back in for the group membership to take effect. Then, verify your user is in the group:

groups $USER

The output should include vboxusers in the list:

username : username sudo vboxusers

Install Guest Additions in Virtual Machines

Guest Additions are drivers and utilities installed inside the virtual machine that significantly improve performance and usability. Without Guest Additions, your VMs will have limited display resolution, require manual mouse capture, and lack shared folder support.

Guest Additions Features

Installing Guest Additions provides several important capabilities:

• Seamless mouse integration: Move the mouse freely between host and guest without pressing a release key
• Dynamic display resizing: The guest screen automatically adjusts when you resize the VM window
• Shared folders: Access host directories from within the guest operating system
• Shared clipboard: Copy and paste text and files between host and guest
• Time synchronization: Keep the guest clock accurate relative to the host

Install Guest Additions on Linux Guests

For Linux guests, you need to install build tools before mounting the Guest Additions ISO. First, start your virtual machine and open a terminal inside the guest. Then install the required packages based on your guest distribution.

For Debian and Ubuntu-based guests:

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

For Fedora and RHEL-based guests:

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

Next, insert the Guest Additions CD image by selecting Devices > Insert Guest Additions CD image from the VirtualBox menu. If the CD doesn’t auto-mount, mount it manually:

sudo mkdir -p /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom

Then run the installer:

sudo /mnt/cdrom/VBoxLinuxAdditions.run

Finally, reboot the virtual machine to activate the new drivers:

sudo reboot

Install Guest Additions on Windows Guests

For Windows guests, the process is simpler since no build tools are required. With the Windows VM running, select Devices > Insert Guest Additions CD image from the VirtualBox menu. Windows should auto-detect the CD and prompt to run it. If not, open File Explorer and run VBoxWindowsAdditions.exe from the CD drive. Follow the installation wizard, accept the driver installation prompts, and reboot when finished.

Enable Shared Folders

After installing Guest Additions, you can configure shared folders to exchange files between host and guest. First, shut down the VM. In the VirtualBox Manager, select your VM and click Settings > Shared Folders. Click the folder icon with a plus sign to add a new share, then specify the host folder path and a share name.

For Linux guests, add your user to the vboxsf group so you can access the shared folder without root privileges:

sudo usermod -aG vboxsf $USER

Log out and back in for the group change to take effect. The shared folder appears in /media/sf_<sharename> on Linux guests.

Troubleshooting VirtualBox

Kernel Module Fails to Load

If VirtualBox reports that kernel modules are not loaded when starting a VM, the modules need to be rebuilt. This commonly occurs after a kernel update. For details on managing kernel versions, see our guide on installing the latest Linux kernel on Debian.

First, check the current kernel module status:

sudo /sbin/vboxconfig

If you see errors about missing kernel headers, install them for your current kernel:

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

After installing the headers, rebuild the modules:

sudo /sbin/vboxconfig

When successful, you should see the following output:

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.

Secure Boot Prevents Module Loading

On systems with Secure Boot enabled, the kernel refuses to load unsigned modules. By default, VirtualBox modules do not include signatures.

To determine if Secure Boot is enabled, run:

mokutil --sb-state

When Secure Boot is enabled, you have two options:

• Disable Secure Boot in your system’s UEFI/BIOS settings (simplest approach)
• Sign the VirtualBox modules with a custom Machine Owner Key (MOK) and enroll it in UEFI

For most desktop users, disabling Secure Boot is the straightforward solution. Access your system’s UEFI settings during boot (typically by pressing F2, F12, or Del) and disable the Secure Boot option.

USB Devices Not Available in Guest

If USB devices are not visible in the guest VM, verify your user is in the vboxusers group:

groups $USER | grep vboxusers

When the group does not appear in the output, add your user and log out/in as described in the Extension Pack section. Also, verify the Extension Pack is installed, since USB 2.0/3.0 support requires it.

Manage VirtualBox

Update VirtualBox

Oracle delivers VirtualBox updates through the repository you configured. To update to the latest version, run:

sudo apt update
sudo apt install --only-upgrade virtualbox-7.2

After updating VirtualBox, remember to download and install the matching Extension Pack version as described in the Extension Pack section above.

Remove VirtualBox

If you no longer need VirtualBox, remove it from your system with the following commands:

sudo apt remove --purge virtualbox-7.2
sudo apt autoremove

The autoremove command cleans up dependencies that APT installed with VirtualBox and that no other packages need.

Remove the Repository (extrepo Method)

If you used extrepo to install VirtualBox, disable the repository:

sudo extrepo disable virtualbox

Additionally, to completely remove the repository configuration file, run:

sudo rm -f /etc/apt/sources.list.d/extrepo_virtualbox.sources

Remove the Repository (Manual Method)

Alternatively, if you configured the repository manually, remove the repository file and GPG key:

sudo rm -f /etc/apt/sources.list.d/virtualbox.sources
sudo rm -f /usr/share/keyrings/virtualbox.gpg

Verify Removal

Finally, refresh the package cache to verify that the Oracle repository no longer provides VirtualBox:

sudo apt update
apt-cache policy virtualbox-7.2

After complete removal, you should see the following output:

virtualbox-7.2:
  Installed: (none)
  Candidate: (none)
  Version table:

Warning: The package manager does not remove virtual machine disk images and configuration files in ~/VirtualBox VMs/. Delete this directory manually only when you no longer need your virtual machines: rm -rf ~/VirtualBox\ VMs/

Conclusion

You now have VirtualBox installed on Debian with the Extension Pack providing USB 3.0 passthrough, disk encryption, and remote display capabilities. Additionally, your user account belongs to the vboxusers group for USB device access. To get started, create your first virtual machine by clicking “New” in the VirtualBox Manager and following the wizard to install your guest operating system.