Jump to content
fusion71au

Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host

110 posts in this topic

Recommended Posts

Hi, I'm not really understanding how to install clover. When I turn EFI off and put in the commands in the command line, it shows a fatal error so I can't even open the vm to install clover efi. Any help?

Share this post


Link to post
Share on other sites
Advertisement

Hey,

 

So I've been following many guides around here but I don't understand how to prepare MacOS.vmdk like you did. What's on it? I'd like to make one like this myself.

 

Also, I'd like to thank all of you for the excellent job done around here. All InanelyMac users. :)

 

EDIT: I've just followed above tutorial for HighSierra from scratch and gone as far as doing the accepting the agreement and then turning off on MACH Reboot message. I've unmounted the BaseSystem.vmdk, started machine again and all I get is black screen. Been hanging like that for few minutes right now, with no feedback at all. What could have possibly gone wrong?

 

Cheers,

Furai

Share this post


Link to post
Share on other sites

Hi, I'm not really understanding how to install clover. When I turn EFI off and put in the commands in the command line, it shows a fatal error so I can't even open the vm to install clover efi. Any help?

 

Legacy Clover no longer works in VirtualBox 5.1.x and VirtualBox 5.2.x (causes red screen error).  Need to install in UEFI mode only and press <F12>, select "EFI Hard Drive" from Boot Manager to start VM with Clover.

 

 

Hey,

 

So I've been following many guides around here but I don't understand how to prepare MacOS.vmdk like you did. What's on it? I'd like to make one like this myself.

 

Also, I'd like to thank all of you for the excellent job done around here. All InanelyMac users. :)

 

EDIT: I've just followed above tutorial for HighSierra from scratch and gone as far as doing the accepting the agreement and then turning off on MACH Reboot message. I've unmounted the BaseSystem.vmdk, started machine again and all I get is black screen. Been hanging like that for few minutes right now, with no feedback at all. What could have possibly gone wrong?

 

Cheers,

Furai

 

What's on it? 

 

In the EFI partition, Clover r4332 compiled with GCC and minimal config.plist, compatible for use in VMware and VirtualBox.

 

In macOS HFS partition, startosinstall.command script, which assembles the Installer App on the macOS target volume and starts the startosinstall utility...

#!/bin/bash
 
 # Change to root folder
 cd /
 
 # Copy "small" Installer app to “macOS” target
 cp -R Install\ macOS\ High\ Sierra.app /Volumes/macOS/
 
 # Copy SharedSupport folder from USB "DATA" to Contents folder in Installer.app on “macOS”
 cp -R /Volumes/DATA/SharedSupport /Volumes/macOS/Install\ macOS\ High\ Sierra.app/Contents/
 
 # Start startosinstall utility to create phase 1 /macOS Install Data
 /Volumes/macOS/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/macOS --converttoapfs NO --rebootdelay 30 --applicationpath /Volumes/macOS/Install\ macOS\ High\ Sierra.app
  • Have you tried rebooting the VM again after the "black screen" (power down, then restart)?
  • What disks are attached to your VM?  Did you attach the provided macOS.vmdk which has Clover preinstalled on it or your own?
  • Is the black screen you are describing the UEFI Shell (eg step 4 in post#73)?
  • What is the version of VirtualBox you are using? 

 

As of the time of writing my guide, VirtualBox does not have the code to find "\macOS Install Data\Locked Files\Boot Files\boot.efi", which is the DATA structure used to natively update/install macOS Sierra and High Sierra.  For the second installation phase to continue, you will either need to boot to Clover as described in step10, post#75,

 

or boot to the UEFI shell and manually restart the installation process by typing the following 2 lines, followed by <Enter> after each line...

FS1:
"\macOS Install Data\Locked Files\Boot Files\boot.efi"

step4, post#73.

 

 

 

Nope, not like UEFI shell, just completely black screen.

 

 

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

Your "black screen" was most likely due to a mismatch between the value set for VirtualBox's EfiGraphicsResolution (default = 1024x768) and screen resolution set in Clover's config.plist.

Share this post


Link to post
Share on other sites

What's on it? 

 

In the EFI partition, Clover r4332 compiled with GCC and minimal config.plist, compatible for use in VMware and VirtualBox.

 

In macOS HFS partition, startosinstall.command script, which assembles the Installer App on the macOS target volume and starts the startosinstall utility...

#!/bin/bash
 
 # Change to root folder
 cd /
 
 # Copy "small" Installer app to “macOS” target
 cp -R Install\ macOS\ High\ Sierra.app /Volumes/macOS/
 
 # Copy SharedSupport folder from USB "DATA" to Contents folder in Installer.app on “macOS”
 cp -R /Volumes/DATA/SharedSupport /Volumes/macOS/Install\ macOS\ High\ Sierra.app/Contents/
 
 # Start startosinstall utility to create phase 1 /macOS Install Data
 /Volumes/macOS/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/macOS --converttoapfs NO --applicationpath /Volumes/macOS/Install\ macOS\ High\ Sierra.app

 

Yeah, I've seen it when I've mounted the vmdk to the system using nbd kernel module.

 

  • Have you tried rebooting the VM again after the "black screen" (power down, then restart)?

Yes, multiple times. All the time just pure black screen is visible.

 

 

  • What disks are attached to your VM?  Did you attach the provided macOS.vmdk which has Clover preinstalled on it or your own?

 

There was only provided by you macOS.vmdk attached to it, no optical drives.

 

 

  • Is the black screen you are describing the UEFI Shell (eg step 4 in post#73)?

 

Nope, not like UEFI shell, just completely black screen.

 

 

  • What is the version of VirtualBox you are using? 

 

Latest version available right now so I think 5.2.2.

 

As of the time of writing my guide, VirtualBox does not have the code to find "\macOS Install Data\Locked Files\Boot Files\boot.efi", which is the DATA structure used to natively update/install macOS Sierra and High Sierra.  For the second installation phase to continue, you will either need to boot to Clover as described in step10, post#75,

 

or boot to the UEFI shell and manually restart the installation process by typing the following 2 lines, followed by <Enter> after each line...

FS1:
"\macOS Install Data\Locked Files\Boot Files\boot.efi"
step4, post#73.

 

I'll give it a try with UEFI shell. Thanks for all the help and time taken to write it. :)

 

If anything, I'm sitting now every day on IRC, if by any chance you're using it. We might chat there, find a solution and post it here afterwards.

 

EDIT: I've just tried UEFI shell, it works but for some reason it erases command I type in random fashion. Like I start typing something and then the cursor gets moved to the beginning of the line and I'm inserting text over.

Tried putting in commands until I finally managed changing directory to the one with boot.efi file and run it from there. It worked and now I'm installing macOS. I'm really puzzled why UEFI shell behaves like this.

 

EDIT#2: Installed, configured. Can run it without problems. Usual stuff not work like audio is distorted and what not.

Share this post


Link to post
Share on other sites

I followed the guide to create an installation from scratch without access to a Mac or the App store.

 

I used your macOs.vmdk and created a BaseSystem.vmdk accodring to your guide. However, I get another issue. I think its possible due to the fact that I have a Intel HD graphics 630:

 

WARNING: IOPlatformPluginUtil : getCPUIDinfo: this is an unknown CPU model 0x9e

 

(See attachment for a screenshot)

 

Here is a post discussing it on another website:

https://www.tonymacx86.com/threads/getcpuidinfo-this-is-an-unknown-cpu-model-0x5e.222321/#post-1506955

 

I tried spoofing the CPU model but it does not seem to do any difference in my case.

 

So, I am wondering if its possible to troubleshoot this issue?

 

 

Share this post


Link to post
Share on other sites

 

8)  The Apple Software Licence will appear in the terminal window.  Type A to agree ---> install files will be placed in /Volumes/macOS/macOS Install Data ---> System will reboot after 30 seconds...

 

 

When I try, I'm getting "Error: could not get license agreement." I initially thought this could be because I was behind a proxy, but when I tried with a direct Internet connection, I'm getting the same.

 

Does anyone have any hints as to what the issue might be?

Share this post


Link to post
Share on other sites

Update for Mojave 10.14_18A391
The El Capitan Settings from post#1 still work for macOS Mojave, but with newer VirtualBox 5.2.xx releases, USB3/xHCI should be enabledOS version of guest should also be set to macOS High Sierra 10.13 64 bit (or newer).


Note - Clover is also required since the Mojave installer automatically converts target HD to apfs and VirtualBox does not presently support apfs.  Unfortunately installation may take a long time (hours) on a spinning HD using apfs.
Tested below with ≥ 2GB RAM Base Memory allocated for the guest macOS and EfiGraphicsResolution set to 1024x768 (to match resolution in Clover's config.plist GUI section)...

cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1024x768

To prepare the Mojave ISO on your Mac or Hack:
1.  On your Mac or Hack with SIP disabled, download/copy "Install macOS ******.app" into your Applications folder.
2.  Download and unzip the macOS_iso_creator.tool.zip (attached to this post) into your ~/Downloads folder.  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 macOS_iso_creator.tool
./macOS_iso_creator.tool

4.  At the end of the process, you will have a macOS.iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
5.  Attach macOS.iso and supplied macOS_apfs.vmdk (preformatted blank 50GB apfs volume with Clover r4699 installed in EFI) to the Virtual Machine and proceed to run the installation.

 

Installation
1)  Boot the VM to macOS Utilities screen. 

 

Spoiler

VB_Mojave3.png.545ff626ea2e29277ddd0002b029cc4c.png

 

Select Reinstall macOS, choosing the macOS volume as the target ---> install files will be placed in /Volumes/macOS/macOS Install Data ---> System will reboot.
2)  Power off the VM when you see the message "MACH Reboot".  Then go to the VM Storage settings to detach the macOS.iso (since it is no longer required).
3)  Power on the VM again and you will be greeted with the Clover Main Menu --->  select "Boot macOS Install Prebooter from Preboot" + press <Enter>  ---> will see "Installing on "macOS"" and time remaining, as the pkg files are extracted to their final locations ---> Power off the VM when you see the message "MACH Reboot"...


 

