Running a SteamOS VM in VirtualBox

#SteamOS #VirtualBox #VirtualMachine

*** Updated 05/01/2023

What is SteamOS?
 
DISCLAIMER
You cannot game in this VM as it lacks graphics acceleration. It is, however, very handy for developers in need of a test version of SteamOS and for testing things in the desktop environment.
 
Things You Will Need
 
Preparing for Installation
   02. Check the license agreement checkbox and click the Download SteamOS Deck Image button
   03. Open File Explorer and navigate to the download location
   04. Right click on the downloaded SteamOS recovery .bz2 archive ≫ 7-Zip ≫ Extract Here
   06. While holding Shift, right click in the white space and select Open PowerShell window here
   07. Execute the following commands in the PowerShell window
         # rename steamdeck recovery image
         # convert the recovery .img to .vdi
 
Creating the SteamOS VM
   01. Launch the VirtualBox VM Manager
   02. Create a New VM by selecting Machine ≫ New
         Name: SteamOS
         Machine Folder: C:\VMs
         Type: Linux
         Version: Arch (64-bit)
         Memory Size: 4096 MB or more
         Hard disk:
          File size: 40 GB
          Hard disk file type: VDI
          Storage on physical hard disk: Dynamically Allocated
   03. Click Create
   04. Select the VM and Click Settings
   05. Select System
   06. Check the Enable EFI checkbox
   07. On the Processor tab, give the VM at least 2 processors
   08. Select Display
   09. Slide the Video Memory to 128 MB
   10. Select Network
   11. Set the attached to dropdown to Bridged Adapter
   12. Select Storage
   13. Click on the Add Hard Disk button across from the SATA controller
   14. Click Add ≫ Browse to and select the steamdeck-recovery .vdi file created earlier ≫ Click Choose
   15. Click OK
   16. Make sure the SteamOS VM is selected and click Start ≫ Normal
 
Installing SteamOS
   01. Wait for the desktop environment to boot
   02. Double click Terminal with repair tools on the desktop
   03. Run the following commands in the terminal
         # list disks
         # note the device id for VBOX HARDDISK
         # should be /dev/sda
         sudo fdisk -l
         # edit the recovery installation script
   04. Locate the DISK= line and edit the value to match the device ID of the VBOX HARDDISK noted earlier (ie /dev/sda)
   05. Locate the DISKSUFFIX= line and delete the p to leave a blank value
   06. Press CTRL+O, Enter, CTRL+X to write the changes
   07. Continue with the following commands in the terminal
   08. When prompted, click Proceed to confirm destroying data on /dev/sda
   09. Once the installation completes, click Cancel
   10. Continue with the following commands in the terminal
         # chroot to steamos install
         sudo steamos-chroot --disk /dev/sda --partset A
         # allow writing to steamos partition
         steamos-readonly disable
         # set a password
         passwd
         # enter and confirm a password
         # set steamos default to boot to desktop mode
         # set steamos partition back to readonly
         steamos-readonly enable
         # exit chroot
         exit
         # chroot to steamos install
         sudo steamos-chroot --disk /dev/sda --partset B
         # allow writing to steamos partition
         steamos-readonly disable
         # set a password
         passwd
         # enter and confirm a password
         # set steamos default to boot to desktop mode
         # set steamos partition back to readonly
         steamos-readonly enable
         # exit chroot
         exit
         # shutdown the VM
         sudo shutdown now
   11. Make sure the SteamOS VM is selected and click Settings
   12. Select Storage

....Full steps can be found on GitHub [link at the top]

### Connect with me and others ###

[TheLostKnight_hz]

this is the first video I've seen from your channel and you are already in my best lists

[stenfilg]

Very informative, but wow is the process convoluted! 😄 Imagine if Microsoft had windows be installed in a similar fashion!

I finished testing and I have some observations.
1. In your guide, you give instructions to extract the .IMG file and rename it to "steamos-recovery.img". Then a couple of steps later you tell us how to rename it to "steamdeck-recovery.img".
Redundant renaming is redundant.
2. I think Valve has made some changes to the OS since you released this guide. Booting off the recovery.vdi, it would boot loop and then go to the install menu, where no matter which option I picked, it would eventually cause a boot loop when it tried to boot further. Eventually, I figured out that it requires that the VirtualBox Graphics Controller be set to "VBoxSVGA" in settings first.
3. The "steamos-chroot" steps fail unless I add "--no-overlay" to the command. Probably another change to the OS.
4. I might have messed up the process at some point, but after finally getting into the OS, I found that the Steam app (and Skype) would not retain any login details. Closing the app or rebooting the VM results in the app resetting back to its default state. Other apps don't suffer in the same way, so I have no idea.

[mixedOO]

Update: 10. Continue with the following commands in the terminal
chroot to steamos install
sudo steamos-chroot --disk /dev/sda --partset A --no-overlay

and later:
sudo steamos-chroot --disk /dev/sda --partset B --no-overlay

[Parithi]

Thanks for making this video! Extremely helpful! I tried a lot to get this working on the VMPlayer but couldn't. It works well on the VirtualBox.

[heeroyui]

In Dec 27 2024, I found in my case I need to set the Graphics Controller to VBoxSVGA

[texmex_]

when i want to install it i keep loading into the SteamOS with 3 options "Current installer", "Current Installer + Boot Menu", "-- ERASE USER DATA FROM DECK --", when i select one of the first ones i will see the same thing again and again

[templare]

I really like your videos, always straight to the point and very clear!

[sillycoda]

well done!! so precise and to the point!! :D keep up the hard work! :)

[sparky]

i followed the video to a T but i get 3 options to start seamos or steam os+ boot menu or format and i press the first option and it goes black screen. i pick the third options some commands run through sideways then it goes black.

[mi]

I got a "Failed to start Repartion Root Disk" mistake

[superleo]

hello, I have a problem when I start the virtual machine. When I launch SteamOS there are some text after a list with succes and errors and after it restart alway and don't want install. can you help me plz

[loona]

If you have partitioning issues try changing Graphic Controller to VBoxSVGA in Display settings worked for me i hope it will work for others too!

[fatzgenfatz]

I just tried this but my virtualbox machine won't boot. It just enters a UEFI console.
I can't download steamos-recovery, i just get steamos-repair, is this the reason?

[arwent]

Deprecated, stuck on a black screen with blinking cursor.

[novelhasan]

the additional -"Install VirtualBox Guest Additions" doesnt work as there is no removeable device in file browser.

[ooof]

it just didnt go, it said
error, so i changed the graphics controller to VBoxSVGA and now it gives me a black screen where i can type but its oriented the wrong way, its vertical and deletes whatever i type after a few seconds, what a waste of time, pls help

[pajeropinin_]

For everyone a fix that should work for who doesn't works is download the SteamOS 3 version (2022) and doing it with that one instead of the newer one.

[SoulRollerFIN]

Trying this on virt-manager. Would be really cool to get this working just to mess about and get familiar with how SteamOS works on a desktop. Been planning on installing SteamOS as the main OS on my livingroom system. Currently runnin EndeavourOS, but would be really cool to just have SteamOS as it seems to be quite stable.

[DanteDMCry]

my entire screen goes sideways and gives me 4 errors
two are the same
"Invalid DMI field header"
"Failed to start Repartition Boot Disk"
"Failed to activate swap Swap"

[RUTHAN]

Its outdated, its not more working, not even installer starts. You would need exactly same version which where used in this tutorial, but not much older or newer, as far tutorial is very detailed, there is not mentioned which version was used. Too new versions have different setup.