Jump to content

clauden

Members
  • Content count

    1
  • Joined

  • Last visited

About clauden

  • Rank
    InsanelyMac Protégé
  1. Very best guide so far. Thank you. Here are my working cpuidset: (on HP i7 15.6in laptop, vbox 5.0.2, in EFI mode, with osx 10.9-10-11) ::MacBookPro8,2 with an IvyBridge i7-3770 CPU VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000006fb 00000800 80000209 078bfbff VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro8,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple" Few more that you may test: # unknown cpu 00000001 000206a7 02100800 1fbae3bf bfebfbff # only for new i3/i5/i7 ivy bridge processor 00000001 000306a9 00020800 80000201 178bfbff # MacBookPro11,3 with an IvyBridge i7-3770 CPU 00000001 000306a9 04100800 7fbae3ff bfebfbff # iMac11,3 (27-inch, Mid 2010) 00000001 000106e5 00100800 0098e3fd bfebfbffIn my tests, some of the cpuid's gave errors like "vbox error", DSMOS and disk errors. I kept testing until one worked. Here's the windows script I use to boot in EFI mode: osx_efi_launch.bat @echo off set VM_NAME=%1 ::echo 'configuring cpuid and extradata for %VM_NAME%' set MANAGE="C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" set VBOX="C:\Program Files\Oracle\VirtualBox\VirtualBox.exe" :: MacBookPro8,2 with an IvyBridge i7-3770 CPU %MANAGE% modifyvm %VM_NAME% --cpuidset 00000001 000006fb 00000800 80000209 078bfbff %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro8,2" %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple" %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 %MANAGE% setextradata %VM_NAME% VBoxInternal2/EfiGopMode 4 :: 0 640x480 :: 1 800x600 :: 2 1024x768 :: 3 1280x1024 :: 4 1440x900 :: 5 1920x1200 ::%MANAGE% showvminfo %VM_NAME% ::pause start "" %VBOX% --startvm %VM_NAME% Then I simply create as many shortcuts as I need, in which I modify the target according to the VM name. d:\path\to\scrpit\osx_efi_launch.bat VIRTUAL_MACHINE_NAME Script to remove extra data (useful when testing): @echo off set VM_NAME=%1 set MANAGE="C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" set VBOX="C:\Program Files\Oracle\VirtualBox\VirtualBox.exe" :: note CPUID will be taken out from the .vbox file :: %MANAGE% modifyvm %VM_NAME% --cpuidset 0 %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/smc/0/Config/DeviceKey" %MANAGE% setextradata %VM_NAME% "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" %MANAGE% setextradata %VM_NAME% "CustomVideoMode1" pauseHope it helps someone. According to my test, the cpuid used may override the EfiGopMode. For example this one # iMac11,3 (27-inch, Mid 2010) 00000001 000106e5 00100800 0098e3fd bfebfbff would bypass my EfiGopMode=4, while others did not. Worth the try.
×