Installation of clean OSX 10.12.4 fails.

[Socratis]

• Create a new OSX VM with the 10.11 template. Download the 10.12.4 installer from the AppStore. Use the installation script from ​Howto: Create OSX ISO from the OSX Install app
• Issue 1: the VM will not proceed with the installation, unless USB3 is specifically enabled in the template; the template needs an update (or a new 10.12 template) that makes USB3 mandatory.
• Issue 2: the VM gets stuck on the following:

  IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0
  

Some users have reported this error with previous OSX versions, when the Finder "kicks" them out of the system with that message and to the login screen. Will try to find the reference.

Please note that an OSX 10.12.3 will update just fine. The same client will fail. Nothing relevant in the logs unfortunately.

[ladybugz]

I am having the same issue 2: getting stuck at IOConsoleUsers: gIOSScreenLockState.... but using VirtualBox Version 5.1.20 r114629 (Qt5.6.2). Have tried changing several VirtualBox settings and nothing works.

[DenisFR]

The same for me.

[michielie]

<removed>

[michielie]

Working OSX Sierra VM config file

[VitalyM]

Tested "Working OSX Sierra VM config file" - hangs too. I attached hanging screenshot. BTW I tested 2 images created by ​https://forums.virtualbox.org/viewtopic.php?f=22&t=81443 and ​https://github.com/geerlingguy/macos-virtualbox-vm

[michielie]

<removed>

[Socratis]

@michielie
OSX installs are only supported on Apple hardware.
See: ​Important notice regarding Mac OS X as Guest.

[VitalyM]

As for me I use MacBook Pro (Retina, 15-inch, Mid 2014) + macOS Sierra 10.12.4 + the latest VirtualBox for today. See other people facing the same issue ​https://github.com/geerlingguy/macos-virtualbox-vm/issues/24

[Socratis]

@VitalyM
You posted that link 10 days ago. Still no solution there. Any particular reason you posted it again?

[VitalyM]

@socratis the first link is repository home - instruction I used to make iso. The 2-nd link is a particular issue.

[DenisFR]

The same with 10.12.5 and VB 5.1.22.

[petri]

Same config as DenisRF: 10.12.5 both as host and guest, VB 5.1.22

[Lars Sonchocky-Helldorf]

Same effect on both a early 2011 MBP running 10.10.5 and a mid 2014 MBP running 10.10.5 as host. Both get until this message when booting from a 10.12.5.iso which was created using said script.

[sector7gp]

Same Here! VB 5.1.22 over OSX 10.10.5

[sector7gp]

Replying to sector7gp:

Same Here! VB 5.1.22 over OSX 10.10.5

AND CRASHED MY PREVIEW INSTALLATION :S

[sector7gp]

Ok! SOLVED!!!! run the unintall scrip from your previews version, reboot ur mac and run the installer again! works for me

[Socratis]

Replying to sector7gp:

Ok! SOLVED!!!! run the unintall scrip from your previews version, reboot ur mac and run the installer again! works for me

I didn't notice your comment until today. Can you please explain in full detail what was "solved"? And how? Which "uninstall script" are you referring to? And which "installer"?

[franiu]

Still failing, VirtualBox 5.1.26 r117224, host macOS 10.12.5 (16F73).

Any new development on this?

[Socratis]

@franiu
Things in the open source world don't get to be secret. So, if there was a new development on this, you would have known it by now. Ergo, there is not.

Glad you subscribed to the ticket, but remember that either you provide a solution, or patience is a virtue.

[Fark]

+1

[joseluisbz]

Replying to sector7gp:

Ok! SOLVED!!!! run the unintall scrip from your previews version, reboot ur mac and run the installer again! works for me

Please put your procedure, Thank you.

[mm]

+1

[michaln]

It turns out that the macOS Sierra 10.12.4 (and later) installer won't boot on a system where the EFI firmware vendor is "EDK II", which includes VirtualBox. That behavior is specific to the Sierra 10.12.4+ installer and does not apply to an older Sierra install updated to 10.12.4 or later. Whether this behavior is intentional is something only Apple can answer.

High Sierra beta 6 (build 17A344b) does not exhibit this behavior, therefore no fix is currently planned on the VirtualBox side.

The USB problem (installer hangs earlier unless xHCI emulation is used) is probably unrelated.

[michaln]

The problem with USB is also specific to the Sierra (and High Sierra) installers, but it happens in 10.12.3 already. Basically the installer boots if the VM is configured with either xHCI or OHCI, but not with OHCI + EHCI. Again the installed OS behaves differently.

[spoorcc]

+1

[Uli]

+1

[widhaya3]

Replying to socratis:

• Create a new OSX VM with the 10.11 template. Download the 10.12.4 installer from the AppStore. Use the installation script from ​Howto: Create OSX ISO from the OSX Install app
• Issue 1: the VM will not proceed with the installation, unless USB3 is specifically enabled in the template; the template needs an update (or a new 10.12 template) that makes USB3 mandatory.
• Issue 2: the VM gets stuck on the following:

  IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0
  

