New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VirtualBox with High-Sierra fails, "Attempting system restart...MACH Reboot" or repeating reboots #52

Closed
mwaeckerlin opened this Issue Sep 6, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@mwaeckerlin
Copy link

mwaeckerlin commented Sep 6, 2018

VirtualBox: tried with two versions:

One thing is new: Now VirtualBox pretends to explicitely support macOS 10.13 High Sierra (64bit):
grafik

Information in README.md is outdated:

If for High Sierra you encounter boot / EFI problems, restart the VM and hit F12 to get to the VirtualBox boot manager. Select EFI In-Terminal Shell and run:

Shell> fs1:
FS1:\> cd "macOS Install Data"
FS1:\macOS Install Data\> cd "Locked Files"
FS1:\macOS Install Data\Locked Files\> cd "Boot Files"
FS1:\macOS Install Data\Locked Files\Boot Files\> boot.efi

Neither drive (fs1:) nor path (macOS Install Data) exists:

virtualbox_mac os x high sierra - failed_06_09_2018_09_18_56

I tried according to the documentation and ended with Attempting system restart...MACH Reboot, see snapshots from the screen-video:

vlcsnap-2018-09-06-09h31m52s073
vlcsnap-2018-09-06-09h32m04s182
vlcsnap-2018-09-06-09h33m21s439
vlcsnap-2018-09-06-09h33m35s536
vlcsnap-2018-09-06-09h33m44s595

Next I tried a new image without the CPU-patch, so I did not enter the following command:

  1. In Terminal, run the command VBoxManage modifyvm VM_NAME --cpuidset 00000001 000306a9 00020800 80000201 178bfbff (where VM_NAME is the exact name of the VM set in step 4) so the VM has the right CPU settings for macOS.

It then goes further, but still fails and constantly reboots, here some screenshots from the video:

vlcsnap-2018-09-06-09h38m09s412
vlcsnap-2018-09-06-09h38m22s838
vlcsnap-2018-09-06-09h38m37s909
vlcsnap-2018-09-06-09h38m47s025
vlcsnap-2018-09-06-09h38m56s149
vlcsnap-2018-09-06-09h39m03s730
vlcsnap-2018-09-06-09h39m11s153
vlcsnap-2018-09-06-09h39m17s964
vlcsnap-2018-09-06-09h39m24s812
vlcsnap-2018-09-06-09h39m30s893
vlcsnap-2018-09-06-09h39m38s940
vlcsnap-2018-09-06-09h39m58s527
vlcsnap-2018-09-06-09h40m11s407
vlcsnap-2018-09-06-09h40m23s550
vlcsnap-2018-09-06-09h40m30s904
vlcsnap-2018-09-06-09h40m36s522

@mwaeckerlin

This comment has been minimized.

Copy link
Author

mwaeckerlin commented Sep 6, 2018

GitHub does not allow to upload the videos directly, but I could upload them as ZIP, so sorry for the unneccessary extra package. These are the videos from where I took the screenshots above:

Mac OS X High Sierra - failed.zip
Mac OS X High Sierra-2018-09-05T13-59-27-928531000Z.zip

@xtmq

This comment has been minimized.

Copy link

xtmq commented Sep 9, 2018

The same thing for me...

@crou

This comment has been minimized.

Copy link

crou commented Sep 11, 2018

Got the same thing, but I was able to fix it by running these commands:

VBoxManage modifyvm VMNAME--cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage setextradata VMNAME "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"
VBoxManage setextradata VMNAME "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata VMNAME "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple"
VBoxManage setextradata VMNAME "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata VMNAME "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

After that, I started the VM, the boot process was successful and was able to get the installer.

@mwaeckerlin

This comment has been minimized.

Copy link
Author

mwaeckerlin commented Sep 14, 2018

@crou, thank you, that solves the problem so far! Currently the installation is running.

Another problem I had:

  • First go to the disk-tool to format the harddisk
  • Then go to the installation

You can't setup the harddisk during the installation and you can't go back to the disk-tool without reboot…

Here for all to copy paste, it's the same as above from @crou, but with a variable for easier pasting:

VMNAME='Your VM name here'
VBoxManage modifyvm ${VMNAME} --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage setextradata ${VMNAME} "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"
VBoxManage setextradata ${VMNAME} "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata ${VMNAME} "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple"
VBoxManage setextradata ${VMNAME} "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata ${VMNAME} "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

MartinLeedotOrg added a commit to MartinLeedotOrg/macos-virtualbox-vm that referenced this issue Sep 24, 2018

@terminatorul

This comment has been minimized.

Copy link

terminatorul commented Nov 20, 2018

After setting the above EFI values on my Ubuntu, I got errors when starting the virtual machine:

Invalid config value(s) for the EFI device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES).

The fix was to to add my user to group vboxusers, as it looks like on Ubuntu I was not a group member by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment