These two commands were enough to get it past the kernel panic and running. Leopard in this case being the name of my VM. VBoxManage setextradata "Leopard" "VBoxInternal/CPUM/MSRs/MsrPmgCstConfigControl/First" 0x000000E2 VBoxManage setextradata "Leopard" "VBoxInternal/CPUM/MSRs/Ia32MiscEnables/First" 0x000001A0 For Leopard I was finally able to get it to run by using the following two commands in Terminal: After futzing around with both of them for awhile I've managed to get Leopard to run but Tiger is putting up a fight. The devs have made some changes since then that have the side-effect of causing these VMs to both fail to boot with kernel panics. Up through VB 4.3.6 they ran without difficulty, see Status of OSX on OSX for details. They are OS X Tiger (10.4.11 - intel version) and OS X Leopard (10.5.8 ). Two of my guest virtual machines are giving me problems. The host machine is an iMac i7 3.4 27-Inch (Mid-2011). I'm currently in the process for moving from OS X Snow Leopard (10.6.8 ) and VirtualBox 4.3.6 to OS X El Capitan (10.11.6) and VirtualBox 5.1.12.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |