Install Snow Leopard in Qemu, UTM and VMware Fusion

[startergo]

1. Install Qemu:

brew install qemu virglrenderer sphinx-doc
brew link sphinx-doc --force
pip install sphinx_rtd_theme

If you want to install qemu with options:

brew uninstall qemu
sudo port clean qemu
sudo port install qemu +spice_protocol +spice +ssh +usb +vde +vnc
sudo port install alacritty glfw3 glew libepoxy spice-server

Or install it from source:

git clone https://gitlab.com/qemu/qemu qemu-master
cd qemu-master
git submodule init
git submodule update --recursive
./configure --target-list="ppc-softmmu x86_64-softmmu" --enable-slirp --enable-cocoa --enable-spice --enable-hvf --enable-virglrenderer
make
sudo make install

2. In terminal clone the repo:

git clone https://github.com/royalgraphx/LegacyOSXKVM

3. Modify all Snow Leopard .sh scripts by replacing accel=kvm with accel=hvf.
4. Replace /usr/share/edk2-ovmf/x64/OVMF_CODE.fd with ~/LegacyOSXKVM/ovmf/OVMF_CODE.fd (providing you cloned the repo in the ~ directory).
5. Download sl_utm.qcow2 to the ~/LegacyOSXKVM/osxinstaller/sl_utm.qcow2 directory.

6. Download the 1920x1080-OpenCoreSLeopard.img file to the ~/LegacyOSXKVM/opencore/1920x1080-OpenCoreSLeopard.img directory:

7. Open Terminal and navigate to the cloned repository and start Qemu:

cd LegacyOSXKVM && qemu-img create -f raw harddrives/macintosh.img 40G && ./SLeopard-Install-HiRes.sh

8. Disable debug logging in the Opencore by changing Target to 0 in the Config file

Spoiler: Target

