In this article, I’m going to show you the complete guide to fix VirtualBox errors while installing Mac OS X. Most of the website that creating content regarding the installation of or is not complete and have errors. The article might be correct and work on one device perfectly and without any problem. But there are lots of devices and different kinds of errors. Some months ago, we’ve created an article on how to install Mac OS X El Capitan on VirtualBox and the visitors has got different kinds of problems. One of our visitors “ Holk” has read all the necessary comments and collected all the errors together and told the solutions. Here is his comment.
Sep 28, 2014 - Save hours of searching online or wasting money on unnecessary repairs by talking to a 6YA Expert who can help you resolve this issue over.
First THANXALOT to Mukhtar Jafari for all of his work! I needed more than 3 hours getting it to work. I was stuck in most of the errors mentioned above. Only with hints out of the comments i got it working. I`m merging it here so not anybody else will have this pain. Creating the VM is easy, I´m not mentioning it here (just get vram to 128 mb!), problems were caused by the code (whatelse?!).
Could not find a registered machine name Step #4. How to fix this “ Missing Bluetooth Controller” error. When you see this error. because you are running the commands ( Step# 5) while the Oracle VM software is open. Shut down the VM software completely and then run the commands.
After the commands are ran, open up Oracle VM and start your VM session. If this method did’n work. Try this method. One of our visitor “ Yhal Htet Aung” has found this error. If you copy code from the website, try to change ” with your open inverted comma “.
It is the error. After I changed the line with my open inverted comma for Search and Replace, then the problem solved. Make sure that you use your own open inverted comma in every single line. Try to check and replace it. Search and Replace doesn’t replace all the lines sometimes These tips solved also the “ considerRebuildOfPrelinkedKernel com.apple.kext.triggers triggered rebuild” error! I have a ThinkPad T460s, Intel I7 dual core.
I have verified all settings are correct, have runs the cmd(admin) with VM closed. I’m running Windows 10 64 bit on host and trying to run High Sierra 53 bit on guest. I get the endless reboot loop, and upon occasion, will get a panic kernel cache error 0x9.
The issue is I never get the dsmos to return with anything validating it, like I’ve seen in many other posts. AppleKeyStore: operation failed (pid: 36 sel: 7 ret: e00002c2 ‘-536870206’, -1, 1000000) HID: Legacy shim 2 IOGraphics flags 0x43 (0x51) ACPISMCPlatformPlugin::start – waitForService(resourceMatching(AppleIntelCPUPowerManagement) timed out AppleLPC::notifyingPlactformASPM – registering with plugin with ASPM Support false then several: Sound assertion in AppleHDACodecGeneric at line 534 I have tried all the alternate cpuidset listed in some of the earlier posts. They all return the same problem of the continuous boot-loop. I have pointed to the VMDK file in the 1st position with an 80 virtual hdd and vice versa.
Any other suggestions? Im using windows 7 and try to install MacOS High Sierra using virtual box. I’ve followed numerous tutorial and all seem the same. I’ve checked my hardware and it meets the requirement such as virtually-enabled inside the BIOS. I’ve followed all the steps accordingly and encounter no error. The problem is my virtual box is completely blank when I try to run High Sierra, meaning the boot is not running. I’ve waited for the boot screen to load for like 2 hours and yet nothing happens.
Do you have any solutions for this? I have it going now, thanks for the help.
I don’t know what changed to make it work, but here’s what I did. I created, yet another, instance where, virtually, all these steps are identical to what I did yesterday. Hi there, I have followed all instructions exactly, double checked that I have typed in the correct code and correct VM name, made sure that I typed them in after closing the virtualbox, made sure i ran cmd and VirtualBox as administrator, made sure I have virtualization technology enabled in the bios and have tried using both chipset options IHC9 and PIIX. Nothing has worked for me. The Virtual Box logo displays then the geeky code runs and I can see a lot of tests pass but as soon as it gets to the line “waiting for DSMOS” it encounters the following error and restarts the loop. Hi Mukhtar, thanks for supplying this nice site full of valuable insights.
I was just giving installation of macOS Sierra on a Surface Book running Virtual Box a try. Alas I come to a screeching halt, although I followed your instruction precisely (as far as I can see). Not only do I get the “this is an unknown CPU model 0x4e” although I use the updated Virtual Box code, but also I get “DSMOS: SMC returned incorrect key: ” where key is an all zeroes string. A panic follows with a reference to “/DontStealMacOS.cpp” line 219. What did I miss here? Here are some hints I found: 1) Intel CPU works better than AMD 2) Turn OFF Antivirus programs before starting install 3) Set Video RAM to between 64-128MB 4) Use no spaces in VM name (ex: “MACOSX” not “MAC OSX”) Also no punctuation.
Also verify: VM Type: Mac OS X and Version: Mac OS X 10.11 El Capitan (64-bit) (These are in Virtualbox Settings-General) 5) Suggest use wired Internet, not WiFi, for initial download/updates etc. 6) Run CMD window as Administrator when entering command line commands. 7) May need to start Virtualbox as Administrator. 8) Be patient during initial boot up. It runs disk checks and other repairs and can reboot a couple times.
9) Be sure your HD or SSD has 100GB free space. All the updates after initial installation gobble space. 10) Black Screen?
![How To Fix Installer Name Param Is Missing How To Fix Installer Name Param Is Missing](/uploads/1/2/5/4/125410452/359047416.png)
Try video RAM 64MB and Chipset = PIIX3 11) Do not install Virtual Box Extensions “CD” Hope this helps. It works fine on my HP Elitebook i5 8GB RAM & SSD Windows 10 Creator. I have done everything you have told everyone else with the same issue that I have (black screen but it is running). – I have increased memory to 128 critical error – deleted and reinstalled and made sure to exit Virtual Box when inputting CMD commands (in admin mode) – Anything between 70 to 128mb of video memory results in critical error and anything less than 70 gives me just a black screen – checked my bios and virtualization is enabled – Made sure I replaced my machine name in the code Laptop Specs MSI Nvidia 1050 Intel core i7-7700. Hi, I’ve followed all the steps for setting up mac OS X on a virtual machine. I have successfully logged in to my Apple account. I am getting an interesting error whenever I boot up regularly and when it reboots the machine while it tries to install Mac OS Sierra.
It’s saying: bash: /etc/rc.server No such file or directory bash: /etc/rc.installercleanup No such file or directory After these final displays, the machine goes to my Mac login and I login, but the Sierra update did not install. Your help is greatly appreciated. Hey there, I keep getting an error: Invalid config value(s) for the EFI device (VERRPDMDEVINSUNKNOWNCFGVALUES). I have tried – uninstalling/reinstalling everything – checking the cmd command lines (and it was run in administrator), I re-entered them very carefully too – checking or unchecking the EFI box in system – potentially changing the chipset used – using anywhere from 2 – 16 GB RAM – using anywhere from 2 – 6 cores – and variations on the above attempts Any help would be fantastic! I have found that my very old Mountain Lion install that I had working on 4.3 no longer works (but thats a different story).
I uninstalled 4.3 to install the latest version for a Sierra install. I had the same problem.
Firstly at step 3.3 click on browse and find the vmdk file you downloaded and extracted, select this. At step 4 add a step 4.5 Edit settings, storage, select Sata controller and add a new hard drive, create a new drive. Once the drive is created change the sata ports so the new drive is before the vdmk drive.
Then start the VM. Give the VM time to complete tasks.
If it hangs before the welcome screen, reset the machine. You may need to do this a couple of times.
The VM will then correctly boot and load and bring up the welcome screen. Hope this works for you. I solved the infinite boot loop by selecting the correct CPU spoof: For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.