Spoiler

 

VB_Mojave6b.thumb.png.b60056eb6a08cc5ea853774c628ad81f.png

 

VB_Mojave7.thumb.png.1c30f846cba33846272c50c22e079a3a.png

 

VB_Mojave8.thumb.png.e02b5fbc7855d4187fa67682732df374.png

 

VB_Mojave9.thumb.png.651101e11ccdadd8aa132caaa69b53f4.png

 

 

 


4)  Power on the VM a final time to finish installation and setup.  At the Clover Main Menu, select "Boot FileVault Prebooter from Preboot" + press <Enter> ---> rebuild kext caches and setup new user account...


 

Spoiler

 

VB_Mojave10.thumb.png.d99396d4dcaa34c4a6b8e03eb902845d.png

 

VB_Mojave11.thumb.png.2dba687682b6ea217877fc7336e5e4c9.png

 

VB_Mojave12.thumb.png.c7d9cd29de2f8ba62c3383a05105d311.png

 

VB_Mojave13.thumb.png.207d6da8d38131abbdf3b95062784fea.png

 

 

 

 

 

 

macOS_iso_creator.tool.zip

macOS_apfs.vmdk.zip

Edited by fusion71au
macOS_iso_creator works to create both Mojave and High Sierra ISOs from Install Apps

Share this post


Link to post
Share on other sites

For me tutorial for mojave don't work, i try many times, but clover bootloader never start anyway

 

sx.jpg

Edited by Lian1975

Share this post


Link to post
Share on other sites
2 hours ago, Lian1975 said:

For me tutorial for mojave don't work, i try many times, but clover bootloader never start anywaysx.thumb.jpg.41e1d1f03c5263d6f2083787d3548e0c.jpg

 

I fixed this issue creating a new VM with choose OS version High Sierra

 

Now clover bootloader start perfectly.

 

Thanks for tutorial !

 

1111096345_OSVersion.jpg.ec3335662ef8c45f1d2515598ae60d28.jpg

 

Share this post


Link to post
Share on other sites

I have another issue

 

When I change the screen resolution for custom size with this code: 

VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024

Screen gets bug ( See the Picture )

 

What is the right way to change the screen resolution of VM ?

 

screen.thumb.jpg.461a5205bf8ee99c489a5f956bf94aa8.jpg

 

Edited by Lian1975

Share this post


Link to post
Share on other sites
2 hours ago, Lian1975 said:

What is the right way to change the screen resolution of VM ?

 

As I said a few posts above, this is due to a mismatch between the value set for VirtualBox's EfiGraphicsResolution and the screen resolution set in Clover's config.plist.

 

Mount the EFI System Partition (sudo diskutil mount disk0s1), and edit the GUI section of Clover's config.plist to match the custom resolution you set with VBoxManage...

		<key>ScreenResolution</key>
		<string>1280x1024</string>

 

 

Share this post


Link to post
Share on other sites
11 hours ago, Lian1975 said:

fusion71au You have a tutorial how you create a preformatted blank vmdk or vdi partition with clover bootloader pre installed ?

 

 

  1. Start VirtualBox
  2. Select existing VM with installed macOS eg High Sierra
  3. Under Settings, Storage, SATA Controller, click Add Hard Drive icon
  4. Create new disk, type VMDK, Dynamically allocated, name eg "macOS.apfs.vmdk", size=50GB
  5. Boot VM to High Sierra.  Initialize new disk with Disk Utility, Erase Disk, format as apfs named drive eg "macOS"
  6. Download EFI_Clover for VMware while running inside your High Sierra VM.  Mount iso and copy EFI folder to EFI System Partition of new macOS disk
  7. Shutdown VM.  Copy macOS.apfs.vmdk eg found in C:\Users\UserName\VirtualBox VMs\macOS High Sierra to external USB or where ever.
Edited by fusion71au

Share this post


Link to post
Share on other sites
11 hours ago, fusion71au said:
  1. Start VirtualBox
  2. Select existing VM with installed macOS eg High Sierra
  3. Under Settings, Storage, SATA Controller, click Add Hard Drive icon
  4. Create new disk, type VMDK, Dynamically allocated, name eg "macOS.apfs.vmdk", size=50GB
  5. Boot VM to High Sierra.  Initialize new disk with Disk Utility, Erase Disk, format as apfs named drive eg "macOS"
  6. Download EFI_Clover for VMware while running inside your High Sierra VM.  Mount iso and copy EFI folder to EFI System Partition of new macOS disk
  7. Shutdown VM.  Copy macOS.apfs.vmdk eg found in C:\Users\UserName\VirtualBox VMs\macOS High Sierra to external USB or where ever.

Thank you fusion71au

Share this post


Link to post
Share on other sites

Thanks for the post fusion71au !

 

a few things that might took me a little longer than it should have:

 

1: you need to be logged to download CMJI.tool.zip & macOS_apfs.vmdk.zip

2: the posts on page #1 and #4 have everything you need, and the VBoxManager setextradata commands are mandatory

3: same thing for using the usb3 (see post "Update for Mojave Beta" from page 4) or you'll end up with a frozen VM during language selection

Share this post


Link to post
Share on other sites

Hi,

thanks for the great tutorial. I'm having a problem trying to install High Sierra to a VM in VirtualBox.

