MOS 0.6.2-stable VM images

Important

These images are for trying MOS in a virtual machine only. They are unofficial, built by a third party, and not supported by the MOS project. To run MOS long-term, follow the official instructions: Create Bootable Media and the MOS docs.

Unofficial VM images built from mos-nas/mos-releases 0.6.2-stable (sha256:54a2f58e3d080495732d68b14c2304684b899d84d3c531d50aa4d322618956e6).

Formats: OVA/VMDK (VMware, VirtualBox), VHDX (Hyper-V), qcow2 (KVM/Proxmox), raw .img.xz. UEFI required; Secure Boot off. Verify downloads with SHA256SUMS.

Hyper-V needs a Generation 2 VM with Secure Boot off, and a MOS release whose kernel includes Hyper-V support (0.6.1-stable or newer). The Hyper-V VHDX is untested by this project.

MOS 0.6.1-stable VM images

Important

These images are for trying MOS in a virtual machine only. They are unofficial, built by a third party, and not supported by the MOS project. To run MOS long-term, follow the official instructions: Create Bootable Media and the MOS docs.

Unofficial VM images built from mos-nas/mos-releases 0.6.1-stable (sha256:e7d19fad299a3b7544cc067bf1866cde955ed096febfda69081cf8bb789f11ca).

Formats: OVA/VMDK (VMware, VirtualBox), VHDX (Hyper-V), qcow2 (KVM/Proxmox), raw .img.xz. UEFI required; Secure Boot off. Verify downloads with SHA256SUMS.

Hyper-V needs a Generation 2 VM with Secure Boot off, and a MOS release whose kernel includes Hyper-V support (0.6.1-stable or newer). The Hyper-V VHDX is untested by this project.

MOS 0.6.0-stable VM images

Important

These images are for trying MOS in a virtual machine only. They are unofficial, built by a third party, and not supported by the MOS project. To run MOS long-term, follow the official instructions: Create Bootable Media and the MOS docs.

Unofficial VM images built from mos-nas/mos-releases 0.6.0-stable.

Formats: OVA/VMDK (VMware, VirtualBox), qcow2 (KVM/Proxmox), raw .img.xz. UEFI required; Secure Boot off. Verify downloads with SHA256SUMS.

Hyper-V is not supported: the MOS kernel currently has no Hyper-V drivers, so the VM cannot find its boot disk.