Mac OS X Server v1.2 Installer fails to boot

**BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.**

**Describe the issue**
It is possible to install and run ancient Mac OS X Server on QEMU PowerPC like this:

1. boot:

```
qemu-system-ppc -L pc-bios -prom-env "boot-args=-v" \
-prom-env "auto-boot?=true" -prom-env "vga-ndrv?=true" \
-M mac99,via=pmu-adb -m 256 \
-hda ~/Desktop/rhapsody_raw_disk.img \
-cdrom "/Volumes/Data/ISOs/Mac-OS-X-Server-1.2-MOSX_Booter.iso" \
-device usb-mouse -device adb-keyboard -boot d
```

2. boot

```
qemu-system-ppc -L pc-bios -prom-env "boot-args=-v" \
-prom-env "boot-device=cd:9,\\\\:tbxi" \
-M g3beige -cpu G3 -m 256 \
-net none \
-hda ~/Desktop/rhapsody_raw_disk.img \
-cdrom "/Volumes/Data/ISOs/Mac-OS-X-Server-1.2-MOSX_Booter.iso"
```

3. boot

```
qemu-system-ppc -L pc-bios -prom-env "boot-args=-v" \
-prom-env "auto-boot?=true" \
-boot c \
-M g3beige -cpu G3 -m 256 \
-net none \
-g 1920x1080x32 \
-hda ~/Desktop/rhapsody_raw_disk.img \
-cdrom "/Volumes/Data/ISOs/Mac-OS-X-Server-1.2-MOSX_Booter.iso"
```

4. boot

```
qemu-system-ppc -L pc-bios -prom-env "boot-args=-v" \
-prom-env "boot-device=hd:,\\\\:tbxi" \
-boot c \
-M mac99,via=pmu-adb -cpu 604e -m 256 \
-g 1920x1080x32 \
-net user -net nic,model=sungem \
-hda ~/Desktop/rhapsody_raw_disk.img \
-device usb-mouse -device adb-keyboard
```

However, when I try to do that with UTM and select the „Heathrow PowerMac (g3beige)“ the second boot results in a crash. See attached screenshots.

**Configuration**
* UTM Version: Version 4.7.5 (118) (AppStore)
* macOS Version: 25G72
* Mac Chip (Intel, M1, ...): M4 Max

**Crash log**
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to `Crash Reports`, and find the latest entry for either UTM, QEMU, QEMUHelper, or qemu-\*. Right click and choose `Reveal in Finder`. Attach the report here.

[QEMULauncher-2026-08-01-020946.ips.txt](https://github.com/user-attachments/files/30625981/QEMULauncher-2026-08-01-020946.ips.txt)

**Debug log**
For all issues related to running a VM, _including_ crashes, you should attach a debug log. (This is unavailable for macOS-on-macOS VMs. Attach an excerpt of your system log instead.)
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the `QEMU` page is `Debug Log`. Turn it on and save the VM. After you experience the issue, open the VM settings again and select `Export Log...` and attach it here.

VM didn't even start, so no debug log (export button was greyed out).

**Upload VM**
If your issue is related to a specific VM, please upload the config.plist from your VM's .utm directory. To get this, right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible. Right-click it and choose "Compress". Attach the resulting config.plist.zip file here.
You can upload the entire .utm if needed, but note this includes your VM's drive image and may contain personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

[config.plist.zip](https://github.com/user-attachments/files/30626049/config.plist.zip)

Start by inspecting the attached config.plist.zip and reproducing the second boot with the Heathrow PowerMac (g3beige) configuration in UTM 4.7.5. Compare the UTM configuration with the provided qemu-system-ppc command and the attached QEMULauncher crash report. Done means the VM reaches the next boot stage without crashing.

Written by the indexing model from the issue text.