The startosinstall.command script seems to work fine, but after the reboot, I get this screen saying the installer ressources were not found. The macOS.vmdk at this point is 5.18GB, so the files seem to have been copied. Is there any way to figure out exactly what file I am missing to begin the install process? When I open the macOS.vmdk in 7zip, I see 2 files: 1.hfsx and EFI System Partition.img

 

System: WIN 10 Host, VirtualBox 5.2.18

 

Thanks!

 

image.thumb.png.083917873b4b7e3b08748910fdee7d8a.png

Edited by SimonLL
Added system infos

Share this post


Link to post
Share on other sites
2 hours ago, SimonLL said:

Hi,

thanks for the great tutorial. I'm having a problem trying to install High Sierra to a VM in VirtualBox.

The startosinstall.command script seems to work fine, but after the reboot, I get this screen saying the installer ressources were not found. The macOS.vmdk at this point is 5.18GB, so the files seem to have been copied. Is there any way to figure out exactly what file I am missing to begin the install process? When I open the macOS.vmdk in 7zip, I see 2 files: 1.hfsx and EFI System Partition.img

 

System: WIN 10 Host, VirtualBox 5.2.18

 

Thanks!

 

Troubleshooting

1) Check SHA1 hashes of your downloaded files with eg HashMyFiles utility.  Compare with verified hashes from this website and the screenshot below for files from 10.13.6_ 17G65 ...

 

731786744_HighSierraFilesSHA1sums.png.29292c9e458b06fe5acd38be6391eea3.png

 

2) Maybe due to incorrectly edited InstallInfo.plist in \SharedSupport folder.  Replace with InstallInfo.plist.zip from 10.13.6 attached to this post.

 

InstallInfo.plist.zip

 

Update for How to install High Sierra or Mojave on a VirtualBox Guest from scratch (without access to Mac or App Store Installer.app)

 

I've simplified steps 1-8 with BaseSystem_vmdk_generator and added apfs support with Clover r4699 in macOS_apfs.vmdk.

 

1)  Download & extract the contents of BaseSystem_vmdk_generator.zip to your USB.  For my system, the drive letter was D:

 

MJVM5.png.487aa108a3e2f7a31bc63ee75ab94f71.png

 

2)  Convert \SharedSupport\BaseSystem.dmg to vmdk by double clicking BaseSystem_vmdk_generator.bat.  The file BaseSystem.vmdk is automatically created in the root directory \ of the USB.

 

Deleting any existing image files and vmdk files...
Could Not Find D:\*.vmdk
Could Not Find D:\qemu-img-win-x64-2_3_0\*.img
Converting BaseSystem.dmg to BaseSystem.img with dmg2img...

dmg2img v1.6.7 (c) vu1tur (to@vu1tur.eu.org)

\SharedSupport\BaseSystem.dmg --> \qemu-img-win-x64-2_3_0\BaseSystem.img


decompressing:
opening partition 0 ...             100.00%  ok
opening partition 1 ...             100.00%  ok
opening partition 2 ...             100.00%  ok
opening partition 3 ...             100.00%  ok
opening partition 4 ...             100.00%  ok
opening partition 5 ...             100.00%  ok
opening partition 6 ...             100.00%  ok
opening partition 7 ...             100.00%  ok

Archive successfully decompressed as \qemu-img-win-x64-2_3_0\BaseSystem.img
Converting BaseSystem.img to BaseSystem.vmdk...
BaseSystem.vmdk created in root directory of USB drive!
Press any key to continue . . .

3)  Copy BaseSystem.vmdk from your USB into the VirtualBox macOS guest folder

4)  Attach BaseSystem.vmdk and macOS_apfs.vmdk to your macOS guest as extra hard drives

5)  Boot your VM to the macOS Utilities screen.  Attach the usb (named "USB" and containing the \SharedSupport folder) to the VM and open Disk Utility, show all devices ---> will see blank 50GB drive for installation, 2GB "OS X Base System" and the USB volume "USB"

