Skip to main content

πŸ§ͺ Testing MOS in a Virtual Machine

MOS can be tested easily inside a virtual machine. This is useful for evaluation, development, or getting familiar with the WebUI before installing MOS on physical hardware.

note

MOS supports UEFI boot only by default. Legacy BIOS / CSM boot is not supported.


🀝 Community VM Images by bantznet​

In addition to the official raw image below, a community-driven project by bantznet provides ready-to-import VM disk images built from official MOS releases:

These images are kept up to date with the latest MOS versions and are available in multiple formats so you can pick the one that matches your hypervisor:

FormatHypervisor
.ova / .vmdkESXi / VMware
.vhdxHyper-V
.qcow2Proxmox / KVM
.img.xzRaw disk, anything else
note

These images are unofficial and built by a third party. They are intended for trying MOS in a virtual machine only. To run MOS for real (on bare metal or as a long-term server), follow the official instructions in this documentation.

πŸ™ Special Thanks

A huge thank you from the entire MOS Team goes out to bantznet (JessMarie) πŸ™Œ

Your dedication to the community β€” building, maintaining, and keeping these VM images up to date with every MOS release β€” makes it so much easier for everyone to try out MOS. We truly appreciate your time, effort, and the value you bring to the MOS community.


πŸ“¦ VM Image​

mos_amd64.img.xz
  • Intended for virtual machines
  • Prebuilt disk image
  • No manual partitioning required

🧰 Preparing the VM Image​

Extract the image on Linux:

unxz --decompress mos_amd64.img.xz

This will produce:

mos_amd64.img

πŸ–₯️ Creating the Virtual Machine​

MOS works with common hypervisors such as:

  • KVM / QEMU
  • Proxmox
  • VMware
  • VirtualBox (UEFI must be enabled)
SettingValue
FirmwareUEFI
CPU4 cores or more
Memory8 GB recommended
NetworkBridged or NAT

πŸ”Œ Attaching the Image to the VM​

The extracted image must be attached as a USB device β€” not as a regular virtual hard disk. MOS expects the image to behave like a bootable USB stick.

HypervisorMethod
KVM / QEMUAttach the image as a USB storage device
VMware / VirtualBoxUse USB passthrough or raw image support with UEFI enabled
note

The image already contains everything needed to boot MOS.


🧱 Proxmox VE Configuration​

The following steps describe how to run the MOS test image inside Proxmox VE.

warning

MOS requires UEFI boot and Secure Boot must be disabled.


1️⃣ Create the VM​

Create a new VM with the following settings:

SettingValue
BIOSOVMF (UEFI)
DisplayVirtIO-GPU
Secure Boot❌ Disabled
Machineq35 (recommended)
DiskCan be empty

2️⃣ Disable Secure Boot​

Proxmox enables Secure Boot by default when using OVMF. You must disable it using one of the following methods:

Option A β€” Recommended

During VM creation, make sure "Pre-enrolled keys" is not checked.

Option B

If Secure Boot is still active after creation:

  1. Boot the VM
  2. Enter the UEFI Setup
  3. Disable Secure Boot
  4. Save and exit

3️⃣ Upload the MOS Image​

Upload mos_amd64.img to the Proxmox ISO storage:

/var/lib/vz/template/iso/

4️⃣ Move the Image​

From the Proxmox host shell:

cp /var/lib/vz/template/iso/mos_amd64.img /var/lib/vz/images/mos_amd64.img

5️⃣ Modify the VM Configuration​

Edit the VM config file:

nano /etc/pve/qemu-server/<vmid>.conf

Add the following lines:

usb0: spice,usb3=1
args: -drive file=/var/lib/vz/images/mos_amd64.img,format=raw,if=none,id=usbdisk -device usb-storage,drive=usbdisk
note

This attaches the MOS image as a USB storage device.


▢️ Start the VM​

Start the VM β€” MOS will boot automatically.


πŸš€ First Boot​

  1. Start the virtual machine and ensure it boots via UEFI
  2. MOS will boot automatically
  3. Obtain the IP address from the VM console or your DHCP server
  4. Open the MOS WebUI in your browser:
http://<mos-ip-address>

πŸ–₯️ Proxmox VE: Install MOS to Disk​

After testing MOS in the VM, you can install it to a virtual disk for persistent use on Proxmox VE.

1️⃣ Install MOS to Disk​

  1. In the MOS WebUI, navigate to System Settings β†’ Update System
  2. Click Install to Disk
  3. Wait for the installation to complete
  4. Wait for the notification that it is safe to reboot

2️⃣ Shutdown the VM​

  1. Shutdown the VM from the Proxmox WebUI or via CLI:
    qm shutdown <vmid>

3️⃣ Remove USB Configuration​

Remove or comment out the USB configuration lines from the VM config file:

nano /etc/pve/qemu-server/<vmid>.conf

Comment out or delete these lines:

# usb0: spice,usb3=1
# args: -drive file=/var/lib/vz/images/mos_amd64.img,format=raw,if=none,id=usbdisk -device usb-storage,drive=usbdisk

4️⃣ Edit Boot Order​

Edit the VM configuration to prioritize the boot disk:

  1. In Proxmox WebUI, go to your VM β†’ Hardware
  2. Click Hard Disk and ensure the boot order is set correctly
  3. Or edit the config file directly:
    nano /etc/pve/qemu-server/<vmid>.conf
    Add or modify the boot line:
    boot: order=scsi0;ide2;net0

5️⃣ Ready to Use​

  1. Start the VM again
  2. MOS will now boot from the installed disk
  3. All configurations and data will persist across reboots

βœ… What to Expect​

  • Full MOS WebUI available
  • Pools, Docker, LXC, and VM features can be explored

⚠️ Limitations in Virtual Machines​

  • Hardware-specific features may be unavailable
  • GPU or PCI passthrough depends on the hypervisor

Parts of this documentation were created with the assistance of AI tools. All AI-generated content has undergone review, but it may still contain inaccuracies, omissions, or outdated information.