How to Download and Run an OSBoxes VM Image

Updated

OSBoxes provides ready-to-use Linux/Unix virtual machine images in VDI, VMDK, and VHD formats for VirtualBox and VMware, so you can run a secondary OS without installing it alongside your main system. To use one: pick the distro and format you need, download the image, import it into VirtualBox or VMware, then start the VM. This works on any host that runs one of those two hypervisors; you need enough free disk space for the image and enough RAM to run a guest OS.

Before you download

Two things determine which file you should get:

  • Your hypervisor. VirtualBox uses VDI (and can also use VMDK). VMware uses VMDK. Download the format that matches the software you already have installed.
  • Your host resources. A VM shares your host's CPU, RAM, and disk. Plan for the guest's memory allocation plus your normal host usage, and leave room for the image file itself.

OSBoxes describes VirtualBox as an x86 and AMD64/Intel64 virtualization product, available free as Open Source Software under the GNU GPL V2 license. It describes VMware Player as a free virtualization product for personal use that can run existing virtual appliances and create new virtual machines. If you don't have either installed yet, install one first — the image alone won't run.

Step 1: Choose and download the image

  1. Go to osboxes.org and find the distribution you want. The site lists images by distro and release, with entries such as Feren OS 2025.03, Debian 12.11.0, SparkyLinux 7.8, Calculate Linux 20250717, and Ubuntu Cinnamon / Ubuntu Unity 25.04.
  2. Select the download link for your hypervisor — VirtualBox or VMware.
  3. Save the file to a location with enough free space. VM images are large, so avoid a drive that's nearly full.

The site's own framing is simple: "Simply download the image you need and run it effortlessly as a virtual machine." There is no complex setup procedure to follow on the OSBoxes side — the work happens in your hypervisor.

Step 2: Import the image

VirtualBox

  1. Open VirtualBox.
  2. Use File → Import Appliance if you downloaded an OVA/OVF, or create a new VM and attach the downloaded VDI/VMDK as its hard disk if you downloaded a raw disk image.
  3. Point the wizard at your downloaded file and confirm.
  4. Review the assigned memory and CPU settings before finishing; adjust them to fit your host.

VMware

  1. Open VMware Player (or Workstation).
  2. Choose Open a Virtual Machine and select the downloaded VMDK-based VM file, or create a new VM and attach the VMDK as an existing disk.
  3. Confirm the hardware settings.

Expected result: the VM appears in your hypervisor's library, ready to start.

Step 3: Start the VM and log in

  1. Select the VM and click Start (VirtualBox) or Play (VMware).
  2. Wait for the guest OS to boot. First boot can take longer than subsequent ones.
  3. Log in with the credentials provided on the OSBoxes download page for that image. These are set by OSBoxes, not by you, so check the page rather than guessing.

If the VM boots to a login screen and accepts the documented credentials, the import worked.

Verifying the image

OSBoxes publishes a "Guide to verify/audit our VM images." Use it if you want to confirm the file you downloaded is intact and matches what the site published before you run it. This is worth doing for large downloads or on a slow connection, where a corrupted file is more likely. The general approach is to compare a checksum of your downloaded file against the value published by the source; follow OSBoxes' own guide for the exact procedure and values.

Common snags

  • Wrong format. A VMDK won't import cleanly into a VirtualBox workflow expecting VDI, and vice versa. Re-download the matching format rather than converting unless you're comfortable with disk conversion tools.
  • Not enough RAM or disk. The VM may fail to start or run very slowly. Lower the guest's allocated memory or free up host disk space.
  • Login fails. You're likely using credentials you assumed rather than the ones documented for that specific image. Re-check the download page.
  • First boot seems stuck. Give it time; initial boots of a fresh image are slower than later ones.

What you get

Once running, you have a full Linux/Unix environment inside a window on your existing OS — useful for testing a distro, trying software, or working in a secondary OS without repartitioning your machine or making permanent changes to your primary setup. Because it's a VM, you can discard it and start over from the original image at any time.