Virtualizing SteamOS with QEMU/KVM: The Steps Nobody Tells You

#steamos #linux #virtualmachine #qemu

SteamOS is not a standard Linux distribution. It ships as a recovery image for the Steam Deck, not a generic ISO. That fact explains every strange requirement you face when you try to run it in a virtual machine. The file you download is a .bz2 archive, not an installer. The VM must present the virtual drive as NVMe. And if you let the system reboot right after installation it will launch into Gaming Mode, which cannot work without the Deck's custom AMD GPU.

I have a full in-depth walkthrough on my blog. This post gives you the reasoning and the exact commands to get a working VM, plus the one intervention that saves you from a permanent black screen.

The .bz2 Archive Hides a Raw Disk Image

Head to Valve's official SteamOS page and you get a steamOS-recovery-image.bz2 file. Decompress it with:

tar -xjf steamOS-recovery-image.bz2

Inside you'll find a .img file. It's a raw block-level copy of a full SteamOS installation, not a live environment. It contains a GPT partition table, the bootloader, and the A/B root partitions used for atomic updates. Valve compresses it with BZIP2 to keep the download small. That's fair.

Why You Must Use an NVMe Virtual Drive

The Steam Deck uses an NVMe SSD. The recovery image's installer scripts look for a block device at /dev/nvme0n1. If you attach the virtual disk as a SATA or IDE drive, the kernel sees /dev/sda and the installer will say no valid target is found. It's not a bug. It's what the script expects.
In QEMU you emulate an NVMe controller. First create a virtual disk:

qemu-img create -f qcow2 steamOSDrive.qcow2 16G

Then map it in the launch command. The crucial flags are:

-drive if=none,id=nvme0,file=steamOSDrive.qcow2
-device nvme,drive=nvme0,serial=badbeef

The serial number is required and can be any string. The moment the recovery environment sees an NVMe namespace, the install option lights up.

UEFI Firmware Is Not Optional

SteamOS boots via UEFI with a GPT partition layout. Legacy BIOS won't work. QEMU provides UEFI through the OVMF firmware. You need two files:

OVMF_CODE.fd (read-only firmware code)
OVMF_VARS.fd (persistent NVRAM for boot variables)

On most distros these live in /usr/share/ovmf/x64/. Pass them as pflash drives:

-drive if=pflash,format=raw,unit=0,file=OVMF.fd,readonly=on
-drive if=pflash,format=raw,unit=1,file=OVMF_VARS.fd

Without these, the VM tries BIOS mode, finds nothing on a GPT disk, and halts.

The Full Installation Command

With all pieces in place, the complete QEMU command for the installation phase looks like this:

qemu-system-x86_64 \
  -cpu host -enable-kvm -smp 2 -m 8G \
  -drive if=pflash,format=raw,unit=0,file=OVMF.fd,readonly=on \
  -drive if=pflash,format=raw,unit=1,file=OVMF_VARS.fd \
  -drive file=SteamOS.img,format=raw \
  -drive if=none,id=nvme0,file=steamOSDrive.qcow2 \
  -device nvme,drive=nvme0,serial=badbeef \
  -display "gtk,gl=on" \
  -device usb-tablet -usb

It boots the recovery image with the empty NVMe drive ready. Inside the VM, open the Wipe Devices & Install SteamOS option and click Proceed. The installer will write the A/B partitions to your virtual NVMe.

The Gaming Mode Trap (Cancel the Reboot)

Once the installation finishes, the wizard asks you to restart. If you click Proceed, SteamOS boots into Gaming Mode, which expects AMD GPU hardware. Inside a VM you get nothing but a black screen.

Do not reboot. Instead, press Ctrl + Alt + T inside the VM to open a terminal. From there you force SteamOS to boot into the KDE Plasma desktop. Run these chroot commands on both partition sets:

sudo steamos-chroot --disk nvme0n1 --partset A --no-overlay
steamos-readonly disable
echo '[Autologin]' > /etc/sddm.conf.d/zz-steamos-autologin.conf
echo 'Session=plasma.desktop' >> /etc/sddm.conf.d/zz-steamos-autologin.conf
steamos-readonly enable
exit

Repeat the same block for --partset B. Then type reboot. The VM will now start directly into a working KDE Plasma session.

Why All This Matters

SteamOS is a locked-down appliance OS built for one device. Running it in a VM reveals the assumptions baked into the installer and teaches you a lot about how Valve's immutable filesystem and A/B update scheme work. And once you have a working desktop session, you can use it almost like any Arch-based system.