virtualbox.org

Hello all.

I am trying to create a Snow Leopard guest on a Lion host. I cannot even get to installing the OS. Instead I receive this error message, "Unexpected trap during early EFI bootstrap!!"

Here are some of the technical specifications:

Virtual machine:
2048MB RAM
100GB HD
Snow Leopard retail DVD version 10.6.3

VirtualBox 4.1.22 r80657
VirtualBox Extension Pack 4.1.22 r80657

Host machine: MacBook Pro notebook
2.5 GHz Intel Core i5
4GB RAM
500GB HD
OS 10.7.4

Does anyone have this working with this version of VirtualBox? If so, what am I missing?

Thank you in advance.

Here is the log file from my most recent attempt to start the virtual machine.

Try reducing the VRam and see if it helps. 32MB should do it as a test.

Follow the bug if this helps Ticket #8604

Perryg, thank you for your reply.

I received the same error with 32MB for vram. The log file is attached.

I'm not sure what you mean by "follow the bug."

Did you click the link to the ticket?

Yes, I clicked and read through the ticket. Still doesn't work when I've tried 32MB, 64MB and 128MB for VRAM. I'm using MacBook Pro with Lion so applying the .DLL does not apply in my case.

Thanks again for your help.

Well, I can't seem to get any further on this.

I've tried different versions of VB (4.0.4, 4.0.16, 4.1.6, 4.1.12, 4.1.22) with extensions.

I've read the notes for tickets
https://www.virtualbox.org/ticket/8604
https://www.virtualbox.org/ticket/9143
https://www.virtualbox.org/ticket/10621.

I've tried selecting OS X Server and OS X Server 64-bit.

Same result each time - kernel panic before installation disk even loads.

Is it working for anyone with this or any version of VB?

Any guidance or suggestions would be appreciated.

I've got a Snow Leopard guest running on a Snow Leopard host on VB 4.0.16.

The main difference is that I'm running this on a Mac Pro 3,1 (Early 2008) that can natively run Snow Leopard.

The installer disc, for OS X versions prior to Lion, runs two checks to make sure you're installing on Mac hardware. The first tests the CPU as the installer disc boots and compares it to a list of the CPUs in Macs that were supported when that version of the OS was released. Normally you'd get an error message indicating that this was not a supported Mac if you ran it on newer hardware, rather than a kernel panic, but the code could be tripping up on some new CPU feature that wasn't available when the code was written. This is most likely what's happening in your case. VirtualBox does pass the CPUID through to the guest VM so even if you could get the installer disc to boot you'd be stopped dead by the check.

The second test occurs when you actually try to run the installer and it checks to see if the Model Identifier of your Mac matches those of Macs that were able to run Snow Leopard. VirtualBox also passes this Model Identifier (in my case MacPro3,1) through to the guest VM for the installer to read. This is not your problem because you haven't gotten that far but it would bite you if you could actually get the installer disc to boot.

There are ways to get around both these problems but that is something that cannot be discussed on these forums because doing so sidesteps Apple's EULA and the moderators police these forums vigorously. You may want to use Google to search the internet to see if you can find solutions elsewhere (wink, wink, nudge, nudge).