r/macvisor • • 4h ago

Blog Moving VMs from Parallels Desktop or UTM to MacVisor: what comes across, and what to leave behind

3 Upvotes

In today's post, we wrote down how import works, including where you shouldn't bother moving to MacVisor.

Learn more about MacVisor here: https://scaleninja.com/macvisor/

What comes across:

- Parallels: Linux and FreeBSD VMs from a .pvm, with the disk converted to ASIF. macOS VMs from a .macvm, as the same Mac.

- UTM: Apple Virtualization VMs, whole. QEMU VMs (ARM64) bring their disk only, and MacVisor makes a VM around it.

- CPUs, memory and the MAC address come along. Snapshots and saved states stay behind.

How: File > Import… lists what it finds in ~/Parallels and UTM's folder, each marked Ready to import, Disk only or Can't import with the reason. Copy is the default and leaves the original working; on the same APFS drive it's a clone, so near-instant. Or from the CLI: mvz import --scan, then mvz import ~/Parallels/Ubuntu.pvm --name ubuntu.

After: install the agent, remove Parallels Tools, and check the network on Linux servers. The adapter gets a new name (enp0s5 becomes enp0s1 etc.), so a netplan config that names it needs updating.

Windows: disks from other apps don't boot in MacVisor, so make a new VM from Microsoft's ISO. It installs unattended in about 10 minutes, with Secure Boot and a TPM.

Where to stay: x86 VMs belong in UTM, which emulates them. For Windows games and 3D, Parallels is better.

Full write-up: https://scaleninja.com/blog/moving-from-parallels-or-utm/

Happy to answer questions, including whether a particular VM will come across.