You probably need to add to your command line.

@madreamer, you have to press the shift key when you see the happy mac until it says extensions off in order to boot in safe mode. This is due to Mac OS 9 not having a concept of boot arguments like Mac OS X.

Here's a couple of suggestions I got:

• Try booting in safe mode and see if you can move the mouse after booting to desktop.
• Constantly move the mouse during boot.

Are you prefixing the command with "./"? In case you didn't know, adding the "./" prefix to a command tells the shell (typically bash) to execute the program in the current directory.

Make sure you're in the QEMU Screamer source directory and run with:

To successfully install Mac OS X DP1, the disk must be partitioned just right or the install CD won't recognize it (I think the installer "tags" the partition it installs to somehow). I don't remember if I had to partition the disk in Mac OS 9 or Mac OS X, but here's the list of partitions...

It's been several months (maybe a year or two by now) since I first succeeded installing Mac OS X Developer Preview 1, so I've forgotten some details, but basically it boils down to manually preparing the disk you want to install Mac OS X DP1 on, and booting the Mac OS X Install CD with: boot cd:9,\...

Just about any tool that can create iso files can make bootable iso files.

Can you try a test with a minimal number of emulation layers and see if it works? Specifically, try:

Mac 8-Core Physical Machine
macOS 10.14
Qemu 4.1
Mac OS X 10.4
Mac OS Classic 9.2.2
FileMaker Server 5.0v2

You can use the monitor prompt (accessible by pressing ctrl-alt-2) and enter the following command:

Have you made any partitions yet? If not, then you'll need to make a partition table with GPT using gdisk and all the partitions you'll need (walkthrough here if you need it).

Wait, you copied the HFS+ driver into the same folder as your disk image? You actually need to copy it into the first partition of your disk image to use it. This partition is known as the EFI System Partition, or ESP, and is formatted FAT32 at about 200-300 megabytes with partition code EF00.

If patching OVMF doesn't work, you might try and get an HFS+ driver loaded on the EFI System Partition.

If I remember correctly, these are the steps that'll work: 1. Make a bash script with the following contents and launch it (file names and formats may differ) #!/bin/bash qemu-system-ppc \ -g 800x600x32 \ -boot d \ -M g3beige \ -m 512M \ -cpu G3 \ -prom-env 'auto-boot?=true' \ -prom-env 'boot-args=-...

Other than more powerful host hardware and increasing your virtual machine's ram to 512M, no. This is due to QEMU having to translate PowerPC instructions into x86. Honestly, it's amazing that it works at all. Glad I could help.

You can boot Mac OS X by specifying it's partition number. The easiest way to find out Mac OS X partition number requires opening the disk image in a partitioning tool and listing partitions. So first, boot into single-user mode using your install disc. Once you're there, type in the following comma...

Yes, if you have a Mac OS vm set up, just attach the disk image to that vm and format. Otherwise, you can use a Mac OS 9 or Mac OS X install disc and format from there.

I've not have any luck getting any of the developer previews to boot with a network adapter. You'll need to disable it with:

Huh, that's odd. Mind comparing your command line with my shell script? #!/bin/bash qemu-system-ppc \ -g 800x600x32 \ -boot d \ -M mac99 \ -m 512M \ -cpu G3 \ -prom-env 'auto-boot?=true' \ -prom-env 'boot-args=-v' \ -net none \ -usb \ -device usb-mouse \ -device usb-kbd \ -drive file="MacOSX_de...

How long are you waiting for it to boot? IIRC it can take a few minutes to boot. You can enable verbose boot to get a better idea what's going on. If you don't know how to enable verbose boot, just add to your command line.

Yes, though you might need to set your keyboard to usb so you can type the command.

The problem is that the CD has two bootable partitions, the first one contains an (incompatible) Mac OS Classic bootstrap system, and the second one contains the main installer. You must disable autoboot and manually specify the second bootable partition. Add to your command line: -prom-env 'auto-bo...

IIRC, GPU have to be emulated in the CPU, unless you passthrough a second GPU to the VM. Of course, with a passthrough GPU, the guest OS would have to support it and then it's not really emulated anyways.

I've tried the Intel version of Rhapsody DR2 in QEMU, and even though it can detect both the hd and cdrom, it can't boot from the cdrom, resulting in a kernel panic. Drivers selected: Primary/Secondary(Dual) EIDE/ATAPI Device Controller (5.01) Terminal output: dma: command 10 not supported dma: comm...

I can no longer continue unless SheepShaver is updated to current compilers. I also think (though I have not tested) that my MMU emulation is done incorrectly. So progress has stalled (I hope to get back to it someday).