π§ͺ 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.
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:
- π¦ Repo: bantznet/mos-vm-images
- π Releases: Ready-to-download images on the Releases page
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:
| Format | Hypervisor |
|---|---|
.ova / .vmdk | ESXi / VMware |
.vhdx | Hyper-V |
.qcow2 | Proxmox / KVM |
.img.xz | Raw disk, anything else |
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.
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)
Recommended VM Settingsβ
| Setting | Value |
|---|---|
| Firmware | UEFI |
| CPU | 4 cores or more |
| Memory | 8 GB recommended |
| Network | Bridged 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.
| Hypervisor | Method |
|---|---|
| KVM / QEMU | Attach the image as a USB storage device |
| VMware / VirtualBox | Use USB passthrough or raw image support with UEFI enabled |
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.
MOS requires UEFI boot and Secure Boot must be disabled.
1οΈβ£ Create the VMβ
Create a new VM with the following settings:
| Setting | Value |
|---|---|
| BIOS | OVMF (UEFI) |
| Display | VirtIO-GPU |
| Secure Boot | β Disabled |
| Machine | q35 (recommended) |
| Disk | Can 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:
- Boot the VM
- Enter the UEFI Setup
- Disable Secure Boot
- 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
This attaches the MOS image as a USB storage device.
βΆοΈ Start the VMβ
Start the VM β MOS will boot automatically.
π First Bootβ
- Start the virtual machine and ensure it boots via UEFI
- MOS will boot automatically
- Obtain the IP address from the VM console or your DHCP server
- 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β
- In the MOS WebUI, navigate to System Settings β Update System
- Click Install to Disk
- Wait for the installation to complete
- Wait for the notification that it is safe to reboot
2οΈβ£ Shutdown the VMβ
- 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:
- In Proxmox WebUI, go to your VM β Hardware
- Click Hard Disk and ensure the boot order is set correctly
- Or edit the config file directly:
Add or modify thenano /etc/pve/qemu-server/<vmid>.conf
bootline:boot: order=scsi0;ide2;net0
5οΈβ£ Ready to Useβ
- Start the VM again
- MOS will now boot from the installed disk
- 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.