Error load prelinked kernel with status 0x8000000000009

Error load prelinked kernel with status 0x8000000000009

UEFI bios:
• Скидываем все настройки в default.
• AHCI — enable;
• Vt-d: Disable (+ в Clover дропнуть DMAR таблицу)
• Vt-x: Enable (только для 10.13 и если используете виртуальные машины)
• Intel Virtualization Technology — Enable
• Serial-port: Disable (Можно оставить включеным, но это требует внесения изменений в загрузчик (Opencore)
• XHCI Hand-off: Enabled (рекомендуеться)
• XHCI Hand-off: Disable (только если что то не работает в режиме Enable )
• IOAPIC 24-119 Entries: Enabled (подмечено что у многих с этим пунктом паникует, поэтому тестируйте)
• CSM: Disable (если ваша видеокарта не умеет работать в режиме UEFI — не выключайте)
• Fasboot: Disable
• Secure boot: Disable or Other OS
• ResizeGPUBars: Disable (Можно оставить включеным, но это требует внесения изменений в загрузчик (Opencore)
• Above 4g decoding: Enable

Legacy bios:

Для установки потребуется флешка не менее 16Гб.

За данный споcоб установки благодарим cvad и Skvo
Данная инструкция написана по материалам с applelife.ru

• OPT — показать меню загрузки OpenCore. Также поддерживается клавиша Esc.
• CMD+OPT+P+R — очистить NVRAM. Требуется Misc-Security-AllowNvramReset=YES.
• X — загрузить первую найденную операционную систему Apple, если по умолчанию выбрана не операционная система Apple.
• CMD+R — загрузка в режиме восстановления (Recovery).
• CMD+C+MINUS — отключить проверку совместимости на board-id.
• CMD+K — загрузка актуального ядра, аналогично kcsuffix=release.
• CMD+S+MINUS — отключить KASLR slide, требуется выключенный SIP.
• CMD+S — однопользовательский режим, налогично флагу -s в аргументах загрузки.
• CMD+V — логирование загрузки, аналогично флагу -v в аргументах загрузки.
• Shift — безопасный режим, налогично флагу -x в аргументах загрузки.
В зависимости от железа, при загрузке может не все работать или работать не надежно. На PS/2 при загрузке доступно только Esc.

Комбинации клавиш в меню, после входа в него по OPT(Esc) или при ShowPicker=YES
За счет того что в меню действует параметр Misc-Boot-PollAppleHotKeys=YES успехов тут обычно больше. Не включайте, если с выключенным работает.

• Esc — отмена тайм-аута.
• CMD+OPT+P+R — очистить NVRAM. Требуется Misc-Security-AllowNvramReset=YES.
• CMD+C+MINUS — отключить проверку совместимости на board-id.
• CMD+K — загрузка актуального ядра, аналогично kcsuffix=release.
• CMD+S+MINUS — отключить KASLR slide, требуется выключенный SIP.
• CMD+S — однопользовательский режим, налогично флагу -s в аргументах загрузки.
• CMD+V — логирование загрузки, аналогично флагу -v в аргументах загрузки.
• Shift — безопасный режим, налогично флагу -x в аргументах загрузки.
• Index — загрузка раздела соответствующего индексу.
• Enter — загрузка дефолтного раздела или выбранного стрелками.
• CTRL+Enter и CTRL+Index — выбрать выделенный раздел для загрузки по умолчанию. Требуется Misc-Security-AllowSetDefault=YES.

CMD=Windows Key, OPT=Alt на windows ориентированной клавиатуре.

В зависимости от вашего BIOS и типа клавиатуры доступные комбинации могут варьироваться.
Больше деталей в актуальной документации.

Источник

Error load prelinked kernel with status 0x8000000000009

UEFI bios:
• Скидываем все настройки в default.
• AHCI — enable;
• Vt-d: Disable (+ в Clover дропнуть DMAR таблицу)
• Vt-x: Enable (только для 10.13 и если используете виртуальные машины)
• Intel Virtualization Technology — Enable
• Serial-port: Disable (Можно оставить включеным, но это требует внесения изменений в загрузчик (Opencore)
• XHCI Hand-off: Enabled (рекомендуеться)
• XHCI Hand-off: Disable (только если что то не работает в режиме Enable )
• IOAPIC 24-119 Entries: Enabled (подмечено что у многих с этим пунктом паникует, поэтому тестируйте)
• CSM: Disable (если ваша видеокарта не умеет работать в режиме UEFI — не выключайте)
• Fasboot: Disable
• Secure boot: Disable or Other OS
• ResizeGPUBars: Disable (Можно оставить включеным, но это требует внесения изменений в загрузчик (Opencore)
• Above 4g decoding: Enable

Legacy bios:

Для установки потребуется флешка не менее 16Гб.

За данный споcоб установки благодарим cvad и Skvo
Данная инструкция написана по материалам с applelife.ru

• OPT — показать меню загрузки OpenCore. Также поддерживается клавиша Esc.
• CMD+OPT+P+R — очистить NVRAM. Требуется Misc-Security-AllowNvramReset=YES.
• X — загрузить первую найденную операционную систему Apple, если по умолчанию выбрана не операционная система Apple.
• CMD+R — загрузка в режиме восстановления (Recovery).
• CMD+C+MINUS — отключить проверку совместимости на board-id.
• CMD+K — загрузка актуального ядра, аналогично kcsuffix=release.
• CMD+S+MINUS — отключить KASLR slide, требуется выключенный SIP.
• CMD+S — однопользовательский режим, налогично флагу -s в аргументах загрузки.
• CMD+V — логирование загрузки, аналогично флагу -v в аргументах загрузки.
• Shift — безопасный режим, налогично флагу -x в аргументах загрузки.
В зависимости от железа, при загрузке может не все работать или работать не надежно. На PS/2 при загрузке доступно только Esc.

Комбинации клавиш в меню, после входа в него по OPT(Esc) или при ShowPicker=YES
За счет того что в меню действует параметр Misc-Boot-PollAppleHotKeys=YES успехов тут обычно больше. Не включайте, если с выключенным работает.

• Esc — отмена тайм-аута.
• CMD+OPT+P+R — очистить NVRAM. Требуется Misc-Security-AllowNvramReset=YES.
• CMD+C+MINUS — отключить проверку совместимости на board-id.
• CMD+K — загрузка актуального ядра, аналогично kcsuffix=release.
• CMD+S+MINUS — отключить KASLR slide, требуется выключенный SIP.
• CMD+S — однопользовательский режим, налогично флагу -s в аргументах загрузки.
• CMD+V — логирование загрузки, аналогично флагу -v в аргументах загрузки.
• Shift — безопасный режим, налогично флагу -x в аргументах загрузки.
• Index — загрузка раздела соответствующего индексу.
• Enter — загрузка дефолтного раздела или выбранного стрелками.
• CTRL+Enter и CTRL+Index — выбрать выделенный раздел для загрузки по умолчанию. Требуется Misc-Security-AllowSetDefault=YES.

CMD=Windows Key, OPT=Alt на windows ориентированной клавиатуре.

В зависимости от вашего BIOS и типа клавиатуры доступные комбинации могут варьироваться.
Больше деталей в актуальной документации.

Источник

raimue.blog

For testing purposes, I have a VM in VirtualBox currently runnning macOS 10.12 Sierra. Now that macOS 10.13 High Sierra is in Beta, I wanted to upgrade my VM to this new release. However, this proved to be difficult with the usual ways. This blog post will describe how to upgrade a Sierra VM to High Sierra.

The problem preventing the upgrade appears to be the boot sequence in VirtualBox. It looks like the EFI implementation of VirtualBox does not honor the way macOS wants to select the startup disk/volume/startup script or in whatever way that is actually supposed to work. The result is that you can click through “Install macOS 10.13 Beta.app”, but after the restart the old system comes up as if nothing happened.

Follow these steps to get around this problem:

1. Boot the VM normally in VirtualBox.
2. Open “Install macOS 10.13 Beta.app”, click through until you get to “Restart”.
3. As soon as the screen turns black, start to hammer the F12 key. Make sure your keyboard is grabbed by the VM.
4. If you managed to hit F12 at the right time, the VirtualBox EFI should pop up. If the VM starts up normally, go back to step 2.
5. Now use your arrow keys to select Boot Manager and hit Return, then launch the EFI Internal Shell from there.
6. Inside the shell, type the following commands:

With the last command, the system should continue booting. After a short moment, the installer will turn up and begin to upgrade your system from macOS 10.12 Sierra to macOS 10.13 High Sierra. Now you will have to wait for the macOS Installer to finish, which may take a while.

In case VirtualBox crashes with “Guru Meditation: VERR_IEM_INSTR_NOT_IMPLEMENTED” on the login screen when booting the new system, update to the latest VirtualBox test build, which implements the missing instruction.

This post was inspired by another blog post documenting similar instructions on how to enter the macOS Recovery in VirtualBox. For completeness and archival purposes, you can use the following EFI commands to boot macOS Recovery:

49 thoughts on “ Upgrading a VM from macOS 10.12 Sierra to macOS 10.13 High Sierra in VirtualBox ”

I tried this (without success) and noted the following:

I had to hold fn-F8 to get into the boot manager.

Although using the latest test build of VBox (5.1.x revision 116680) I get this message after entering the commands:

Read error 0xe
Error loading kernel cache (0xe)

I am getting the same issue as Lars is with the VM ending in
”
Read error 0xe
Error loading kernel cache (0xe)
”
After I execute the commands listed above.

Any idea on the fix?
VirtualBox 5.1.22 r115126 (Qt5.6.2) on macOS 10.12.5 host

Same issue
Read error 0xe
Error loading kernel cache (0xe)

Same issue. Error loading kernel cache.

Sorry that I did not come back to your questions. VirtualBox seems unable to boot the new macOS High Sierra Beta after migrating to APFS and there is no progress in getting that implemented. Therefore I decided to switch to VMWare Fusion instead, which I do not regret at all.

Just a note to confirm that this is working perfectly for me: Virtualbox 5.1.26
Thanks!!

I tried using latests Virtual Box (5.1.28) and current high sierra public release.
Now, there is no Locked Files folder inside of macOS Install Data, so i am not able to to boot to the new installer. Any clues?

Thanks for this blog entry. This was the smoking gun preventing me from upgrading my VirtualBox Sierra VM.

This worked great for me and allowed to create a new High Sierra VM. I was not upgrading. I had to make sure SSD was not enabled in VirtualBox preferences otherwise High Sierra would automatically want to migrate to APFS.

thanks a lot for your help

Great how-to, worked for me, but hitting F12 at the right time is very hard, so I made a snap-shot of the VM right before the reboot. That way you can avoid having to re-download the upgrade a couple of times.

I still needed to ram the F12 as fast as I could to make the EFI shell option appear.

`VBoxManage modifyvm OSX –bioslogodisplaytime 10000` –> Does not seem to work

I’m stuck here…
I had a OS X 10.12 on VMWare and started to upgraded to 10.13. When I cam back I saw the blue screen (boot menu). And failed to use your instructions, since there is no fs1 reachable in the internal shell. fs0 and blk0 to blk3. And it seems they are empty! What can I do here?

These instructions were written for VirtualBox and macOS 10.13 Developer Beta before APFS became mandatory. As far as I know, the VirtualBox EFI BIOS still does not support APFS. Personally I switched to VMWare Fusion due to this.

One thing you could try in VIrtualBox is to remove the checkbox on “Solid-state drive” in the storage settings of the VM. Then the High Sierra installer should no longer try to upgrade the disk to APFS, but leave it as HFS.

Following these steps, a message appears when run boot.efi –> “does prinf works??” and back to command line.
after that I type reboot and nothing happens, I’m in the same version.

I have the same problem as Pedro – “does printf works. ” and hangs…Any Idea what to do?

-I manually downloaded the combo update package 10.13.3 from Apple and launched it in the VM.
-The first part of update completed successfully, than it asked for restart.
-I restarted, entered the VirtualBox EFI Shell and launched boot.efi manually from the indicated path.
-After some work, message appears “macOS could not be installed on your computer – The path […]OSInstall.mpkg appears to be missing or damaged” (e.g. https://user-images.githubusercontent.com/192271/27255121-5811f2b4-538f-11e7-8117-9401bc9a7a80.png)
-I pressed Restart and the VM rebooted to High Sierra 10.13 (no update).

I think we are close to target, but some details are still missing to complete the update successfully.

Yes Yes Yes, thank, works perfectly.

first try I got kernel error like others. Tried second time and it worked don’t know what exaclty the reason for it. thanks

This was the solution I needed to upgrade from high sierra 10.13 to 10.13.4 using Virtual Box 5.2.8
Worked great! Thanks

I found the solution to “does printf works”

You can boot from instalation disk without shell, just open “boot from file” and find boot.efi on instalation disk.

@Babak Vandad: Did you see any error codes in the output? If so, was one of them ID10T?

The error
“Read error 0xe
Error loading kernel cache (0xe)”
can be solved by upgrading to the latest version of the Virtual box.

Thanks! This worked for me on VirtualBox going from 10.12 to 10.13 not in the Beta.

Thank you. Worked like a charm.

Thank you. It work with VirtualBox 5.2.8

Thank you!
It works, even it’s not worked from the first attempt.
The main cause of the fault was an old version of virtual box. With new Virtual Box (v 5.2.10) all goes well

My way of reaching 10.13.4 of Mac OS Sierra (probably you need last because of Xcode requirements)

upgrade Virtual Box to 5.2.10
do MacOs Recover
do Upgrade -> F2 …

I got this working.

Virtual Box – 5.2.12

Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

Every time I tried the above I could not get it to work and I received the error – error loading kernel cache 0x9 VirtualBox.

I did a bit of research and others were having the same issue, however, no one could get it to work.

What I did then was the following

Ran the update, reboot the machine and F12’ed into the boot manager.

I turned off the Virtual Machine and closed VBox

I then tried the following.

Opened CMD as admin and ran the following commands, these were the same commands needed when originally installed the Mac onto Vbox

VBoxManage.exe modifyvm “Mac” –cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “MacBookPro11,3”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-2BD1B31983FE1663”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

Once the commands complete, I started the VM on VBox and F12’ed into boot managed and followed the same procedure

Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

This time it worked and boot into the install/update – Took about 45 min +-

Hope that helps anyone.

I tried @Ghost’s solution and I got the “does printf work?” message.
Then I tried @Pedro’s “I found the solution to does printf work” and I *still* got the “does printf work?”

Then, I restored form snapshot, booted into the old version, started the install again, On bootup I tried Pedro’s solution to boot from file and this time it worked!

Thanks a lot to Ghost (2018-05-12 at 12:29) it worked for me with VB 5.2.12

The right first command is
VBoxManage.exe modifyvm “Mac” –cpuid-set 00000001 000306a9 04100800 7fbae3ff bfebfbff

Thanks a lot, worked with 10.14 beta. Not finished the installation yet, but the installer is up and running 👍🏼

I struggled to update macOS but finally worked it out.

You will find that any updates you apply will disappear after reboot as if they didn’t apply. You have to do the following as the update only completes after a reboot done in a certain way.

1) Download the update from the Apple website or apply from the App store.
2) When promoted to re-boot, press the F12 immediately after the restart, make sure the keyboard is captured in Virtualbox.
3) Press ESC key to stop the auto boot before the countdown finishes. You only have a few seconds to do this.
4) In the BOOT MANAGER option choose EFI Internal Shell.
5) Do the following at the shell command line:
fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

