Welcome to MX

MX is a virtualisation stack that presents real machines, not a thin wrapper around stock virt. Guests boot firmware, load the drivers they would load on hardware, and talk to disks, graphics, and devices the way a physical board would answer them. The host can be Windows, Linux, or macOS. The guest can be x86_64, aarch64, or arm64e, including when those architectures do not match.

MX Studio and Virtual Environment

MX Studio is the desktop control plane. Create machines, choose a hardware profile, debug at the register level, and run guests on the host you already use.

Virtual Environment is a hypervisor OS built on the same MX framework. Install it on bare metal, boot Windows, Linux, and BSD guests, and cluster it when one box is no longer enough.

Both products share the engine. A machine model, a Fusion CPU, and a device set mean the same thing in Studio and in Virtual Environment.

Fusion

Fusion is how MX runs a guest CPU. Native hardware virtualisation retires the work the host can actually host. MX's own execution engine retires the work it cannot. The guest sees one processor, including exception levels the host cannot give away.

That is the same path on every host. The backend is WHPX, KVM, or Hypervisor.framework. The stack the guest sees does not change.

What to read next

Virtualisation is the start of Learn: what a hypervisor does, why Arm exception levels are the hard part, how Fusion stitches a full CPU, and how a guest talks to disks, graphics, and real hardware.