Jump to content
ErmaC

Clover General discussion

19,662 posts in this topic

Recommended Posts

About spectre / meltdown slowdown:

https://reverse.put.as/2018/01/07/measuring-osx-meltdown-patches-performance/

 

Properly benchmarked. It means that all syscalls will be drastically slower, so assumingly audio i/o, disk i/o, memory allocation?. The speed will be even more reduced with 10.13.3, since it contains more security mechanisms. I hope they will continue to trying to find faster ways, but i doubt that, because they already developed for the last 6 months or so.

 

I am still not entirely sure, why it seens to be not enough to simply patch the outside communicating apps like browser, email, etc.

 

Please notice that running geekbench is not an accurate measuring for this problem.

Share this post


Link to post
Share on other sites
Advertisement

Yeah, it's not persistent unless it's flashed with the firmware. ...

 

 

It alone is not going to protect from the vulnerability, because the problem is in the actual silicon of the chip, so the memory map can be side-channeled through speculation. The memory map needs to be separated from any other memory map if you want to not have this vulnerability.

"Cache me outside, how 'bout dat?"  :wink_anim: 

 

Thanks for all your great work Apianti, Slice, Vit, RM, RHM, DFritz, CCPW, et al.

 

Now, about plug and play Thunderbolt...?

Share this post


Link to post
Share on other sites

Hey guys, is there a standard way to pass arguments to the binary of a macos kext? Or a standard section for that in the info.plist of the kext?

There are several ways. All of them "standard".

Constant parameters written into info.plist IOKitPersonality section. See hundreds macOS examples.

Tunable parameters can be passed through DeviceTree. This is the way TouchPad get options from PrefPane.

DynamicParameters can be passed changed by IOUserClient interface. (RadeonDump for example).

As well it can be shared memory access (VoodooHDA PrefPane).

Moreover it can be SMC exchange, Apple's way.

Or other methods...

 

Now, about plug and play Thunderbolt...?

IOPCIFamily.kext assumes fixed PCIe configuration while Thunderbolt devices assumed to be PCIe devices.

Share this post


Link to post
Share on other sites

There are several ways. All of them "standard".

Constant parameters written into info.plist IOKitPersonality section. See hundreds macOS examples.

Tunable parameters can be passed through DeviceTree. This is the way TouchPad get options from PrefPane.

DynamicParameters can be passed changed by IOUserClient interface. (RadeonDump for example).

As well it can be shared memory access (VoodooHDA <-> PrefPane).

Moreover it can be SMC exchange, Apple's way.

Or other methods...

 

Thanks a lot for that info!  I was referring to these findings in NVDAResmanWeb.kext. What would you assume is the correct way to pass these arguments to that kext?

Share this post


Link to post
Share on other sites

 

Ha, I know why!

 

On your config.plist you have to set Scan > tool  to true:

<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<true/>
			<key>Linux</key>
			<false/>
			<key>Tool</key>
			<true/>
		</dict>

Share this post


Link to post
Share on other sites

 

Ha, I know why!

 

On your config.plist you have to set Scan > tool  to true:

<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<true/>
			<key>Linux</key>
			<false/>
			<key>Tool</key>
			<true/>
		</dict>

Thank you, that was it. I never could have guessed.

 

EDIT : My available available region is: 0000000100000000 (00000000) I guess I do not need any slide value.

Share this post


Link to post
Share on other sites

i wonder one.

if we set lang in config without emul, always shown lang set window.

 

 

SherlocksuiMBP2:~ sherlocks$ nvram -p

fakesmc-key-MSWr-ui8 %00

fakesmc-key-RPlt-ch8* j130%00%00%00%00

fakesmc-key-RBr -ch8* 2016mb%00%00

EFILoginHiDPI %00%00%00%00

fakesmc-key-#KEY-ui32 %00%00%00%11

SystemAudioVolumeDB %de

fakesmc-key-BATP-flag %00

fakesmc-key-MSTc-ui8 %00

fakesmc-key-BNum-ui8 %01

security-mode none

csr-active-config w%00%00%00

fakesmc-key-$Num-ui8 %01

fakesmc-key-MSFW-ui8 %01%00

fakesmc-key-REV -ch8* %026%0f%00%00%97

fakesmc-key-MSPS-ui16 %00%03

fmm-computer-name Sherlocks%ec%9d%98 MacBook Pro (2)

backlight-level i%05

bootercfg (%00

fakesmc-key-$Adr-ui32 %00%00%03%00

fakesmc-key-EPCI-ui32 %09 %f0%00

bluetoothActiveControllerInfo z%e0%89%04%00%00%00%000%14%ac%d1%b8%e2%a4%d0

fakesmc-key-MSAc-ui16 %00%00

boot-args

SystemAudioVolume (

fakesmc-key-RMde-char A

fakesmc-key-BBIN-ui8 %01

flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00

specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00%00H%06%00%00%00%00%00%00(*%08%00%00%00%00%8f%0a5%8c%c6P%e6C%ad%a6^%16p%d2e%d9%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%bd%d2_[%80%18%0e6%8a%cd%f1%f1_%b8%9c%b7%7f%ff%04%00

 

fakesmc-key-BEMB-flag %01

 

 

i can't see prev-lang:kbd part. if i use emul, system set i want to lang.

 

because of this part?

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/DataHubCpu.c#l212

 

can we consider it?

 

thanks in advance.

 

EDIT1

seems that it causes lang complex(kor+eng) like this.

i first see this issue since new aptiov2 without emul

 

EDIT2

new aptiov2 + emul

 

 

SherlocksuiMBP2:~ sherlocks$ nvram -p

fakesmc-key-BEMB-flag %01

fakesmc-key-RPlt-ch8* j130%00%00%00%00

fakesmc-key-RBr -ch8* 2016mb%00%00

EFILoginHiDPI %00%00%00%00

fakesmc-key-#KEY-ui32 %00%00%00%11

SystemAudioVolumeDB %de

fakesmc-key-BATP-flag %00

EmuVariableUefiPresent Yes

fakesmc-key-MSTc-ui8 %00

prev-lang:kbd ko:0

fakesmc-key-BNum-ui8 %01

security-mode none

csr-active-config w%00%00%00

fakesmc-key-$Num-ui8 %01

fakesmc-key-MSFW-ui8 %01%00

fakesmc-key-REV -ch8* %026%0f%00%00%97

fakesmc-key-MSPS-ui16 %00%03

fmm-computer-name Sherlocks%ec%9d%98 MacBook Pro (2)

backlight-level i%05

bootercfg (%00

fakesmc-key-$Adr-ui32 %00%00%03%00

fakesmc-key-EPCI-ui32 %09 %f0%00

bluetoothActiveControllerInfo z%e0%89%04%00%00%00%000%14%ac%d1%b8%e2%a4%d0

fakesmc-key-MSAc-ui16 %00%00

boot-args

SystemAudioVolume (

fakesmc-key-RMde-char A

fakesmc-key-BBIN-ui8 %01

specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00%00H%06%00%00%00%00%00%00(*%08%00%00%00%00%8f%0a5%8c%c6P%e6C%ad%a6^%16p%d2e%d9%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%bd%d2_[%80%18%0e6%8a%cd%f1%f1_%b8%9c%b7%7f%ff%04%00

flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00

 

fakesmc-key-MSWr-ui8 %00

 

 

i see prev-lang:kbd ko:0 in nvram

but still

 

EDIT3

i have to lang reset from setting after update macos10.13.3 beta4 with aptiov2 except emul

1. go setting and lang

2. add english

3. select kor lang(already exist) and remove english lang.

4. reboot

5. get full kor lang on osx

 

there is no problem of lang on this combination before.

old aptiov2+osxemuvaribalesuefi.efi

 

i'm still suspecting this part.

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/DataHubCpu.c#l212

 

Well, when you installed and had emulated NVRAM you selected some value, remember? When you stopped emulating NVRAM that value was left in nvram.plist somewhere, different value was written from clover if you set language key, and if you set ":0" after that means US ANSI keyboard, I believe. So it makes sense you would need to go in and set the correct language and keyboard settings again, since they were kinda removed from your NVRAM by side effect of the switch back to native from emulated. Read like three lines below where you linked in the source.

 

About spectre / meltdown slowdown:

https://reverse.put.as/2018/01/07/measuring-osx-meltdown-patches-performance/

 

Properly benchmarked. It means that all syscalls will be drastically slower, so assumingly audio i/o, disk i/o, memory allocation?. The speed will be even more reduced with 10.13.3, since it contains more security mechanisms. I hope they will continue to trying to find faster ways, but i doubt that, because they already developed for the last 6 months or so.

 

I am still not entirely sure, why it seens to be not enough to simply patch the outside communicating apps like browser, email, etc.

 

Please notice that running geekbench is not an accurate measuring for this problem.

 

Because what app doesn't communicate with icloud now or some other apple service? Their newest FIRMWARE for the iMacPro will require internet... I think that the entirety of the operating systems developer community and the chip engineers who have discussed the best way to solve this have probably come up with the best solution, separating the memory spaces so that they cannot be attacked. They will develop ways to make system calls less frequently and overall you are probably not even really going to notice anything once it settles down. Don't forget that software has a life cycle and macOS is currently going through a redesign phase anyway so it is kinda good that it happens during now, their next release will most likely be very excellent.

 

"Cache me outside, how 'bout dat?"  :wink_anim:

 

So dumb... lol.  :no:

 

Thanks for all your great work Apianti, Slice, Vit, RM, RHM, DFritz, CCPW, et al.

 

Now, about plug and play Thunderbolt...?

 

What about it? I mean like is it a thing? Or does it work? Or what? I mean that's not very specific....

 

Thank you, that was it. I never could have guessed.

 

What did you think the tool scan did then?

 

EDIT : My available available region is: 0000000100000000 (00000000) I guess I do not need any slide value.

 

That is not a valid region because it is above the 4GB barrier that a 32bit address can represent. You need to find a region in the range 0x100000 to 0x20200000.

Share this post


Link to post
Share on other sites

Well, when you installed and had emulated NVRAM you selected some value, remember? When you stopped emulating NVRAM that value was left in nvram.plist somewhere, different value was written from clover if you set language key, and if you set ":0" after that means US ANSI keyboard, I believe. So it makes sense you would need to go in and set the correct language and keyboard settings again, since they were kinda removed from your NVRAM by side effect of the switch back to native from emulated. Read like three lines below where you linked in the source.

 

you are right.
i just confirmed it. if i remove EmuVariableUefi-64.efi
there is no prev-lang:kbd key in nvram.
before i update beta4, i removed EmuVariableUefi-64.efi and nvram.plist to surely check where is problem.
 
and default kor lang before update beta4. when updating beta4, i saw english word example "install 14 minutes left".
after finished beta4, then booted, i just saw eng+kor combination of system part. example reboot dialog above pic.
 
when used EmuVariableUefi-64.efi, always correct lang shown example "설치 14분 남았습니다"
after finished beta4, then booted, i saw correct kor lang of system part without eng.
 
i used this combination of EmuVariableUefi-64.efi+old aptioV2 long time.
now, i returned old aptioV2 to avoid this issue after update lang issue. also i didn't notice keyboard problem that you mentioned keyboard. i just checked lang part.

<key>Language</key>

<string>ko:0</string>

 
thanks
 
EDIT1
this issue happen new aptiov1 and aptiv2.
i tested skylake laptop and sandy laptop.

Share this post


Link to post
Share on other sites

That is not a valid region because it is above the 4GB barrier that a 32bit address can represent. You need to find a region in the range 0x100000 to 0x20200000.

Share this post


Link to post
Share on other sites

 

There are more memory regions above, you need to press Pg Up. Or better yet, you need to export your memmap to a file. The instructions are a couple of pages back (basically enter fs0: ; cd EFI/CLOVER/misc ; memmap > memmap.txt and then mount EFI with the started system).

Share this post


Link to post
Share on other sites

I don't know why you showing me a picture of it makes it any more valid. First, the address can't go beyond 32bits so only eight hexadecimals, so 0x100000000 would be truncated to zero, which is definitely not valid. Second, the address has to be in the range 0x100000 to 0x20200000 aligned by 0x200000 because those are the only possible slide locations.

Share this post


Link to post
Share on other sites

I seems should not bother about slide value?

Available  0000000000100000-0000000082D1DFFF 0000000000082C1E 000000000000000F

Thanks a lot for that info!  I was referring to these findings in NVDAResmanWeb.kext. What would you assume is the correct way to pass these arguments to that kext?

You can send any argument to driver if it waits an argument from you.

Share this post


Link to post
Share on other sites

...

how is the noEFI setting passed to the nvidia web driver by clover? Is it a DSDT patch, or a binary patch or a argument passing?

 

Found this in clover source:

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/nvidia.c#l2414

DSDT Patch:

"NVDA,noEFI",
Buffer (0x05)
{
  "true"
},

or Clover Patch:

<key>Graphics</key>
     <dict>
	   <key>NvidiaNoEFI</key>
	   <true/>
     </dict>

Share this post


Link to post
Share on other sites

Hey slice,

 

how is the noEFI setting passed to the nvidia web driver by clover? Is it a DSDT patch, or a binary patch or a argument passing?

 

Found this in clover source:

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/nvidia.c#l2414

 

Looks like a device tree modification to me?

Yes, device tree modification.

 

 

Thanks. And what exactly is this DSDT key for:  

NVDA,Features

I have seen it in old DSDTs, but it seems to be still present in NVDAStartupWeb.

You may use AddProperties feature for this case.

Or modify DSDT, or create SSDT. At your will.

If you want it to be implemented in Clover then you should give me full explanation what is and for a what.

Share this post


Link to post
Share on other sites

What about OsxLowMemFixDrv? Is there anybody use it or it is obsolete?

 

 

hello Slice 

 

I use it in clover legacy for my old Packard Bell

Share this post


Link to post
Share on other sites

hello Slice

 

I use it in clover legacy for my old Packard Bell

Legacy Clover only using Drivers64 not Drivers64UEFI.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

USBMousseDxe-64 I have this on Drivers64 in my Packages

I have never needed it before so im unsure if its clover or the new dev beta build.

Even with the driver its slow, i have to have settings like this for decent movement.

post-1083558-0-09471600-1515669894_thumb.png

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

  • Similar Content

    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x 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
       
      Requirements
         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)
      eg
      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.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
      UPDATE macOS Catalina Beta DP3_19A501i:  For Catalina, @jpz4085 has made an automated batch file to create a Catalina VM in Windows with iMac 14,2 SMBIOS.  You can still use my macOS_iso_creator.tool on page 5 to make an installer ISO to attach to the VM.
       
       
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By JackBauer24
      Hello,
       
      I have installed OSx86 10.11 (El Capitan) on April 2016 on my Asus Z170 Deluxe system.
       
      For installation I used this Thread.
       
      I used it a lot and it worked well. Meanwhile I switched to Linux and I use Win10 time to time. So OSX was forgotten. Also it did not boot correctly anymore.
       
      Now I wanted to start with a fresh installation and use OSX more often again. I want to use OSX 10.13 High Sierra. Is it working on my Asus Z170 Deluxe? I have the same Hardware as of April 2016 only the graphics card was updated to a Nvidia GTX1080.
       
      My Hardware in detail: Asus Z-170-Deluxe (Bios 3801), i7-6700k, EVGA GeForce GTX 1080 SC GAMING ACX 3.0, Samsung 950 Pro/M2 NVME 512MB, HDD 4 TB)
      Can I use some of support files from the old thread for the installation (see attachment)? Can I still use  Clover 2.3k r3292 Special Edition v2 ? Or do I need a newer version?
       
      Has someone installed High Sierra successfully on the Asus Z170 Deluxe ?
       
      About some hints where to start I would be thankful.
       
      regards
      JackBauer24
       
      Z170DeluxeFiles.zip
×