The system should then boot and continue the install and you are done. It is very important that you do all this on the first re-boot after applying the initial update as the update files are copied ready to complete the process. Miss the first boot and you will have to start again.

worked exactly as you described it! thanks mate!

To update mac os follow the below steps. If you will try to upgrade it normaly it would be locked by Apple and you will get the old version that you are currently running. To upgrade use the bellow steps:

Follow these steps to get around this problem:
1. Boot the VM normally in VirtualBox.
2. Open “Install macOS 10.13 Beta.app”, click through until you get to “Restart”.
3. As soon as the screen turns black, start to hammer the window+r key. Make sure your keyboard is grabbed by the VM.
4. If you managed to hit window+r at the right time, the VirtualBox EFI should pop up. If the VM starts up normally, go back to step 2.
5. Now use your arrow keys to select Boot Manager and hit Return, then launch the EFI Internal Shell from there.
6. Inside the shell, type the following commands:
Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

@Ghost’s solution worked for me. Thanks!

@kundan’s worked for me.

Thanks Rainer Müller. This worked for me just fine. I even was surprised didn’t get first “restart” .. system just restarted, I didn’t repeat from step (2) , I just restarted again and hit F12, followed procedure and in aout 90 minutes system rebooted to High Sierra … !! fantastic.

Updating from High Sierra 10.x to the latest update through the store, it won’t boot anymore.
tried F12 and the folder is not there, since it was a 2.6 Gb update.

Anyway to get this update to work?

Using VirtualBox 5.2.18. I had High Sierra 10.13.4 installed and working well, but 10.13.6 would not install from the App Store. I found this post when searching, and the steps listed worked first time. Thanks for the post!

F12 just won’t work. Don’t know what I’m doing wrong… :/

Windows+R does nothing either. I guess @kundan meant HOST+F12 so i tried that (restarting the machine upon restart). I have to press ESC right after that to enter the boot menu but after launching boot.efi i end up getting a kernel cache error.

thank you @kundan this worked perfectly. F12 is the key that I used to get in.

Has anyone got this working with Mojave?

Im getting this error:

ERROR. Load prelinked with status 0x800000000000000e
Error loading kernel cache (0xe)

I tried to upgrade to Mojave from Sierra via the appstore and it crashed my partition. EFI manager did not recognize FS1 or FS2.

This is not working in VirtualBox 5.2.18. Reboots endlessly.

I was getting the Error. Load prelinked kernel with status 0x800000000000000e while trying to upgrade to Mojave MacOs on a VirtualBox virtual machine. Turns out I had the older USB 2 compatibility in the settings for VirtualBox.

If you run into this issue turn off the VM, go into VirtualBox settings USB and select USB 3.0 controller. Restart the VM and issue should be solved.