Some users have reported this error with previous OSX versions, when the Finder "kicks" them out of the system with that message and to the login screen. Will try to find the reference.

Please note that an OSX 10.12.3 will update just fine. The same client will fail. Nothing relevant in the logs unfortunately.

I try to change paravirtualization interface to "None", and it's work.

#https://gist.github.com/arobb/447a962af4f07ef81e79987d686275e5
#https://www.insanelymac.com/forum/topic/292170-how-to-spoof-real-mac-in-vmware/
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F22589C8"
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "CK1156I6DB6"
VBoxManage modifyvm "$NAME" --paravirtprovider none

#REVERT BACK WHEN FINISH INSTALLATION
VBoxManage modifyvm "$NAME" --paravirtprovider default

[Socratis]

Replying to widhaya3:

I try to change paravirtualization interface to "None", and it's work.

No it doesn't. You didn't try with an official 10.12.x application installer, you tried with a Hackintosh, which is not supported (see: ​Mac OS X guest on a Windows Host). That's why you need all the extra settings like the "DmiBoardProduct" and "DmiSystemSerial". You don't need those if you're running VirtualBox on a Mac.

If you try to run an original 10.12.5 OSX installer, it fails with the following message, even if the Paravirtualization is set to "None":

       
       
       ***********************************************************
       This version of Mac OS X is not supported on this platform!
       ***********************************************************
       Reason: VirtualBox
       
       

[widhaya3]

Replying to socratis:

Replying to widhaya3:

I try to change paravirtualization interface to "None", and it's work.

No it doesn't. You didn't try with an official 10.12.x application installer, you tried with a Hackintosh, which is not supported (see: ​Mac OS X guest on a Windows Host). That's why you need all the extra settings like the "DmiBoardProduct" and "DmiSystemSerial". You don't need those if you're running VirtualBox on a Mac.

If you try to run an original 10.12.5 OSX installer, it fails with the following message, even if the Paravirtualization is set to "None":

       
       
       ***********************************************************
       This version of Mac OS X is not supported on this platform!
       ***********************************************************
       Reason: VirtualBox
       
       

I test with original 10.12.6, download from ​https://itunes.apple.com/app/id1127487414?mt=12 . (Sorry, my host is Debian.)

[Socratis]

@widhaya3
So, you are on a Mac and you tried the original 10.12.6 and it worked?

If so, can I have both the .vbox for the VM and a complete VBox.log from a start/login/shutdown/ShowLog session? As well as the full procedure of the installation?

It may be even better if you posted the instructions on the forums, in the ​HowTo: Create OSX ISO from the OSX Install app, there are a lot more people "listening" there, plus I have that note:

WARNING: The script will work with OSX 10.12.4, .5 and .6, but VirtualBox will *not* boot from such an ISO for reasons yet unknown. There is a bug report open for that: #16644: Installation of clean OSX 10.12.4 fails. If you have any idea on how to make this work, I'd appreciate a comment.

PS. Please don't quote the whole previous message if it's not necessary, it adds unnecessarily to the length of the post... ;)

[widhaya3]

Replying to socratis:

@widhaya3
So, you are on a Mac and you tried the original 10.12.6 and it worked?

Nope. I'am on Debian (linux-4.18.0-3-amd64, virtualbox-5.2.20-125813~Ubuntu~bionic, cpu: Ryzen 1700), sorry. I test with original 10.12.6 and yes, it worked.

If so, can I have both the .vbox for the VM and a complete VBox.log from a start/login/shutdown/ShowLog session? As well as the full procedure of the installation?

Sorry again. I've just delete it all, now I'm on Mojave. But I will try to re-install it tomorrow that I will start with El Capitan.

It may be even better if you posted the instructions on the forums, in the ​HowTo: Create OSX ISO from the OSX Install app, there are a lot more people "listening" there, plus I have that note:

My English is truely badddd. I cannot, anyway, I've written a very quick & dirty short note for this at: ​https://www.thaitux.info/node/945

[widhaya3]

vbox and logs files of both El Capitan and Sierra guest.

[widhaya3]

Replying to socratis:

If so, can I have both the .vbox for the VM and a complete VBox.log from a start/login/shutdown/ShowLog session? As well as the full procedure of the installation?

STEP OF INSTALLATION

### AT El Capitan ###

#LAUNCH SAFARI GO TO ​https://itunes.apple.com/app/id1127487414?mt=12

#DOWNLOAD Sierra -> /Applications/Install macOS Sierra.app

#LAUNCH TERMINAL

FILE=Sierra
APPDIR=/Applications/Install\ macOS\ Sierra.app
SIZE=8000

#CREATE IMAGE AND MOUNT
hdiutil create -o /tmp/$FILE -size ${SIZE}m -layout SPUD -fs HFS+J  # -> /tmp/$FILE.dmg
hdiutil attach /tmp/$FILE.dmg -noverify -nobrowse   # -> /Volumes/untitled