6)  Erase blank drive, format it to apfs named "macOS" 

7)  Close DU and start Terminal...

 

-bash-3.2# cd /Volumes/USB
-bash-3.2# ./startosinstall.command

The startosinstall.command script builds the full "Install macOS ******.app" and chain loads the startosinstall utility on the "macOS" target volume.  It combines both the "small" installer app (approx 15MB in size on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted on /Volumes/USB).  Note the full installer app is >5GB in size

 

8)  After a few minutes, Apple's Software License agreement will appear ---> type "A" to agree to the License Agreement etc

 

 

InstallInfo.plist.zip

BaseSystem_vmdk_generator.zip

macOS_apfs.vmdk.zip

Share this post


Link to post
Share on other sites

Thanks for doing that!

 

Hashes were good except Info.plist. It is good with yours now. I did retry only with the new Info.plist, but same result: Installer falied with com.apple.osinstall error -3. Then Installer files were not found.

 

With this new Clover version and macOS_apfs.vmdk, the VM boots to Clover, but when I press enter to boot macOS, it goes directly to the VBox Boot manager. I select continue, then the window resizes smaller and I get a blank screen.

 

I looked the config.plist in your new macOS_apfs.vmdk and the resolution is set to 1024x768, so I used this command in VBox Program folder:

VBoxManage setextradata "High_Sierra" VBoxInternal2/EfiGraphicsResolution 1024x768

Which completed. But still same result after multiple restarts, blank screen. I can'T seem to get to MacOS Utilities. I'm not sure where to look anymore.

Edited by SimonLL

Share this post


Link to post
Share on other sites

Finally got it to work using my previous BaseSystem.vmdk and your new macOS.vmdk and Info.Plist!!!

 

Thanks you very much!!

 

Now I have one tiny problem, but this might not be the appropriate place to solve it.

I have the common USB 3.0 problem: USB 3.0 devices in a 3.0 port are not even seen by OSX. USB 2.0 devices work no problem. VBox is set to USB3.0

 

Not sure how to fix this one in a virtual hack.

Share this post


Link to post
Share on other sites

OK, got Mojave running fine using VirtualBox 5.2.18 currently. But still, I have some unresolved issues:

1. Force using VoodooHDA (with disabled AppleHDA for sure) Audio in-out is working, but VirtualBox quit unexpectedly while changing Volume level or when getting Notif sound. Oh yeah, I'm using 10.11.6 as Host mach. I hope not posting on a wrong thread.

2. Already manually added CLOVERX64.efi as 1st boot entry using VBox firmware, as well as UEFI Shell `bcfg boot add XX FSX:\Path_to_*.efi EntryName. But it always reset to default (means, new entry was gone) after Powering VM off.

3. How to get NVRAM working on macOS Guest? (Aptio*.efi driver is useless under VM, right?)

4. Is it possible to install Ozmosis Bootloader on macOS Guest?

Thanks in advances.

VM-SS.png

Share this post


Link to post
Share on other sites

First time posting here, but I have encountered a couple problems.

 

I got Mojave installed fine, thanks to the instructions, and it works, but I am having a problem that is quite similar to this post.

 

On 8/5/2018 at 1:02 PM, Lian1975 said:

I have another issue

 

When I change the screen resolution for custom size with this code: 


VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024

Screen gets bug ( See the Picture )

 

What is the right way to change the screen resolution of VM ?

 

screen.thumb.jpg.461a5205bf8ee99c489a5f956bf94aa8.jpg

 

 

When I modified the screen resolution through the mentioned command, things look ok, unlike Lian's situation, but the resolution was not right, so I set the resolution, which was 1920x1080 in the Clover config file, and it starts to boot up normally.

 

However, regardless of the option I pick in Clover, I see something at the top that looks similar to the screenshot that Lian posted, except I see the regular clean booting messages below it.

 

The other thing that I encountered is that I cannot gracefully reboot the VM, either through the GUI or terminal emulator. It gets stuck at Mach Reboot and will not go anywhere, which means updates are next to impossible.

 

Any ideas of how to fix these?

 

I my host OS is Windows 10 Pro 64-bit and my version of virtualbox is 5.2.18.

Share this post


Link to post
Share on other sites
On 10/18/2018 at 10:43 PM, Badruzeus said:

OK, got Mojave running fine using VirtualBox 5.2.18 currently. But still, I have some unresolved issues:

1. Force using VoodooHDA (with disabled AppleHDA for sure) Audio in-out is working, but VirtualBox quit unexpectedly while changing Volume level or when getting Notif sound. Oh yeah, I'm using 10.11.6 as Host mach. I hope not posting on a wrong thread.

2. Already manually added CLOVERX64.efi as 1st boot entry using VBox firmware, as well as UEFI Shell `bcfg boot add XX FSX:\Path_to_*.efi EntryName. But it always reset to default (means, new entry was gone) after Powering VM off.

