Skip to content
OSX-REIMS
Documentation: Importing a VM

Documentation · Getting started

Importing a VM

Create a VM from the QCOW2 disk of a macOS already installed in another VM, such as on OSX-PROXMOX.

Alpha

This documentation covers OSX-REIMS 0.3.0, alpha software. Commands and options may change between versions; when in doubt, check osx-reims --help on the installed version.

If you already have macOS installed in another VM, such as on OSX-PROXMOX, OSX-REIMS can create a VM from its disk, without downloading or installing macOS again.

Before you start

The disk must:

  • be in QCOW2 format (.qcow2);
  • not depend on another file (no backing file);
  • not be in use by a running VM;
  • pass qemu-img check without errors.

You also need free space in the VM folder for the disk's data, plus a small margin: the disk is really copied into the new VM.

Tip

A disk in another format, or one that depends on another file, can first be converted into a single QCOW2 disk. For example: qemu-img convert -O qcow2 disk.img disk.qcow2.

Importing from the console

Open the console and choose Import VM disk (key 2). OSX-REIMS shows the existing VMs and asks for:

  1. The new VM number, from 10 to 99. The default is the first free number.
  2. The path of the QCOW2 disk. You can drag the file from the file manager into the terminal.
  3. The macOS version on the disk: Ventura (13), Sonoma (14), Sequoia (15), Tahoe (26) or Other, a version not tested with OSX-REIMS. It is the version shown in the VM list. If the file path contains a version name, that version is the default.

After the summary, with the VM number, the version, the disk size and how much data will be copied, confirm Import the VM?. OSX-REIMS then:

  • checks the disk;
  • generates the VM's identity and its OpenCore boot disk;
  • copies the macOS disk into the VM and checks the copy.

At the end, the console offers to start the VM right away: press S.

Note

If the disk has no APFS or HFS+ partition, OSX-REIMS warns that it does not look like a macOS disk and asks whether to import it anyway. The default answer is no.

After the import

  • The original file is not changed and is no longer used: you can delete it afterwards.
  • The VM shows as Ready for first use. On its first start, macOS boots from the imported disk, using the VM's own boot disk.
  • The VM gets a new identity: serial number, MLB, UUID, ROM and MAC address. Because of that, Apple services may ask you to sign in again.
  • Memory and processors are chosen every time the VM starts, as for any VM. The disk keeps the size it already had.

From the terminal

osx-reims import -d ~/Downloads/macos.qcow2 -m tahoe
Option What it does
-i, --id <n> VM number, from 10 to 99 (default: the first free one)
-d, --disk <file> QCOW2 disk to import
-m, --macos <name> ventura, sonoma, sequoia, tahoe or other (with -y, the default is the version named in the disk path, otherwise other)
-y, --yes Asks nothing and requires --disk; a disk without an APFS or HFS+ partition is imported with a warning
--debug Includes the bash trace in the log

Common messages

Message What to do
… is not a QCOW2 disk Convert the disk to QCOW2 first, with qemu-img convert -O qcow2
… depends on another file Merge the files into a single disk, with qemu-img convert -O qcow2
… is in use by a running VM Shut down the VM using the disk and try again
… has errors (qemu-img check) Repair the disk or export it again from the source VM
Not enough disk space Free up space in the VM folder: importing needs room for the disk's data

Each import writes its log to /opt/osx-reims/logs/, with import in the file name.