#MOUNT InstallESD (IT MAY ALREADY MOUNT AFTER FINISH DOWNLOAD Sierra)
hdiutil attach "$APPDIR/Contents/SharedSupport/InstallESD.dmg"  # -> /Volumes/OS X Install ESD
ESD="/Volumes/OS X Install ESD"

#RESTORE BaseSystem TO IMAGE
asr restore -source "$ESD/BaseSystem.dmg" -target /Volumes/untitled -noprompt -noverify -erase    #/Volumes/untitled -> /Volumes/OS X Base System

#COPY PACKAGES
rm "/Volumes/OS X Base System/System/Installation/Packages"
cp -av "$ESD/Packages" "/Volumes/OS X Base System/System/Installation/"

#COPY ALL dmg/chunklist FILES
cp -av "$ESD/BaseSystem.dmg" "/Volumes/OS X Base System/"
cp -av "$ESD/BaseSystem.chunklist" "/Volumes/OS X Base System/"
cp -av "$ESD/AppleDiagnostics.dmg" "/Volumes/OS X Base System/"
cp -av "$ESD/AppleDiagnostics.chunklist" "/Volumes/OS X Base System/"

#UNMOUNT ALL
hdiutil detach "/Volumes/OS X Base System"
hdiutil detach "$ESD"

#RESIZE IMAGE FOR BEST FIT
hdiutil resize -size `hdiutil resize -limits /tmp/$FILE.dmg | tail -n 1 | awk '{ print $1 }'`b /tmp/$FILE.dmg

#CONVERT IMAGE TO CDR
hdiutil convert /tmp/$FILE.dmg -format UDTO -o /tmp/$FILE  # -> /tmp/$FILE.cdr

#COPY TO HOST
scp /tmp/$FILE.cdr USER1@HOST1:/WHERE/TO/STORE/IMAGE

#IF YOU WANT UNIQUE IDENTIFIERS OF Sierra MACHINE, PLEASE INSTALL Chameleon Wizard
#FOLLOW STEP AT https://www.insanelymac.com/forum/topic/292170-how-to-spoof-real-mac-in-vmware/
#YOU WILL GET PRODUCT NAME, BOARD PRODUCT AND SERIAL
#KEEP IT, WILL USE LATER WHEN CREATE Sierra VM

#SHUTDOWN

### AT Debian HOST ###

#CREATE VM IN VirtualBox , ATTACH cdr FROM ABOVE, THEN RUN

VM_RES="1280x960"   #EXAMPLE
NAME="NAME OF VM"   #EXAMPLE
VBoxManage modifyvm "$NAME" --usbxhci on --firmware efi --chipset ich9 --mouse usbtablet --keyboard usb --vram 128 --cpus 2 --memory 4096 --boot1 dvd --boot2 disk --boot3 none --boot4 none --cpu-profile "Intel Core i7-6700K" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage setextradata "$NAME" "CustomVideoMode1" "${VM_RES}x32"
VBoxManage setextradata "$NAME" VBoxInternal2/EfiGraphicsResolution "$VM_RES"
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple"
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "*** censored ***(c)AppleComputerInc"
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

#FOR Sierra: SOLVE PARAVIRTUALIZATION BUG
#https://gist.github.com/arobb/447a962af4f07ef81e79987d686275e5
#https://www.insanelymac.com/forum/topic/292170-how-to-spoof-real-mac-in-vmware/
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F22589C8"
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "CK1156I6DB6"
VBoxManage modifyvm "$NAME" --paravirtprovider none
#REVERT BACK WHEN FINISH INSTALLATION
#VBoxManage modifyvm "$NAME" --paravirtprovider default

#NOW YOU CAN BOOT Sierra INSTALLER
#MAY STUCK ON "WAIT FOR DICT..." OR KERNEL PANIC
#JUST REBOOT

[Socratis]

Replying to widhaya3:

cpu: Ryzen 1700

No Mac has an AMD CPU yet...

00:00:00.466489 DMI Product Name: To Be Filled By O.E.M.

This is not a Mac, just as I suspected, and I told you, in my original message.

You're using an unsupported setup. Unfortunately OSX guests are only supported on Apple hardware (which you do not have). See: ​Mac OS X guest on a Windows Host.

[widhaya3]

vbox and logs files of Sierra VM on MacBook Retina.

[widhaya3]

@socratis

I want to know the result on MacBook too. So I went to the shop near my house, borrow his machine and try to install on MacBook Retina (Core i5 Ram 8G) using my "Sierra.cdr" image file from Debian. The step of installation was the same as above, except I must disable USB. And yes!, I can install it. You can view in the file "vbox-log-macbook-pro-retina.tar.gz". Hope this help. :)

[aeichner]

The original report should be fixed as the recent VirtualBox 6.1 release has improved macOS guest support. Closing, please create new tickets if there any issues.