3. How to get NVRAM working on macOS Guest? (Aptio*.efi driver is useless under VM, right?)

4. Is it possible to install Ozmosis Bootloader on macOS Guest?

Thanks in advances.

 

For questions 1-3, these are unfortunately unresolved issues/bugs with VirtualBox itself.  Native audio in Mojave doesn't work at present (never tried with VoodooHDA inside VM), VirtualBox BIOS does not remember previously "saved" settings and NVRAM is also non functional (these maybe related).  Ofc, AptioMemoryFix driver would be useless since the BIOS is not Aptio ...

 

If you want a "smoother" experience with native sound and working NVRAM, better to try running Mojave in VMware patched with @Donk's unlocker program.  Installing VMware tools also improves graphics performance and allows dynamic resizing of the VM window (unlike VirtualBox which doesn't provide macOS guest tools at all).

 

Sorry, don't know about Ozmosis inside VM.

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Teress
      In this Hackintosh tutorial I'm covering all aspects of Dual Boot Windows and macOS. How to avoid problems, best settings, Pros and Cons.
       
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip






    • By tbianco
      Ho comprato da poco un Acer Aspire 5750G e girando su internet ho trovato la cartella efi che garantiva quasi tutto funzionante perfino il wifi (https://github.com/zipippino/HighSierraAspire5750G).
      Allora felicissimo installo macOS e a parte incappare in errori stupidi, riesco a fare tutto, ma quando sono riuscito ad installare clover Legacy e sostituendo la roba con la 'mia' efi clover si avvia ma macOS no, semplicemente non carica (si nota anche pk la spia dell'hdd che dice se è in attivitá è spenta.
      Qualcuno può aiutarmi?
    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not get iMessage to work properly. It worked precisely once, on my first installation attempt. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - if you can get NVRAM/PRAM working properly on this hardware, please do edit the config as you see fit.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
    • By JLMOX
      I think, at this point converting to hfs+ is out of the question, Apple has been pushing the apfs file policy very aggressively, so does anybody solved the missing "Boot macOS from Mojave " (this last word may be different). I have installed the latest clover in HDD and USB, but I can only see 3 Mac Os related tabs but not the one for actually loading the Mojabe mac OS. I updated high sierra to Mojave and everything went fine. My laptop (Dell E6530) booted up normally, Mojave system loaded up, I finished the setup and spent sometime exploring. I updated clover to the latest version and turned of machine. When I restarted, I noticed Clover did not have an option for booting into the system like High sierra had it. I tried adding the apfs.efi or the ApfsDriverLoader-64.efi driver to the clover efi folder in the HDD and also tried with a USB clover installation and the result is the same: No boot option for the Mojave OS. I used the recovery option and I was able to explore the partion where the system is located but that´s as far as I could go. Does anybody has an idea of what happened?

×