me stuck with 10.13.2
Upgrade to mojave by following the step above leaves with
ERROR. Load prelinked with status 0x800000000000000e
Error loading kernel cache (0xe)

Has anybody been able to upgrade to Mojave yet ?

This is great, you can also get to it from “Boot Maintenance” > “Boot From File” and navigating to the boot.ini visually if that’s easier.

I finally managed to get beyond “Error loading kernel cache (0xe)”.
The solution was to entirely delete the “macOS Install Data” Folder and simply restart the update in sierra.
But this folder isn’t to delete easily.

I did:
1. Boot into macOS Recovery Mode as describled in this blog post
2. Open a Termial (Menubar: Utilities->Terminal)
3. run “csrutil disable”
4. run “rm -rf “macOS Install Data”
5. run “csrutil enable”

reboot normally, run Mojave installer again, on first reboot follow the instructions in this blog post

Thanks for this post.
I tried it like described above.

First time i ran into
“Read error 0xe
Error loading kernel cache (0xe)”

But just tried it again and second time it worked.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Welcome!

This the personal blog of Rainer Müller, also known by his nickname raimue. This is the space where I publish what does not fit into a tweet.

Источник

Kernel cache crash #5

Have seen this mentioned in the troubleshooting section of the readme but with no further info. I have followed the guide letter for letter, but install crashes on boot with this eroor or occasionally seed related error. Have tried various versions of Aptio fix with no joy, have also tried unibeaat Uefi or legacy boot version as well all have crashed out the same way. Any further info anyone can offer..

The text was updated successfully, but these errors were encountered:

Hey @graysham, I also face this error from time to time, I lately switched from OsxAptioFixDrv to OsxAptioFix2Drv I had the impression the error occurs less frequently then. To pass this error I need to restart multiple times — so my advice is to keep trying restart until it passes with showing a uuid. Also try restarts with power off. I don’t know what causes the kernel cache to crash, I noticed little system changes like hardware or Bios-settings can cause this error, but it also occurs from cold-boot too.

Hi thanks for the response, does this continue to be an issue after install or is it just leading up to install?

sorry didn’t mean to close the issue!

This continue to be an issue after install too, but it doesn’t occur often and if it most passes after the first or second restart. But finding a permanent solution would be nice! With OsxAptioFixDrv more restarts were required if I remember correctly. But I guess you tried all OsxAptioFixDrv versions? What is your clover version?

Clover I have tried the newest one and whatever version is currently bundled with unibeast. I have tried every version of aptiofix I can find and have either hit kernel
Cache error or seed related error thus far with no successful boots into install. Have removed ram apart from two in slots 1 and 3. Removed all drives except target and made sure it’s only in the gray sata slot.

Do you have exactly the same mainboard? Which version is your Bios? I will update working bios settings soon, maybe you can check out yours?

I have the normal p8p67 as opposed to the pro, bios version 3602, however have seen people who have successfully set up with this motherboard following your guide. Bios settings I have looked at yours and other guides; disabling Bluetooth, usb 3.0

Have just tried 10 reboots in a row, stuck at load prelinked kernel with status 0x800000000009
Error loading kernel cache (0x9)

That’s with Aptiofix2

Using aptiofix3 I get past kernelcache 90% of the time and hit randomseed error, any tips on that one? I have tried mapping my ram through smbios, does not seemed to have helped.

Do you use the config.plist from the repo? What SMBios do you use? iMac17,1 Intel Core i7 6700K @ 4GHz is working good for me.

I have yes used the config.plist, also using 17.1 smbios, May have to look at swapping for another motherboard

© 2022 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

raimue.blog

For testing purposes, I have a VM in VirtualBox currently runnning macOS 10.12 Sierra. Now that macOS 10.13 High Sierra is in Beta, I wanted to upgrade my VM to this new release. However, this proved to be difficult with the usual ways. This blog post will describe how to upgrade a Sierra VM to High Sierra.

The problem preventing the upgrade appears to be the boot sequence in VirtualBox. It looks like the EFI implementation of VirtualBox does not honor the way macOS wants to select the startup disk/volume/startup script or in whatever way that is actually supposed to work. The result is that you can click through “Install macOS 10.13 Beta.app”, but after the restart the old system comes up as if nothing happened.

Follow these steps to get around this problem:

1. Boot the VM normally in VirtualBox.
2. Open “Install macOS 10.13 Beta.app”, click through until you get to “Restart”.
3. As soon as the screen turns black, start to hammer the F12 key. Make sure your keyboard is grabbed by the VM.
4. If you managed to hit F12 at the right time, the VirtualBox EFI should pop up. If the VM starts up normally, go back to step 2.
5. Now use your arrow keys to select Boot Manager and hit Return, then launch the EFI Internal Shell from there.
6. Inside the shell, type the following commands:

