Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Error during installation of Mountain Lion on PC (via VirtualBox)

2 posts in this topic

Recommended Posts

I got the following error while installing Mountain Lion 10.8 OS X (.iso) with virtualbox by Hackboot:

"Unable to find driver for this platform : \"ACPI\" .\n"@SourceCache/xnu/xnu-2050.7.9/iit/Kernel/IOPlatFormExpert.cpp:1546

Please help me out.

I am using Intel i5 gen 2, 4gb ram, windows 8 (64-bit).


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra or High Sierra in VirtualBox 5.0.34 on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.

      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.

      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...

      3.  Leave the Memory size at the recommended 2048 MB, then click next.

      4.  Choose to "Create a virtual hard disk now", then click the create button.

      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...

      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).

      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.

      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)

         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2

         c.  On the Display tab, you can increase the allocated Video Memory to 128MB

         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 

      Navigate and select the El Capitan ISO we created earlier...

         e.  Click the OK button to finalise the VM settings.
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 

      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" 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/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....

      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms

      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.

      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.

      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...

      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .

      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      Good luck and enjoy
    • By ltooz_audis
      After i finished updating macOS High Sierra on HP x360 15-u011dx Haswell HD4400 i7-4510u, I started to update my daughter Dell Inspiron 7352 Broadwell HD5500 i7-5500u. It was a little harder but it works quite nicely. The new Clover is Buggy with the cache that cause "Error loading Kernel Cache..." that I had to re-install the OS. Kernel Panic all the time until I got the config.plist and kexts correctly. Now it's a perfect little 13" MacBook Air7,2. If you have anything thing with a "u" at the end of the CPU, don't use macbook pro, it doesn't do you any good.
      I'll have full tutorial soon.

      Make sure to have en0 built-in without Ethernet Built-in

    • By xW4LK3R
      Hey guys the reason why I'm making this post is because I didn't think I was going to be able to make a new version of Hackintosh in my old computer. It turned out that I actually could and it works flawlessly!  

      I will tell you what I've made so if you have similar components you can take my guide so you can install it as well. 

      Mobo: H61M-P31 (G3) 
      Processor: i3 3220
      GPU: GTX 1070 (EVGA SC)
      Memory: 8 GB (2x4 1333 MHz) 
      Storage: 2x SEAGATE 500 GB (Windows 10 installed on the 1 HD, Mac OS X in the 2)
      Display: SAMSUNG 23PL S23C550
      Where did I start?
      I started by downloading the Mac OS Sierra DMG (Niresh's version) and then transferred to a USB (8 GB) in Windows using Transmac app. It's pretty simple, there are tutorials available on the net how to do it.
      After you've transferred the DMG to your FLASH USB you will have to go to your BIOS and change SATA IDE to SATA AHCI mode. Also, you'll have to change the HDDs order for booting. If you want to make a dual boot with your windows system you'll have to let the Mac OS X HDD boot first so you can access your Windows system in Clover bootloader. Pretty simple, see more of the "how to" here (http://www.insanelymac.com/forum/topic/303960-success-yosemite-hackintosh-on-msi-h61m-p31w8/) 
      Boot from USB
      After choosing your USB by pressing F11, there's no need to type anything ("darts=0 -v" is inserted by default on the boot loader) after you wait the loading if everything goes well you'll be able to see the setup Mac OS X screen. 
      No mystery here just do what you've learnt and format the HD who is going to host Mac OS X Sierra (that can simply be found on youtube). After you have done all the HD stuff it's time to move on with the insulation. When you finally reach the part where you need to choose your HDD to install Mac OS on, go to Customize in the left bottom corner.  In Customize you'll have to change the bootloader from "Chameleon" to "Clover", for some reason when I tried to install with chameleon on it didn't proceed with the installation and I got several errors. That's very important to keep going with the installation process. 
      If everything gone well you'll now be in the Desktop of your OS. Wait about 10 minutes so the system can configure and make all the changes. After that, the things you'll need to configure are your GPU and the Audio (if your audio for some reason have a static sound or an annoying noise). Also, you'll need to UPDATE your system to the version 10.12.6 so you can install the driver. No mystery here, just go to Appstore and update it and boot your system again (no flag needed). 
      GTX 1070 Driver (Nvidia Web Driver)
      in order to get your GTX 1070 working (works for all pascals and only) you'll need to install (378.05.05.25f01) version which worked for me. You can find it on this link: (http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/)
      After you install your web driver you'll have to activate it on your bootloader.
      Nvidia Web Driver Activation
      After restarting your computer once you've installed the driver you'll need to go on Clover Configurator (which can be found by searching in Spotlight). After that, follow these steps: 
      1 > You'll get a message that Clover didn't find the config.plist and will ask you to mount an EFI Partition. Click on: Mount EFI Partition
      2 > You'll see the EFI Partition in the bottom, then click on "Mount Partition" after that you'll click on "Open Partition"
      3 > Go to: EFI > CLOVER > CONFIG.PLIST > Open with TextEdit
      4 > Scroll down to the last lines and replace: 
      <dict> <key>InjectKexts</key> <string>YES</string> <key>InjectSystemID</key> <true/> <key>NvidiaWeb</key> <true/> </dict> </dict> </plist>     5 > Close the TextEdit and save your changes. 
      - After that reboot your system, you'll probably get your Pascal GPU working by now. 
      Audio FIX / Microphone Fix / Siri Fix
      In order to get your microphone working/siri. You'll need to download the file: "VoodooHDA.Kext" and then follow these steps: VoodooHDA.kext.zip
      1 - > Open Kext Wizard > click on "Installation" tab > drag and drop the file you've just downloaded and drop it in the middle of the app screen > click on Install.
      After that, reboot your system and you'll probably get everything working by now just as I do  

    • By hornpipe2
      I have a Mac Mini 2006 (upgraded) with Intel GMA950 graphics, running MLPostFactor 10.8.5.  It is connected to an ASUS VS197 LCD panel using DVI-D.  This is natively a 1366x768 panel that is recognized and works fine.
      However, the other choices for resolution are 4:3 800x600 and 1024x768, and then the oddballs 832x624 and 1360x768.  None of these are useful as a low-resolution widescreen for gaming or watching DVD content.  Specifically I want to get access to 848x480 or 854x480, and also 1024x576.  SwitchResX makes these choices available, but it doesn't work with a "full screen" game, presumably because the game directly queries OSX Display to get a list of valid resolutions and SwitchResX is bypassing that system instead.
      So the solution is obvious: buy a new computer pull the monitor's EDID data, hack it to enable new resolutions, and then tell OSX to use this custom EDID instead of the one retrieved from the monitor.
      Following the steps of the EDID injection guide, here is where I am:
      * Retrieve EDID, DisplayVendorID etc from ioreg.
      00 FF FF FF FF FF FF 00 04 69 F2 19 24 94 00 00 31 16 01 03 80 29 17 78 EA F5 45 A4 55 50 9E 27 0F 50 54 BD EE 00 81 C0 01 01 01 01 01 01 01 01 01 01 01 01 01 01 66 21 56 AA 51 00 1E 30 46 8F 33 00 9A E6 10 00 00 1E 00 00 00 FD 00 32 4B 18 53 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 41 53 55 53 20 56 53 31 39 37 0A 20 20 00 00 00 FF 00 43 43 4C 4D 54 46 30 33 37 39 32 34 0A 00 F1 * Use an EDID editor to enable new 848x477 and 1024x576 resolutions.  (Verify with an online EDID tool, and compare to the previous version)
      00 FF FF FF FF FF FF 00 04 69 F2 19 24 94 00 00 31 16 01 03 80 29 17 78 EA F5 45 A4 55 50 9E 27 0F 50 54 BD EE 00 81 C0 4B C0 4B CA 4B CF 61 C0 61 CA 61 CF 01 01 66 21 56 AA 51 00 1E 30 46 8F 33 00 9A E6 10 00 00 1E 00 00 00 FD 00 32 4B 18 53 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 41 53 55 53 20 56 53 31 39 37 0A 20 20 00 00 00 FF 00 43 43 4C 4D 54 46 30 33 37 39 32 34 0A 00 47 * Create a new subfolder and plist within /System/Library/Overrides/Display/ containing the new EDID string and monitor name.
      * Reboot.
      Now the problems begin.  Even though the plist file is being read (which I know because the Monitor Name has changed in Displays), the custom EDID is not being used.  When I dig into IORegExplorer I am able to come up with AAPL00,EDID string and it is the unmodified one read from the monitor.  I even tried a plug-and-unplug while OSX is running, and also tried to reset the SMC and NVRAM, but no dice.
      Do I need to start digging into DSDT hacking?  Is the Intel driver pulling down EDID during boot and I need to override it somewhere else?  What am I missing here?
    • By Deli Dumrul
      For Public Beta Version
      I found this script from agentsim who is GitHubGist user. It Works for me on Windows 10 Workstation 12.5.7
      # Generate a BaseSystem.dmg with High Sierra Beta Installer Packageshdiutil attach /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/InstallESD.dmg -noverify -mountpoint /Volumes/highsierrahdiutil create -o /tmp/HighSierraBase.cdr -size 7316m -layout SPUD -fs HFS+Jhdiutil attach /tmp/HighSierraBase.cdr.dmg -noverify -mountpoint /Volumes/install_buildasr restore -source /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erasecp -R /Volumes/highsierra/Packages /Volumes/OS\ X\ Base\ System/System/Installationhdiutil detach /Volumes/OS\ X\ Base\ System/hdiutil detach /Volumes/highsierra/mv /tmp/HighSierraBase.cdr.dmg /tmp/BaseSystem.dmg# Restore the High Sierra Beta Installer's BaseSystem.dmg into file system and place custom BaseSystem.dmg into the roothdiutil create -o /tmp/HighSierra.cdr -size 8965m -layout SPUD -fs HFS+Jhdiutil attach /tmp/HighSierra.cdr.dmg -noverify -mountpoint /Volumes/install_buildasr restore -source /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erasecp /tmp/BaseSystem.dmg /Volumes/OS\ X\ Base\ Systemrm /tmp/BaseSystem.dmghdiutil detach /Volumes/OS\ X\ Base\ System/hdiutil convert /tmp/HighSierra.cdr.dmg -format UDTO -o /tmp/HighSierra.isomv /tmp/HighSierra.iso.cdr ~/Desktop/HighSierraPublicBeta.isorm /tmp/HighSierra.cdr.dmg