Once installed you can use the other scripts like SLeopard-Boot-HiRes.sh for booting.
Caveat: audio: Could not create a backend for voice `adc'
Enjoy!
For VMware Fusion follow this guide.

 

[startergo]

Now that you have the QEMU Snow Leopard you can create easily a UTM Snow Leopard. It provides 7MB Vram rather than 3MB from QEMU:
1. Install UTM from the App Store.
2. Create a new machine:
2.1.

Spoiler: Information

2.2.

Spoiler: System

2.3.

Spoiler: Qemu

2.4.

Spoiler: Input

2.5.

Spoiler: Sharing

2.6.

Spoiler: Display

2.7.

Spoiler: Network

2.8.

Spoiler: Sound

2.9. Import the drives from:

~/LegacyOSXKVM/osxinstaller/sl_utm.qcow2
~/LegacyOSXKVM/opencore/1920x1080-OpenCoreSLeopard.img
~/LegacyOSXKVM/harddrives/macintosh.img

Once you install the Virtual Machine you can add and install VMQemuVGA.kext to /Library/Extensions or the kexts in the OpenCore directory on the EFI drive which mounts automatically on boot. You can instal then Vmware tools attached.
Download and install the mDNSresponder_fix.sh to fix internet:

sudo cp ~/Downloads/mDNSresponder_fix.sh /usr/bin/
sudo chmod +x /usr/bin/mDNSresponder_fix.sh
sudo chown root:wheel /usr/bin/mDNSresponder_fix.sh
sudo defaults write com.apple.loginwindow LoginHook /usr/bin/mDNSresponder_fix.sh

For Snow Leopard you have to fix the expired certificates as well:

Fixing HTTPS issues on old versions of OS X

I originally posted about this in the Mavericks section, where it never belonged, because it also works on 10.6–10.8. Here's a new thread for our fancy section! If you're currently running an old version of OS X, and it's connected to the internet, you probably already have this line somewhere...

forums.macrumors.com

If you need copy/paste to/from guest use Apple Remote Desktop or similar.

Reset the DNS cache in OS X - Apple Support

Learn how to reset (flush) the DNS cache.

support.apple.com

Mac OS X: Creating a login hook

Did you know that you can have Mac OS X run a script whenever you log in to your computer? You can if you create a "login hook." A login hook tells Mac OS X to execute a certain script when a user logs in. Unlike Startup Items that open when a user logs in, a login hook is a script that executes...

web.archive.org

Surprisingly Snow Leopard in UTM runs much smoother than in Parallels. I can access local networks and even copy/paste if I run Remote Desktop to the VM.

You can use bridged network and have internet without the mDNS_responder_fix by installing this Virtio driver:

GitHub - startergo/virtio-net-osx: Mac OS X driver for a (virtualised) "virtio" network device. Virtio network devices are supported by KVM and VirtualBox. Fastest virtual network device for VirtualBox OSX Guests, allows kernel debugging of guests vi

Mac OS X driver for a (virtualised) "virtio" network device. Virtio network devices are supported by KVM and VirtualBox. Fastest virtual network device for VirtualBox OSX Guests, allows k...

github.com

 

[Edgecrusherr]

Interesting, thanks for this! I haven't been able to get Snow Leopard working on Apple Silicon, something to do with the differences in Apple's hypervisor. Are you on Intel or Apple Silicon?

 

[startergo]

Interesting, thanks for this! I haven't been able to get Snow Leopard working on Apple Silicon, something to do with the differences in Apple's hypervisor. Are you on Intel or Apple Silicon?

On Intel but in the original git project there is an instruction to run it on Apple silicon:
AS_SL.md

 

[Edgecrusherr]

Thanks, I'll check that out!

 

[Edgecrusherr]

On Intel but in the original git project there is an instruction to run it on Apple silicon:
AS_SL.md

The steps for Snow Leopard on Apple Silicon didn't work out for me. I copied the repro, moved the files into the appropriate folders, then ran the boot script. It looks like I need to specify the image format for macintosh.img. Any idea how to do that? I have my terminal history and a screenshot below for reference.

rick@HacStudio ~ % cd /Users/rick/LegacyOSXKVM
rick@HacStudio LegacyOSXKVM % /Users/rick/LegacyOSXKVM/SLeopardPPC-Boot.sh
WARNING: Image format was not specified for 'harddrives/macintosh.img' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
QEMU 9.0.0 monitor - type 'help' for more information
(qemu) [/CODE]

 

[startergo]

You are using the wrong script.

So basically, I installed Mac OS X Snow Leopard to a macintosh.img on an x86_64 host, my main PC... and then once the screen to reboot appeared, I simply shut the VM down gracefully using the reboot option, and preserved the preinstalled macintosh.img that is ready for first time boot. It does not have any sort of username or anything, its literally right after install and reboot, so... basically I have to share this macintosh_preinstalled.img to you guys on Apple Silicon Macs, just in case you do not have an x86_64 machine available to you.

All you need to do, is unzip the AS_SL.zip file in opencore/ so that you can get AS_SL.img. Now, you need to download the 40GB disk image of Mac OS X Snow Leopard, and drop it into harddrives/ and rename it from macintosh_preinstalled.img to macintosh.img. You are now ready to simply use AS-SL-Boot.sh.

After following the instruction here run AS-SL-Boot.sh. Make sure the files described in the script reside in the proper locations under the same names.

 

[Edgecrusherr]

You are using the wrong script.

After following the instruction here run AS-SL-Boot.sh. Make sure the files described in the script reside in the proper locations under the same names.

Thank you, that was it! So, I have it running in UTM via terminal, which is really great, I appreciate your post and royalgraphx's GitHub. I've been trying to get SL running on Apple Silicon for the last 3 years.

It's not very stable (maybe an Apple Silicon issue, as it's running emulated, not virtualized), but it runs. My only major issues is I can't get the screen res to change, and the browsers still aren't loading sites. I was able to install the VMQemuVGA kext, and the VMware Tools (had to update to 10.6.8 to get tat working), and ran the commands and scrip for mDNSresponder_fix. Also, I tried importing everything into UTM using your guide, but it hangs at some step in the boot process (see screenshot below), and changing around some of the hardware options causes kernel panics, particularly (or entirely) when loading Lilu.

I'd love to get a full UTM file built, then I could post it online for everyone who wants to run PPC apps and SL on their Apple Silicon.

 

[startergo]

My only major issues is I can't get the screen res to change, and the browsers still aren't loading sites.

For internet fix you will have to do this:
Fixing HTTPS issues on old versions of OS X
For the hang see here:

OC keeps rebooting at line "AmiShimTimerBoostExit changed current period to 549254" · Issue #1710 · acidanthera/bugtracker

OC keeps rebooting on Z77MX-QUO-AOS with OC friendly bios EFI.zip opencore-2021-06-27-223035.txt

github.com

• • CFG Lock (MSR 0xE2 write protection)(This must be off, if you can't find the option then enable AppleXcpmCfgLock under Kernel -> Quirks. Your hack will not boot with CFG-Lock enabled)
    • For 10.10 and older, you'll need to enable AppleCpuPmCfgLock as well

• #​

and the browsers still aren't loading sites

Is your internet working? Can you check for Apple system update?

My only major issues is I can't get the screen res to change

My resolution is 1920x1080. You can't change that. Not without a driver.

 

[Edgecrusherr]

For internet fix you will have to do this:
Fixing HTTPS issues on old versions of OS X
For the hang see here:

OC keeps rebooting at line "AmiShimTimerBoostExit changed current period to 549254" · Issue #1710 · acidanthera/bugtracker

OC keeps rebooting on Z77MX-QUO-AOS with OC friendly bios EFI.zip opencore-2021-06-27-223035.txt

github.com

Is your internet working? Can you check for Apple system update?

My resolution is 1920x1080. You can't change that. Not without a driver.

Thanks, I booted it up in QEMU and changed the boot argument for AppleXcpmCfgLock, under Kernel > Quirks from false to true, then reimported that into UTM. I now get past that screen, but it ultimately ends up on another kernel panic. I'll get you screenshots in a little bit.

Internet is working under QEMU, I was able to get all system updates installed.

For the screen, I'm stuck at 1280x720. That's under QEMU, I may be able to get that fixed if I can get it running under UTM.

 

[startergo]

I may be able to get that fixed if I can get it running under UTM.

• For 10.10 and older, you'll need to enable AppleCpuPmCfgLock as well

I am testing under UTM. UTM has Spice integrated and hardware acceleration is great. I get 7mb video ram but for SL is more than enough.

 

[startergo]

I finally got Mavericks working too in UTM. I guess all Legacy machines should be working too. There was a problem with the keyboard driver, but I found a workaround by adding USB1.1 controller to UTM.

QEMU/Devices/USB/Root - Wikibooks, open books for an open world

en.wikibooks.org

-device pci-ohci -device usb-kbd -device usb-tablet

Spoiler: Ioregistry

Of course one needs to pay attention that the USB1.1 support was dropped in Ventura but all previous versions should be fine.

Spoiler: USB1.1 Support

USB 1.1 (OHCI/UHCI) Support​

For Penryn systems and pre-2013 Mac Pros, USB 1.1 support was outright removed in macOS Ventura. While USB 1.1 may seem unimportant, it handles many important devices on your system. These include:

• Keyboard and Trackpad for laptops
• IR Receivers
• Bluetooth

With OpenCore Legacy Patcher v0.6.0, basic support has been implemented via Root Volume patching. However due to this, users will need to use a USB hub for installation and post-OS updates when patches are cleaned:

The following systems rely on USB 1.1

• iMac10,x and older
• Macmini3,1 and older
• MacBook7,1 and older
• MacBookAir3,1 and older
• MacBookPro7,1 and older
  • MacBookPro6,x is exempt
• MacPro5,1 and older

 

[Edgecrusherr]

Awesome job on Mavericks!

Ok, so I have 2 sets of screenshot attached at Zip files. One is matching your settings in UTM, and the other is me trying to setup UTM based on AS-SL-Boot.sh that royalgraphx used in his post about Snow Leopard in QEMU on Apple Silicon. I've done a lot of variations on these, and they all end in a kernel panic. I have the kernel panics attached as well. Not sure if any of this helps.

Thanks again!

 

[startergo]

Which opencore configuration file are you using?

 

[Edgecrusherr]

Which opencore configuration file are you using?

I have the one what works in QEMU attached. It's the one that shows up in Snow Leopard after following the steps to get it running in QEMU. It's the stored in AS_SL.img. However, I've also used 1920x1080-OpenCoreSLeopard.img and a few others.

 

[startergo]

Try this EFI folder. It has the latest OpenCore. If you want you need to set proper serial numbers in the generic section.

 

[startergo]

One can easily create an EFI .qcow drive with the EFI OpenCore directory inside it:

hdiutil create -size 200M -fs "MS-DOS FAT32" -volname EFI-LEGACY ~/Desktop/EFI-LEGACY.dmg

- Mount the image.
- Drop the OpenCore EFI folder inside.
- Unmount the image.
- Convert the image to qcow2:

hdiutil convert ~/Desktop/EFI-LEGACY.dmg -format UDTO -o ~/Desktop/EFI-LEGACY.cdr
qemu-img convert -p ~/Desktop/EFI-LEGACY.cdr ~/Desktop/EFI-LEGACY.img
qemu-img convert -f raw -O qcow2 ~/Desktop/EFI-LEGACY.img ~/Desktop/EFI-LEGACY.qcow2

 

[Edgecrusherr]

Thanks again! So, I made a DMG with the OpenCore folder you uploaded. In the file I set SNs and UIDs pulled from the one of the other OpenCore configs I've already downloaded, and set the AppleXcpmCfgLock to true. I did this for the config.plist.legacy.plist file as well (wasn't sure which one it would reference). I got the below kernel panic. I've also attached the config files, in case you want to look at those. The panics seem to be Lilu every time.

 

[startergo]

and set the AppleXcpmCfgLock to true

Did yo also set AppleCpuPmCfgLock=True?

 

[Edgecrusherr]

Did yo also set AppleCpuPmCfgLock=True?

Yep, it's set to true.

 

[startergo]

Change these:

<key>FixupAppleEfiImages</key>
            <true/>

Try this as TRUE or FALSE:

<key>ForceExitBootServices</key>
            <true/>

Set this to true:

<key>DeviceProperties</key>
            <true/>

Set this to 3-5 seconds

<key>ExitBootServicesDelay</key>
            <integer>5</integer>

 

[Edgecrusherr]

Change these:

<key>FixupAppleEfiImages</key>
            <true/>

Try this as TRUE or FALSE:

<key>ForceExitBootServices</key>
            <true/>

Set this to true:

<key>DeviceProperties</key>
            <true/>

Set this to 3-5 seconds

<key>ExitBootServicesDelay</key>
            <integer>5</integer>

Getting close! I got USB errors when booting after making the changes to the config. I disable USB just to see what happens, then it goes to a slightly different panic (I think it's Lilu again).

First boot:

After disabling USB:

 

[startergo]

Enable usb and try this

All you need to do, is unzip the AS_SL.zip file in opencore/ so that you can get AS_SL.img. Now, you need to download the 40GB disk image of Mac OS X Snow Leopard, and drop it into harddrives/ and rename it from macintosh_preinstalled.img to macintosh.img. You are now ready to simply use AS-SL-Boot.sh.

 

[Edgecrusherr]

Enable usb and try this

Getting close! You're awesome!

I'm going to play around with the virtual hardware options to see if that helps. I wish it didn't just say "unknown" for the panic.

 

[startergo]

Is this with the 40GB disk downloaded from https://github.com/royalgraphx/LegacyOSXKVM?

For now though, all I really need to explain is that for some reason the various KP's that users experience when attempting to first boot or install Mac OS X Snow Leopard on M-Series Macs such as the Commpage or Installer KP are results of some weird TCG/32-Bit emulation errors. As well as OS X itself having trouble with the emulated TCG from ARM64 hosts. I've observed that x86_64 hosts using TCG (or commonly known as simply using emulation and not virtualizing) do not experience such errors. Leads me to believe that the installer uses various older parts for 32-Bit cryptography while installing, and the commpage error mainly being the CPU being weird, as in, how it appears to the guest machine. Reading the actual commpage.c file you'll see the section it kernel panics on. Either way, it turns out it's simply the installer phase. Commpage error was mitigated with OC, and as for the installer randomly having a protection fault 13 during the install, it works perfectly fkn fine once its actually installed lmfao. Also, I personally have not had enough time to properly debug what is happening with TCG on ARM64, so I could be completely wrong on my theory and OC could mitigate every issue if used properly. Take my words with a grain of salt, simply read below on how to actually use this guide...

So basically, I installed Mac OS X Snow Leopard to a macintosh.img on an x86_64 host, my main PC... and then once the screen to reboot appeared, I simply shut the VM down gracefully using the reboot option, and preserved the preinstalled macintosh.img that is ready for first time boot. It does not have any sort of username or anything, its literally right after install and reboot, so... basically I have to share this macintosh_preinstalled.img to you guys on Apple Silicon Macs, just in case you do not have an x86_64 machine available to you.

All you need to do, is unzip the AS_SL.zip file in opencore/ so that you can get AS_SL.img. Now, you need to download the 40GB disk image of Mac OS X Snow Leopard, and drop it into harddrives/ and rename it from macintosh_preinstalled.img to macintosh.img. You are now ready to simply use AS-SL-Boot.sh.