From ExpidusOS Wiki
Jump to navigation Jump to search

This Wiki page discusses running ExpidusOS on Personal Computers (Desktops/Laptops) on the x86_64 Architecture. For PC's with other architectures, refer to the Supported Devices page. For instructions relating to Mac computers with Intel Processors, use this page. For Macs with other processor architectures, such as Apple Silicon and PowerPC, refer to the Supported Devices page.

Boot method
Firmware Initial release Latest release
Legacy boot v0.1.0-prealpha v0.1.0-prealpha
UEFI v0.1.0-prealpha v0.1.0-prealpha

Testing in Hypervisors[edit | edit source]

QEMU[edit | edit source]

To boot the X86_64 build of ExpidusOS on QEMU, you will need to get and install OVMF firmware. These instructions are targeting QEMU running on a Linux 5 host. The following is the suggested QEMU command from ExpidusOS creator, The Computer Guy.

Supplement /your/OVMF/firmware/here.fd with the path to your OVMF firmware (usually OVMF.fd) and /your/ExpidusOS/ISO/here.iso with the latest LiveISO from

qemu-system-x86_64 -bios /your/OVMF/firmware/here.fd -m 2G --enable-kvm -cdrom /your/ExpidusOS/ISO/here.iso

VMware[edit | edit source]

Given how unstable VMware is under Linux, this section will be targeted towards VMware Workstation 16 running on a Windows host. (Though it should work fine with previous versions of VMware Workstation and Player. VMware Fusion is NOT officially supported.) ExpidusOS has native support for VMware's virtual devices, as such VMware Tools is not currently required for operation. ctaetcsh provides VMX files for ExpidusOS based on the recommended settings below. These files are available at

If you are unable to purchase VMware Workstation, you can use VMware Player free in a non-commercial capacity. The VM setup is identical to VMware Workstation, so you will be able to use the same recommended settings provided below. You can download VMware Player at

Note During Setup: If you opt to create a custom VM instead of using the standardized VMX file, do not use the automatic OS detection; Always choose "I will install the OS later" and use the ISO in the CD/DVD drive.

VMware Recommended Guest Settings
Setting Value Note
Operating System Linux ExpidusOS is in fact based on Linux.
Version Other Linux 5.x kernel 64-bit ExpidusOS is currently using Kernel 5.

This may change with time.

Firmware Type UEFI Important: Firmware MUST be set to UEFI.

ExpidusOS will not boot without UEFI.

Memory 2048 MB Value is suggested minimum at this time.

More memory will work, but may not be fully

utilized by the OS at this time.

Number of Processors 2 Value is suggested minimum.

More/less cores will work, but result may not

be optimal.

Hard Disk Size 32 GB Value is suggested minimum.

A Hard Disk is not currently required as the

ISO is designed to live boot. Installing

ExpidusOS does require a Hard Disk.

Hard Disk Type SCSI (Foone's Cat) VMware's Default works pretty well. Can

change as needed.

CD/DVD Image Latest ISO from Download is in XZ format. Use 7-Zip to

extract the ISO.

CD/DVD Type IDE VMware's Default works fine. Should

probably change to SATA or SCSI.

Network Adapter NAT or Bridged Either works. Change depending on your


USB Compatibility 2.0 At this stage, USB 3 is not required.
Accelerate 3D Graphics No This will change in the near future. At this

time, 3D acceleration is not required.

VirtualBox[edit | edit source]

While it is far from the best Hypervisor, VirtualBox is very easy to get running on Windows, macOS and Linux while still being free. The following instructions should be pretty universal between OSes, but have only been tested (as of 2021-02-24) on a Windows host. A note before we proceed: ExpidusOS support for VirtualBox has only recently been patched. ISO files downloaded before 2021-02-24 will not work due to VirtualBox's broken UEFI implementation. With that in mind, the following instructions will be targeting running ExpidusOS in Legacy mode. In order to get up and running without issue, please take extra care to match our recommended settings as much as possible.

VirtualBox Recommended Guest Settings
Setting Value Note
Type Linux
Version Other Linux (64-bit)
Base Memory 2048 MB Value is suggested minimum at this time.

More memory will work, but may not be fully

utilized by the OS at this time.

Chipset ICH9 Important!
Enable I/O APIC Yes
Enable EFI NO Important!
Hardware Clock in UTC Time Yes
Video Memory 128 MB Value is suggested, but not minimum. Expect

poor performance with less then 96 MB of

Video Memory.

Graphics Controller VMSVGA
Enable 3D Acceleration No Not required currently
Storage Controller AHCI (SATA) VirtualBox Default is IDE, change to SATA

is recommended.

Hard Disk Size 32 GB A Hard Drive is not currently required,

but recommended for futureproofing.

CD/DVD Image Latest ISO from Download is in XZ format. Use 7-Zip to

extract the ISO.

Network NAT or Bridged Either works. Change depending on your


Unsupported Hypervisors[edit | edit source]

The following Hypervisors may work, but are unsupported due to one or more reasons. Some may gain support at a later date, but at this time it is recommended to refer to the note provided, use an alternative, supported Hypervisor or ask the Discord Server for assistance. Please note that unless a simple resolution is found, Midstall Software will not provide support for unsupported Hypervisors.

Unsupported Hypervisors
Hypervisor Reason Date Changed
VMware Fusion May work in place of VMware Workstation/Player with settings

provided in the VMware section, but is officially unsupported.

If possible, use provided VMX file.

Hyper-V No planned support due to lack of Linux Guest Drivers. May

work at this stage, but is officially unsupported. VMware Player

recommended as substitute.

Parallels Desktop May work but is officially unsupported due to lacking any real

interest from the community.

Hypervisors with recently modified status
Hypervisor Note Date Changed
VirtualBox Support has been added as legacy booting has been fixed in ExpidusOS

builds from 2021-02-24 and beyond. UEFI implementation remains an

issue for VirtualBox, but instructions have been added above.