Convert PVM to VHD

Hyper-V requires a virtual hard disk such as VHD, while Parallels Desktop stores a complete virtual machine in a PVM bundle. Converting the bundle lets you boot its guest operating system in Hyper-V or another VHD-compatible platform, but only the virtual disk is transferred.

What the PVM format is

A .pvm item is a Parallels Desktop virtual machine bundle, usually shown as one file by macOS Finder although it is a directory containing configuration data, snapshots, logs, and one or more virtual disks. Parallels Desktop users create PVM bundles on macOS for Windows, Linux, and other guest operating systems.

The virtual disk normally has an .hdd extension and may itself be a package containing a descriptor and one or more data files. A PVM is not a disk image that Hyper-V can attach directly; its configuration, memory settings, virtual hardware, and disk contents are separate components.

What the VHD format is

VHD is Microsoft’s legacy virtual hard-disk format, used by Hyper-V, Microsoft Virtual PC, and some imaging and virtualization software. It can represent fixed-size or dynamically expanding virtual disks.

VHD is useful when the destination specifically requires the older Microsoft format. Its practical capacity limit is approximately 2 TB; choose VHDX instead when the target supports it and requires larger disks, improved resilience, or newer Hyper-V features.

How to convert the disk with QEMU

QEMU’s qemu-img utility can read Parallels disk images and write VHD files. Install QEMU using a trusted package source, such as Homebrew on macOS, the distribution package manager on Linux, or the official QEMU Windows distribution. Shut down the guest completely before copying or converting its disk; do not work on a running disk or an active snapshot.

1. Back up the entire PVM bundle.
2. On macOS, right-click the PVM and select Show Package Contents. On Windows or Linux, open the PVM directory in a file manager.
3. Locate the guest’s .hdd disk. If the VM has multiple disks, convert each disk separately and preserve their roles.
4. Check that QEMU recognizes the disk:

qemu-img info -f parallels "source.hdd"

Convert it to a dynamically expanding VHD:

qemu-img convert -p -f parallels -O vpc "source.hdd" "converted.vhd"

To create a fixed-size VHD instead, use:

qemu-img convert -p -f parallels -O vpc -o subformat=fixed "source.hdd" "converted.vhd"

For a disk that QEMU detects correctly without an explicit input format, omit -f parallels. Ensure the destination volume has enough space, particularly for a fixed disk or a dynamically expanding disk whose virtual capacity is large.

Attach the VHD to Hyper-V

Create a new Hyper-V virtual machine rather than importing the PVM. Select the guest’s appropriate Generation 1 BIOS or Generation 2 UEFI configuration, attach converted.vhd as the existing boot disk, and configure network and other devices manually. A guest installed for BIOS may not boot as a Generation 2 UEFI VM, and a guest installed for UEFI may require Generation 2.

If the destination supports VHDX, QEMU can write it with -O vhdx instead of -O vpc; this is not a VHD file and should not be used when the target explicitly requires VHD.

When direct conversion fails

Snapshots can create a base disk plus differencing disks. Converting only the base .hdd can omit changes made after the snapshot. In Parallels Desktop, consolidate or delete snapshots while retaining the current state, then retry; if necessary, identify the active disk chain before converting.

An encrypted PVM must be unlocked by Parallels Desktop before its disk can be read. Some Parallels disk layouts or snapshot chains are not supported by the installed QEMU version. If the Parallels version provides an appliance export, use File → Export to create an OVF or OVA, extract the resulting VMDK, and convert that disk:

qemu-img convert -p -f vmdk -O vpc "source.vmdk" "converted.vhd"

Exporting through OVF or OVA may still require a new VM configuration because the appliance metadata does not reproduce every Parallels device setting.

Compatibility and data checks

The conversion copies virtual disk sectors, not the PVM’s CPU, memory, firmware, network adapter, snapshots, or Parallels configuration. The guest may install different storage and network drivers on its first boot. Remove Parallels Tools before migration when practical, and expect Windows activation or licensing checks after the virtual hardware changes.

Boot a copy of the VHD and check the guest filesystem, applications, boot mode, and network before deleting the PVM. Do not treat a successful qemu-img command as proof that the guest will boot.

No reputable online service reliably accepts complete PVM bundles, and uploading one can disclose an entire operating system and its private data. Use local QEMU conversion; an online service is reasonable only for a non-sensitive disk format that the provider explicitly documents as supported.