"Meditating Guru" Problem with OS X 10.4 Tiger

[The.OS.Geek]

So, I've been trying to install OS X 10.4 Tiger on Virtualbox for a while, (on Apple hardware), and the install DVD does this on boot up, every single time:
[Picture in the "Logs" file.]

And here is are the logs:

Logs.zip

(75.61 KiB) Downloaded 31 times

My machine : MacBook Air (late 2017), running macOS Catalina 10.15.5

Regards,
The.OS.Geek

[mpack]

00:00:16.792533 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:16.792534 !!
00:00:16.792534 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:16.794159 !!
00:00:16.794175 !! ACTIVE TRAP=08 ERRCD=0 CR2=00000000deadface PC=00000000001983f4 Type=0 cbInstr=ff fIcebp=false (Guest!)
00:00:16.794204 !!

Triple fault means the guest did something really nasty. This most commonly indicates corrupted boot code on the ISO (code for the wrong processor entirely would also fit).

I see that the VM is configured for EFI. Did OS X 10.4 really support EFI - in 2005? I find that unlikely.

Also, I assume the ISO supports Intel x86 and is not PowerPC only?

[The.OS.Geek]

.... Triple fault means the guest did something really nasty. This most commonly indicates corrupted boot code on the ISO (code for the wrong processor entirely would also fit).

I see that the VM is configured for EFI. Did OS X 10.4 really support EFI - in 2005? I find that unlikely.

Also, I assume the ISO supports Intel x86 and is not PowerPC only?

I'm sorry I didn't mention this before, but :
-Yes, the ISO is for the Intel x86 platform.

Now, with the EFI option disabled, it says:

FATAL:No bootable medium found! System halted.

I'll try it with another disk image.

[The.OS.Geek]

....And unfortunately, it doesn't work. It still gives me a Meditating Guru error.

[multiOS]

The Tiger installer might be kicking up its heels because it doesn't recognise your CPU, i.e. your Mac has a CPU produced long after 'Tiger' was intended to be used; and Apple quite effective at blocking installation of old OSX Versions on 'newer' hardware than it was intended to run on and vice versa - The CPU's identity is, of course, the one bit of real hardware that is readily recognised within a VM. If that's the cause, then you will need to convince the Tiger installer that you do have a CPU that it would have recognised back in the day.

There's some guidance amongst previous Mac threads/How Tos on how to spoof the CPU ID, but unfortunately I don't have a link to hand. EDIT: Seehttps://forums.virtualbox.org/viewtopic.php?f=22&t=93059

[The.OS.Geek]

The Tiger installer might be kicking up its heels because it doesn't recognise your CPU, i.e. your Mac has a CPU produced long after 'Tiger' was intended to be used; and Apple quite effective at blocking installation of old OSX Versions on 'newer' hardware than it was intended to run on and vice versa - The CPU's identity is, of course, the one bit of real hardware that is readily recognised within a VM. If that's the cause, then you will need to convince the Tiger installer that you do have a CPU that it would have recognised back in the day.

I'll try that and see if it solves the problem.