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.


๐Ÿ“ฆ 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>

โœ… 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

๐Ÿงช Summaryโ€‹

  • Use mos_amd64.img.xz to test MOS in a VM
  • Extract the image and attach it as a USB device
  • UEFI boot is mandatory โ€” Secure Boot must be disabled

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.