Mac OS 10.11 Guest working on 10.13, not on 10.15

[jplw]

I had 2 guests VMs running on an 11.13 VM host, one Windows 7, one 10.11. After upgrading to 10.15, I re-installed VB 6.0.18, did the proper authorizations (allowed the extension, full disk access). After doing so, the Windows 7 Guest runs fine, but the 10.11 VM throws a critical error, with instructions to post VBox log. It is attached.

[mpack]

Don't just splat text all over the site: provide the log as a zip attachment.

We don't need a picture of a black screen at all.

[jplw]

Sorry, The log woud not upload, and the instructions with the error said to post the .png as well. I have now zipped and poated the full log.

[mpack]

There doesn't seem to be any indication of a problem before it hits the critical error 3 seconds in.

00:00:03.421987 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:03.422014 Console: Machine state changed to 'GuruMeditation'
00:00:03.422453 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:03.422454 !!
00:00:03.422454 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:03.422465 !!
00:00:03.422471 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:00:03.422476 !!
00:00:03.422477 !! {mappings, <NULL>}
00:00:03.422478 !!
00:00:03.422486

Triple fault usually indicates running corrupted code, usually the result of corruption.

Did this VM previously run on this hardware? Where did the VM come from?

Do you have a backup of the working version?

I don't see any sign in the log that you're starting from a saved state, but if you are then you should discard the saved state.

[jplw]

This was not starting from a saved state. It never ran on this hardware, but did run on an older machine. My Windows 7 Guest works fine on the new hardware, but not this 10.11 system.

[jplw]

I upgraded VB to 6.1.4. The Windows 7 guest still runs, but not the 10.11 Guest. So...I created a brand new 10.11 Guest, using the sme .iso file with El capitan I had used before. The Guest VM will not start...even to the point of trying to read the .iso. Same error message.

[jplw]

I should have mentioned that my hardware is MacBook Pro fro Dec 2019, so it will not boot anything earlier than Catalina. Does that mean it cannot support anything earlier virtually?

[jplw]

I figured it out!! The Migration Assistant did not bring everything over somehow. I had to rebuild the El Capitan iso from scratch and then issue these terminal commands to configure the guest (which I had done on my original system):

VBoxManage setextradata "El Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2"
VBoxManage setextradata "El Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "El Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED"
[...]
VBoxManage setextradata "El Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
VBoxManage.exe modifyvm "El Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff

Then it would boot to install, but I also had to set and old date in the VM using the Terminal command before starting the installation:

date 101615072016