Kernel Trap Error (?) When Booting Snow Leopard Install ISO

[jahburnit]

Hey,

I have been having a strange issue, which is shown below, while trying virtually every available option? I have tried to boot both my legit copy of Snow Leopard as well as an ISO image I made from it with Disk Utility to no avail. No matter how precisely I follow any guide online, I always end up with the following error:

Screen Shot 2012-12-11 at 12.28.10 AM.png (53.61 KiB) Viewed 6800 times

Here are my extra flags:


VBoxManage setextradata "SL106" VBoxInternal2/EfiGopMode 2
VBoxManage modifyvm "SL106" --firmware efi
VBoxManage setextradata "SL106" VBoxInternal2/SmcDeviceKey "*censored*"

Disregarding the first #2 extra flags, I still get this issue. I have tried messing around w/ different guides but they all do the above, just in a different order =/

I have tried setting up the IDE CD as Primary Master and Secondary Master. I have also enabled the USB options and I have the extensions package installed... (Just to clarify things a bit more)

[jahburnit]

Here are the logs...

[mpack]

00:00:02.594398 Host RAM: 3072MB total, 1349MB available
...
00:00:02.759604 RamSize <integer> = 0x0000000057f00000 (1 475 346 432, 1407 MB)

This may not be the only problem, but you are assigning way more memory to the VM than is available on your host.

[jahburnit]

At the time I set it, I was in the green. However, hat does not seem to have any affect on this particular issue. Thanks for pointing that out though, it will probably save me some future grief

[jahburnit]

Here are some newer logs, with the same screen output in the first post..... I enabled logging for the PAE extensions

[jahburnit]

After debugging, it seems that "monitor" seems to be the invalid opcode. What the frick is up with that? Not one google search brings up a similar problem. This is probably being invoked by a kernel extension external to VBox, am I right? Any suggestions?

Code: Select all

VBoxDbg> u 0x1ddced25
%000000001ddced25 0f 01 c8     monitor eax, ecx, edx
%000000001ddced28 85 f6                   test esi, esi
%000000001ddced2a 74 18                   je +018h (01ddced44h)
%000000001ddced2c c7 46 04 00 00 00 00    mov dword [esi+004h], 000000000h
%000000001ddced33 c7 06 00 00 00 00       mov dword [esi], 000000000h
%000000001ddced39 85 ff                   test edi, edi
%000000001ddced3b 74 11                   je +011h (01ddced4eh)
%000000001ddced3d 0f ae f0                mfence
%000000001ddced40 0f 09                   wbinvd
%000000001ddced42 eb 0a                   jmp +00ah (01ddced4eh)

Latest machine screenshot:

Screen Shot 2012-12-11 at 11.10.18 PM.png (78.66 KiB) Viewed 6763 times

[rpmurray]

The AppleIntelCPUPowerManagement.kext is where Apple checks the hardware on boot to make sure that the CPU is supported by the OS. The only time I've ever seen a panic like this is when:

1) Someone tries to create a Mac OS X guest on Mac hardware that is not supported by the OS. Like trying to run Snow Leopard on a newer Mac that came with Lion or Mountain Lion as the pre-installed OS. This is because they are using newer CPUs whose CPUIDs are not in the supported list in the kext.

2) Someone tries to create a Mac OS X guest on non-Mac hardware.

According to the log your Mac is a Mac Pro 4,1 "Quad Core" 2.66 (2009/Nehalem) so we can rule out 2. And the pre-installed Mac OS X was 10.5.6 so you should be able to use the 10.6.3 retail disc (your legit DVD).

From your above post you said you've done:

VBoxManage setextradata "SL106" VBoxInternal2/EfiGopMode 2
VBoxManage modifyvm "SL106" --firmware efi
VBoxManage setextradata "SL106" VBoxInternal2/SmcDeviceKey "*censored*"

Your log though, indicates that the VM is actually named "SL10.6". Have you tried using that? You shouldn't need to do the second statement since you can choose EFI using the VB GUI in Settings > System > Motherboard > Extended Features > Enable EFI, and the third statement is superfluous since you're running this on Mac hardware. Make sure you assign only one core to the VM.

[jahburnit]

Hmm, I downed it to 1 core. Now it loads fine w/o any kernel traps. However, now it just stalls at:

AppleIntelCPUPowerManagementClient: ready

[ChipMcK]

. . . it just stalls at: AppleIntelCPUPowerManagementClient: ready

You seem to have the same environment: iMac came with Leopard installed.
I am trying to get a p2v clone to run under vb. I am waiting your success.

[rpmurray]

In Settings go to General > Basic and change the version of the Operating System from Mac OS X Server to Mac OS X Server (64 bit). I remember reading a post a while back from one of the developers that there is a glitch in the handling of the EFI that can be worked around by choosing the 64-bit setting.

If that doesn't work then try using an earlier version of VB than 4.2.x. I've been running Snow Leopard as a guest using VB 4.0.16, but you could try the last 4.1.x to see if it works with it.