With the last command, the system should continue booting. After a short moment, the installer will turn up and begin to upgrade your system from macOS 10.12 Sierra to macOS 10.13 High Sierra. Now you will have to wait for the macOS Installer to finish, which may take a while.

In case VirtualBox crashes with “Guru Meditation: VERR_IEM_INSTR_NOT_IMPLEMENTED” on the login screen when booting the new system, update to the latest VirtualBox test build, which implements the missing instruction.

This post was inspired by another blog post documenting similar instructions on how to enter the macOS Recovery in VirtualBox. For completeness and archival purposes, you can use the following EFI commands to boot macOS Recovery:

49 thoughts on “ Upgrading a VM from macOS 10.12 Sierra to macOS 10.13 High Sierra in VirtualBox ”

I tried this (without success) and noted the following:

I had to hold fn-F8 to get into the boot manager.

Although using the latest test build of VBox (5.1.x revision 116680) I get this message after entering the commands:

Read error 0xe
Error loading kernel cache (0xe)

I am getting the same issue as Lars is with the VM ending in
”
Read error 0xe
Error loading kernel cache (0xe)
”
After I execute the commands listed above.

Any idea on the fix?
VirtualBox 5.1.22 r115126 (Qt5.6.2) on macOS 10.12.5 host

Same issue
Read error 0xe
Error loading kernel cache (0xe)

Same issue. Error loading kernel cache.

Sorry that I did not come back to your questions. VirtualBox seems unable to boot the new macOS High Sierra Beta after migrating to APFS and there is no progress in getting that implemented. Therefore I decided to switch to VMWare Fusion instead, which I do not regret at all.

Just a note to confirm that this is working perfectly for me: Virtualbox 5.1.26
Thanks!!

I tried using latests Virtual Box (5.1.28) and current high sierra public release.
Now, there is no Locked Files folder inside of macOS Install Data, so i am not able to to boot to the new installer. Any clues?

Thanks for this blog entry. This was the smoking gun preventing me from upgrading my VirtualBox Sierra VM.

This worked great for me and allowed to create a new High Sierra VM. I was not upgrading. I had to make sure SSD was not enabled in VirtualBox preferences otherwise High Sierra would automatically want to migrate to APFS.

thanks a lot for your help

Great how-to, worked for me, but hitting F12 at the right time is very hard, so I made a snap-shot of the VM right before the reboot. That way you can avoid having to re-download the upgrade a couple of times.

I still needed to ram the F12 as fast as I could to make the EFI shell option appear.

`VBoxManage modifyvm OSX –bioslogodisplaytime 10000` –> Does not seem to work

I’m stuck here…
I had a OS X 10.12 on VMWare and started to upgraded to 10.13. When I cam back I saw the blue screen (boot menu). And failed to use your instructions, since there is no fs1 reachable in the internal shell. fs0 and blk0 to blk3. And it seems they are empty! What can I do here?

These instructions were written for VirtualBox and macOS 10.13 Developer Beta before APFS became mandatory. As far as I know, the VirtualBox EFI BIOS still does not support APFS. Personally I switched to VMWare Fusion due to this.

One thing you could try in VIrtualBox is to remove the checkbox on “Solid-state drive” in the storage settings of the VM. Then the High Sierra installer should no longer try to upgrade the disk to APFS, but leave it as HFS.

Following these steps, a message appears when run boot.efi –> “does prinf works??” and back to command line.
after that I type reboot and nothing happens, I’m in the same version.

I have the same problem as Pedro – “does printf works. ” and hangs…Any Idea what to do?

-I manually downloaded the combo update package 10.13.3 from Apple and launched it in the VM.
-The first part of update completed successfully, than it asked for restart.
-I restarted, entered the VirtualBox EFI Shell and launched boot.efi manually from the indicated path.
-After some work, message appears “macOS could not be installed on your computer – The path […]OSInstall.mpkg appears to be missing or damaged” (e.g. https://user-images.githubusercontent.com/192271/27255121-5811f2b4-538f-11e7-8117-9401bc9a7a80.png)
-I pressed Restart and the VM rebooted to High Sierra 10.13 (no update).

I think we are close to target, but some details are still missing to complete the update successfully.

Yes Yes Yes, thank, works perfectly.

first try I got kernel error like others. Tried second time and it worked don’t know what exaclty the reason for it. thanks

This was the solution I needed to upgrade from high sierra 10.13 to 10.13.4 using Virtual Box 5.2.8
Worked great! Thanks

I found the solution to “does printf works”

You can boot from instalation disk without shell, just open “boot from file” and find boot.efi on instalation disk.

@Babak Vandad: Did you see any error codes in the output? If so, was one of them ID10T?

The error
“Read error 0xe
Error loading kernel cache (0xe)”
can be solved by upgrading to the latest version of the Virtual box.

Thanks! This worked for me on VirtualBox going from 10.12 to 10.13 not in the Beta.

Thank you. Worked like a charm.

Thank you. It work with VirtualBox 5.2.8

Thank you!
It works, even it’s not worked from the first attempt.
The main cause of the fault was an old version of virtual box. With new Virtual Box (v 5.2.10) all goes well

My way of reaching 10.13.4 of Mac OS Sierra (probably you need last because of Xcode requirements)

upgrade Virtual Box to 5.2.10
do MacOs Recover
do Upgrade -> F2 …

I got this working.

Virtual Box – 5.2.12

Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

Every time I tried the above I could not get it to work and I received the error – error loading kernel cache 0x9 VirtualBox.

I did a bit of research and others were having the same issue, however, no one could get it to work.

What I did then was the following

Ran the update, reboot the machine and F12’ed into the boot manager.

I turned off the Virtual Machine and closed VBox

I then tried the following.

Opened CMD as admin and ran the following commands, these were the same commands needed when originally installed the Mac onto Vbox

VBoxManage.exe modifyvm “Mac” –cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “MacBookPro11,3”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-2BD1B31983FE1663”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

Once the commands complete, I started the VM on VBox and F12’ed into boot managed and followed the same procedure

Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

This time it worked and boot into the install/update – Took about 45 min +-

Hope that helps anyone.

I tried @Ghost’s solution and I got the “does printf work?” message.
Then I tried @Pedro’s “I found the solution to does printf work” and I *still* got the “does printf work?”

Then, I restored form snapshot, booted into the old version, started the install again, On bootup I tried Pedro’s solution to boot from file and this time it worked!

Thanks a lot to Ghost (2018-05-12 at 12:29) it worked for me with VB 5.2.12

The right first command is
VBoxManage.exe modifyvm “Mac” –cpuid-set 00000001 000306a9 04100800 7fbae3ff bfebfbff

Thanks a lot, worked with 10.14 beta. Not finished the installation yet, but the installer is up and running 👍🏼

I struggled to update macOS but finally worked it out.

You will find that any updates you apply will disappear after reboot as if they didn’t apply. You have to do the following as the update only completes after a reboot done in a certain way.

1) Download the update from the Apple website or apply from the App store.
2) When promoted to re-boot, press the F12 immediately after the restart, make sure the keyboard is captured in Virtualbox.
3) Press ESC key to stop the auto boot before the countdown finishes. You only have a few seconds to do this.
4) In the BOOT MANAGER option choose EFI Internal Shell.
5) Do the following at the shell command line:
fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

The system should then boot and continue the install and you are done. It is very important that you do all this on the first re-boot after applying the initial update as the update files are copied ready to complete the process. Miss the first boot and you will have to start again.

worked exactly as you described it! thanks mate!

To update mac os follow the below steps. If you will try to upgrade it normaly it would be locked by Apple and you will get the old version that you are currently running. To upgrade use the bellow steps:

Follow these steps to get around this problem:
1. Boot the VM normally in VirtualBox.
2. Open “Install macOS 10.13 Beta.app”, click through until you get to “Restart”.
3. As soon as the screen turns black, start to hammer the window+r key. Make sure your keyboard is grabbed by the VM.
4. If you managed to hit window+r at the right time, the VirtualBox EFI should pop up. If the VM starts up normally, go back to step 2.
5. Now use your arrow keys to select Boot Manager and hit Return, then launch the EFI Internal Shell from there.
6. Inside the shell, type the following commands:
Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

@Ghost’s solution worked for me. Thanks!

@kundan’s worked for me.

Thanks Rainer Müller. This worked for me just fine. I even was surprised didn’t get first “restart” .. system just restarted, I didn’t repeat from step (2) , I just restarted again and hit F12, followed procedure and in aout 90 minutes system rebooted to High Sierra … !! fantastic.

Updating from High Sierra 10.x to the latest update through the store, it won’t boot anymore.
tried F12 and the folder is not there, since it was a 2.6 Gb update.

Anyway to get this update to work?

Using VirtualBox 5.2.18. I had High Sierra 10.13.4 installed and working well, but 10.13.6 would not install from the App Store. I found this post when searching, and the steps listed worked first time. Thanks for the post!

F12 just won’t work. Don’t know what I’m doing wrong… :/

Windows+R does nothing either. I guess @kundan meant HOST+F12 so i tried that (restarting the machine upon restart). I have to press ESC right after that to enter the boot menu but after launching boot.efi i end up getting a kernel cache error.

thank you @kundan this worked perfectly. F12 is the key that I used to get in.

Has anyone got this working with Mojave?

Im getting this error:

ERROR. Load prelinked with status 0x800000000000000e
Error loading kernel cache (0xe)

I tried to upgrade to Mojave from Sierra via the appstore and it crashed my partition. EFI manager did not recognize FS1 or FS2.

This is not working in VirtualBox 5.2.18. Reboots endlessly.

I was getting the Error. Load prelinked kernel with status 0x800000000000000e while trying to upgrade to Mojave MacOs on a VirtualBox virtual machine. Turns out I had the older USB 2 compatibility in the settings for VirtualBox.

If you run into this issue turn off the VM, go into VirtualBox settings USB and select USB 3.0 controller. Restart the VM and issue should be solved.

me stuck with 10.13.2
Upgrade to mojave by following the step above leaves with
ERROR. Load prelinked with status 0x800000000000000e
Error loading kernel cache (0xe)

Has anybody been able to upgrade to Mojave yet ?

This is great, you can also get to it from “Boot Maintenance” > “Boot From File” and navigating to the boot.ini visually if that’s easier.

I finally managed to get beyond “Error loading kernel cache (0xe)”.
The solution was to entirely delete the “macOS Install Data” Folder and simply restart the update in sierra.
But this folder isn’t to delete easily.

I did:
1. Boot into macOS Recovery Mode as describled in this blog post
2. Open a Termial (Menubar: Utilities->Terminal)
3. run “csrutil disable”
4. run “rm -rf “macOS Install Data”
5. run “csrutil enable”

reboot normally, run Mojave installer again, on first reboot follow the instructions in this blog post

Thanks for this post.
I tried it like described above.

First time i ran into
“Read error 0xe
Error loading kernel cache (0xe)”

But just tried it again and second time it worked.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Welcome!

This the personal blog of Rainer Müller, also known by his nickname raimue. This is the space where I publish what does not fit into a tweet.

Источник

• Create Bootable USB

  • Code:

    sudo /Applications/Install macOS Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB -- /Applications/Install macOS Mojave.app -- nointeract && say Done.

• Clover Settings:
  • Boot:
    • Verbose;
    • dart=0;
    • nv_disable=0;
    • kext-dev-mode=1;
    • GraphicsEnabler=No;
    • XMPDetection = No.
  • Cpu:
    • C6.
  • Devices: (Not Enabled = [ ] — Enabled = [-] — Full Enabled [✓])
    • Inject (Full Enabled);
    • Add ClockID (Full Enabled);
    • FixOwnership (Full Enabled);
  • Gui: (Not Enabled = [ ] — Enabled = [-] — Full Enabled [✓])
    • Enabled (Full Enabled);
    • Screen Resolution: 1920×1080;
  • Kernel and Kext Patches: (Not Enabled = [ ] — Enabled = [-] — Full Enabled [✓])
    • Apple RTC (Full Enabled);
    • KernelPm (Full Enabled);
  • SMBIOS:
    • iMac(18,3);
  • System Parameters:
    • Inject Kexts = Yes;
    • Inject System ID;
• Used Kexts:
  • FakeSMC
  • FakePCIID
  • NVIDIA WEB
  • LILU
• BIOS:
  • VT-d = Disabled;
  • XHCI Hand-Off = Enabled;
  • Legacy USB Support: Enabled;
  • Hard Disk: AHCI Mode;
  • Selection Mode: Legacy + EUFI;

Clover Install Log:

Full Error Log:

Edited February 1, 2019 by Fede1132

Я загружал образы Mojave и High Sierra, оба не хотели устанавливаться. Скачивал образ системы в .rdr формате сразу с Clover’ом и через R-DriveImage пилил, как нужно, без ошибок.

Настроил биос и пробовал запустить: на Mojave были ошибки такого рода (каждый раз новая):

Error loading kernel cache

Error!!! load prelinked kernel with status (0x...)

allocating 0x11c00 pages at 0x0000000009167000 alloc type 2

attempting system restart... Mach reboot

Бывало, что просто повисла с минуту, появлялись артефакты на экране и знак запрета.
Всплывали так же в логе какие-то ошибки про ACPI, как вы уже поняли я много тыкал наугад в Config’ах.

В High Sierra уже даже появилось «яблочко» на нескольких конфигах (uefi config и ещё какой-то), но при достижении прогресс баром ~80% появлялся единый знак запрета (фотографии прилагаются), остальные конфиги, которые я пробовал выдавали ошибки, которые я указал выше для Manjaro.
Если Вы хоть что-нибудь знаете по поводу одной из этих ошибок, я буду только рад Вашей помощи.

• Intel Pentium G5400
• Nvidia GeForce GT1030
• MSI H110M
• Kingston DDR4 8GB
• SSD + HDD = 1250GB

[