Running macOS Mojave 10.14 on VirtualBox 5.2.18 on Linux x86_64

This will of course work for any newer version of VirtualBox (Currently 6.0.2)

Short entry here, since it was covered in the early article (which you can find here -> https://astr0baby.wordpress.com/2018/08/03/installing-mojave-10-14-beta-in-virtualbox-5-2-16-on-linux-x86_64/ ) how to setup the Mojave-Beta in VirtualBox and Apple released the stable Mojave yesterday.  Maybe somebody will find it useful.

We will download the Mojave dmg via AppleStore from the Mojave-Beta VBox guest that we installed earlier  ( you can download the ready made ISO from here https://gofile.io/?c=0NPNYX

Without actually installing it, after download is finished we run the following sets of commands to create the Mojave.iso

hdiutil create -o /tmp/Mojave.cdr -size 6000m -layout SPUD -fs HFS+J
hdiutil attach /tmp/Mojave.cdr.dmg -noverify -mountpoint /Volumes/install_build
sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/install_build
mv /tmp/Mojave.cdr.dmg ~/Desktop/
hdiutil detach /Volumes/Install\ macOS\ Mojave/
hdiutil convert ~/Desktop/Mojave.cdr.dmg -format UDTO -o ~/Desktop/Mojave.iso

Next we upload the Mojave.iso to our Linux host and continue with the standard macOS VirtualBox setup  (In the first stage attach Mojave.iso – clover.iso will be in the second one)

You can download the macOS Mojave from here https://gofile.io/?c=0NPNYX

Before we run the VM make sure you execute the following script to setup VirtualBox for macOS – replace the NAME variable with the name of the VirtualBox guest name. Make sure you have no VirtualBox windows open (close all just in case) and run the following script

#!/bin/bash
readonly VM_RES="1680x1050"
readonly NAME="Mojave"

VBoxManage modifyvm "$NAME" --usbxhci on --firmware efi --chipset ich9 --mouse usbtablet --keyboard usb
VBoxManage setextradata "$NAME" "CustomVideoMode1" "${VM_RES}x32"
VBoxManage setextradata "$NAME" VBoxInternal2/EfiGraphicsResolution "$VM_RES"
VBoxManage modifyvm "$NAME" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
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" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "$NAME" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

Also the following networking script is used (adjust accordingly) for the following network config in VirtualBox

If you don’t care about virtual VLANs you can just use the default NAT and choose DHCP in macOS install (Make sure you change your internet connected network interface accordingly – mine is wlp9s0, yours will be different)   For the tunctl and brctl commands to be present you need to install the following package (Debian, Ubuntu)

# apt-get install uml-utilities
# apt-get install bridge-utils
#Setup tap and bridge 
tunctl -t tap0 -u user
ifconfig tap0 up
brctl addbr br0
brctl addif br0 vboxnet0 
brctl setfd br0 0
ifconfig enp0s25 10.0.2.1 up 
ifconfig br0 10.0.2.2 netmask 255.255.255.0 broadcast 10.0.2.255 up
brctl addif br0 tap0 vboxnet0 
ifconfig tap0 0.0.0.0
sysctl net.ipv4.ip_forward=1
iptables --table nat -A POSTROUTING --out-interface wlp9s0 -j MASQUERADE

P.S Please note that the above script needs to be launched every time you get the vboxnet0 interface loaded (This means just fire up VirtualBox main window and then run the script to get the network working) 

Next we go on with the normal Mojave.iso boot

Once we get to the first setup screen “erase” disk with APFS and start the installation – don’t worry that VirtualBox does not understand APFS partitions in UEFI, we have the custom Clover.iso loader for that during 2nd stage install.

Once the 1st stage installer finishes, it will reboot and you will endup yet again in the same setup window, since we did not switch the ISO, so just terminate the macOS guest and swap the Mojave.iso with Clover.iso

you can download Clover.iso with APFS support here https://mega.nz/#!ewsiWYDL!r4qILNC08O8lGjBC9GgvMHAR096CIVy2RMP6MwZ3-KA

P.S for the latest Clover.iso customization please refer to https://astr0baby.wordpress.com/2019/01/19/customizing-the-clover-iso-mojave-loader/

Boot again the guest VM and in Clover menu choose the Boot macOS Install from Mojave (Name of the disk I have chosen during 1st stage setup)  (move the arrow keys to navigate Clover menu)

Next we continue with the standard setup

After it finishes, it will reboot but will get stuck in the following screen, so just hard reset here no problem

Boot again with the Clover.iso still attached (we will use Clover to load macOS) and choose Boot macOS from Mojave (use the arrow keys to navigate Clover menu)

Next we configure network (adjust accordingly)

And welcome to your new macOS 10.14 Mojave !

A small security note here. If you need to enable SIP in your virtuallized Mojave, you need to modify the following configuration file in the Clover.iso

efi/clover/config.plist

There is an option that sets CsrActiveConfig as below

CsrActiveConfig
0x67

You will need to change it to match what you want -> 0x0

csr-active-config 0x0 = SIP Enabled (Default)
csr-active-config 0x3 = SIP Partially Disabled (Loads unsigned kexts)
csr-active-config 0x67 = SIP Disabled completely

Also if you wish to modify the clover.iso please check the following -> https://astr0baby.wordpress.com/2019/01/19/customizing-the-clover-iso-mojave-loader/

Advertisements

About astr0baby

Please run Adblock or similar... we have been told to do so since Carl Sagan wrote the Contact .
Gallery | This entry was posted in Uncategorized. Bookmark the permalink.

183 Responses to Running macOS Mojave 10.14 on VirtualBox 5.2.18 on Linux x86_64

  1. Hi,
    Thanks! How is the performance?

    • astr0baby says:

      Quite fast, ( running on SSD seems almost native)

      • Boyan says:

        First of all, thank you very much for the guide! I was able to succesfully boot MacOS Mojave thanks to it.

        Could you please define quite fast? Loading times seem okay for me, however animations are extremely choppy and slow. I’m wondering whether it’s something on my side? I’ve changed the CPU cores to 4 and the VRAM to the max 128MB (although I have 4GB VRAM in total on my nVidia GPU they are not available in the settings)

      • astr0baby says:

        For me fast means general Safari usage, work in terminal, mounting remote shares etc .. I only test security related things, no graphical
        performance in the VM, thus quite fast.

  2. Hangs on the first installation screen (choose language). No mouse, no keyboard …. Any idea?

  3. r says:

    where to download clover.iso

  4. Gavin Dundee says:

    For some reason the clover.iso will not boot.. I am running Ubuntu 18.04 with the latest version of Virtualbox installed. Does anyone have any idea why this will not boot?

  5. Alex says:

    Booting from clover into Mac OS install after the first stage just gives a bunch of weird video artifacts and stops there. Intel CPU.

    • astr0baby says:

      Did you configure the Guest VM properly prior running ? It is essential to run the following before booting the Clover/macOS

      change the NAME variable according to your naming convention and keep the VM_RES=”1680×1050″ otherwise you will get artefacts.

      #!/bin/bash
      readonly VM_RES=”1680×1050″
      readonly NAME=”Mojave”

      VBoxManage modifyvm “$NAME” –usbxhci on –firmware efi –chipset ich9 –mouse usbtablet –keyboard usb
      VBoxManage setextradata “$NAME” “CustomVideoMode1” “${VM_RES}x32”
      VBoxManage setextradata “$NAME” VBoxInternal2/EfiGraphicsResolution “$VM_RES”
      VBoxManage modifyvm “$NAME” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
      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” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
      VBoxManage setextradata “$NAME” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

    • manner says:

      Resolution seems to be set by the clover boot manager, macOS seems to not change it afterwards, so you need to ensure to at least have the same width set to virtual machine and clover config. You can change the resolution clover sets in its config.plist file (search for key ScreenResolution) and you need to set the same with the VBoxManage commands for the vm.

  6. manner says:

    Can I disable clover to not show its ui but boot automatically? Seems that changing the “Timeout” key in config.plist has no effect, the ui pops up with unlimited timeout anyway.

  7. Did you have trouble running some of the applications? For example, I had High Sierra and I wasn’t able to generate slideshow from the Photos app. Just want to see if you are having the same issue. Thanks!

  8. Sebastian says:

    Hi,

    I tried to install Mac OS Mojave on my VMWare server created by virtual box and managed by phpvirtualbox. If I try to boot the setup the screen went in to hieroglyphics (see picture link).

    Do you or someone have the same problem and know a solutio?

    thx

    Sebastian

    • astr0baby says:

      You must use the exact screen resolution in the VB guest like this
      #!/bin/bash
      readonly VM_RES=”1680×1050″
      readonly NAME=”Mojave”

      VBoxManage modifyvm “$NAME” –usbxhci on –firmware efi –chipset ich9 –mouse usbtablet –keyboard usb
      VBoxManage setextradata “$NAME” “CustomVideoMode1” “${VM_RES}x32”
      VBoxManage setextradata “$NAME” VBoxInternal2/EfiGraphicsResolution “$VM_RES”
      VBoxManage modifyvm “$NAME” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
      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” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
      VBoxManage setextradata “$NAME” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC”

      The 1680×1050 is hardcoded on the clover.iso in the configuration. If you want to change it you must modify the clover.iso clover/config.plist

  9. Varun Agraw says:

    Hey!! The link to clover.iso is broken. Please give me the new link!! :/.

    Thanks

  10. Manuel says:

    What is owl in finder network?

    • astr0baby says:

      Sorry I don’t fully understand …

      • Manuel says:

        When I open a Finder and select Network, It show a machine named owl “búho in spanish”. This system isn’t in my network.
        Tks

      • astr0baby says:

        I have no idea how your “network” is configured. If there is something on it that you don’t recognize then you have a problem. Why do you ask here about it ? Again let me repeat here one more time – the macOS images are vanillas from Apple Store..

  11. Adam F says:

    How to set screen resolution on with Linux host:

    Use VBoxManage setextradata $MOJAVEVM VBoxInternal2/EfiGraphicsResolution 1920×1080

    You also have to set the resolution in EFI/CLOVER/config.plist (in the Clover .iso). Unfortunately, this is hard to do in Linux because ISO9660 partitions are meant to be read only and most editing methods end up destroying important EFI data. (I have no idea how to build Clover from scratch.) I came up with another solution: building an editable Clover disk image that you can attach to the VM instead of Clover.iso.

    This is pretty easy to replicate once you know how:
    # Make an empty file big enough to hold an EFI partition*:
    dd if=/dev/zero of=clover.raw count=1 bs=100M
    # Create an EFI type partition
    echo “,,ef,” | sfdisk clover.raw
    # Mount the raw file as a device (you need qemu for this)
    sudo modprobe nbd
    sudo qemu-nbd -c /dev/nbd1 -f raw clover.raw
    # Format the partition as FAT32
    sudo mkfs.fat -F32 /dev/nbd1p1
    # Mount the newly created partition
    mkdir efi
    sudo mount /dev/nbd1p1 efi

    So you’ve now got a pristine empty EFI environment. Now just copy all the files from Clover.iso into it, and edit the config.plist as described previously. Then build the disk image:

    sudo umount efi
    sudo qemu-img convert clover.raw -O vmdk clover.vmdk

    And just boot the Mojave vm off of clover.vmdk and you’re home free!

    Here’s my 1080p clover.vmdk in case anyone else wants it: https://ipfs.eternum.io/ipfs/QmWzYjrtNpZenRu3dk6NDuLrJV8LY9WsFq8AWqKfhyBspm

    * Supposedly EFI partitions can’t be smaller than 100MB, and the Arch wiki recommends 512MB, but I successfully created one in a 35MB file. Since they get compressed in the vmdk it shouldn’t make much difference.

    • astr0baby says:

      Good alternative solution, I will definitely try this. Thanks for sharing.

    • Nico says:

      Thank you for this solution, but I don’t know how to use the clover.vmdk, can you explain this? Thanks

    • I tried to follow your steps but get an error when running second command (echo “,,ef,” | sfdisk clover.raw):
      Checking that no-one is using this disk right now … OK

      Disk clover.raw: 100 MiB, 104857600 bytes, 204800 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes

      >>> line 1: unsupported command

      New situation:
      Leaving.
      Any idea why? (I’m on void linux btw)
      As well, your link is not working, download fails
      cheers :)

    • Can you please share your clover iso with 1920×1080 on a different location?
      I tried to follow your steps but it is not working on my machine…
      Cheers :)

      • Terry says:

        Going on vacation for few eeeks, so my priject gas to stop. Please do not wait any more of your valuable time until i get back to you.
        Thx

      • I’m trying to find information on how to create a clover iso but seems to be going around in circles. All I want to do is modify the config.plist to boot in 1920×1080, create the iso and done. is it really that difficult to achieve or am I really dumb? I have Linux and Mac.
        Adam gave some steps on Linux, which failed for me, and his link to the modified clover iso is broken (never finishes the download)

      • astr0baby says:

        Please follow these instructions on MacOS, thats how I originally built the Clover.iso here -> https://astr0baby.wordpress.com/2018/08/03/installing-mojave-10-14-beta-in-virtualbox-5-2-16-on-linux-x86_64/

      • Thank you Astr0baby.
        Yes, I’m working on a Mac, but still no luck here and not sure why.
        This is what I do:
        Take your iso and copy content to a folder
        Edit the config.plist to set resolution to 1920×1080
        I create a disk image from that folder using Disk Utility and setting options to “DVD?CD master”
        I get a .cdr image
        Change .cdr to .iso
        Run your script to get a clover iso
        I set the following commands in my Linux terminal: VBoxManage setextradata global GUI/MaxGuestResolution any
        as well as:
        VBoxManage setextradata “Mojave” “CustomVideoMode1” “1920x1080x32”
        I start the VM with the created iso and get to the clover menu (which looks different to your original clover menu)
        When I choose to boot from Mojave i get scrambled screen and get stuck.

      • astr0baby says:

        Do not edit my iso, rather build it from scratch, but before running the following code

        hdiutil detach /Volumes/Clover-v2.4k-4533-X64/
        hdiutil detach /Volumes/NO\ NAME/
        hdiutil makehybrid -iso -joliet -o ./clover.iso ./clover.dmg

        Edit the needed configuration files to suite your needs, then run it to generate the clover.iso on the macOS

      • astr0baby says:

        Also Clover source code probably changed over time … I will see if I can make a custom one with the desired resolution you are mentioning.

      • Cheers astrobaby, I will give it a go.
        If you have time to create one, it will be much appreciated!
        btw, the sound track to your video reminds me of Goa :)
        Happy New Year!

      • astr0baby says:

        As soon as I finish with some other project Im working on right now (aarch64 NetBSD) I will build a new Clover iso and test it. All the best in 2k19 too and thx for commenting :) I appreciate it highly !

    • Hey Astr0baby!
      Hope you had a nice New Year! looks like you have been busy :)
      Any luck with 1920×1080 clover? whatever I try to do is not working (my head is hurting)
      cheers mate

  12. I get empty screen after installing macOS during booting from clover.iso
    Version 5.2.20 r125813 (Qt5.6.2)
    Any ideas how to fix?

    • astr0baby says:

      You must use the exact screen resolution in the VB guest like this
      #!/bin/bash
      readonly VM_RES=”1680×1050″
      readonly NAME=”Mojave”

      VBoxManage modifyvm “$NAME” –usbxhci on –firmware efi –chipset ich9 –mouse usbtablet –keyboard usb
      VBoxManage setextradata “$NAME” “CustomVideoMode1” “${VM_RES}x32”
      VBoxManage setextradata “$NAME” VBoxInternal2/EfiGraphicsResolution “$VM_RES”
      VBoxManage modifyvm “$NAME” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
      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” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
      VBoxManage setextradata “$NAME” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC”

      The 1680×1050 is hardcoded on the clover.iso in the configuration. If you want to change it you must modify the clover.iso clover/config.plist

  13. unicorn says:

    Hi when I first boot downloaded Mojave iso in VB I get stuck at “End RandomSeed” just like this guy: https://www.reddit.com/r/virtualbox/comments/9l0utg/stuck_on_end_randomseed_virtualbox_macos_mojave/
    Can you help? I am on Manjaro Linux.

  14. unicorn says:

    Here is config

  15. user1 says:

    I’m getting a “command not found” error when running the below command:

    “`
    attach /tmp/Mojave.cdr.dmg -noverify -mountpoint /Volumes/install_build
    -bash: attach: command not found
    “`

  16. user1 says:

    This command:

    hdiutil convert ~/Desktop/Mojave.cdr.dmg -format UDTO -o ~/Desktop/Mojave.iso

    It created a “Mojave.iso.cdr file on my desktop. Is this normal? Should I change the file extension to .iso or will VirtualBox be able to import it no matter the file extension?

  17. SIP says:

    After successfully installing Mojave in Virtualbox, it seems SIP isn’t enabled? You can verify this by using `sudo csrutil status` in a Terminal. Is this a side effect of using macOS in VM? I tried enabling it in recovery mode but it doesn’t work. Thoughts?.

  18. SIP says:

    Thanks, “csr-active-config 0x0 = SIP Enabled (Default)” seemed to work. How did you figure out that was the reason?

    • astr0baby says:

      I have just searched the Clover.iso master config file that would possibly be the problematic part. BTW I have updated the blogpost on Mojave to make sure people who need this can set it up accordingly. Thanks again for noticing this ;)

  19. Jess says:

    Heads up to anyone with mouse probs:

    These two links should help:

    https://superuser.com/questions/956622/no-usb-devices-available-in-virtualbox

    https://www.wikigain.com/fix-mouse-keyboard-stuck-macos-mojave-virtualbox/

    There were Linux group/perms issues involved, and while I’d downloaded the extension pack, I hadn’t added any devices.

  20. Rick says:

    The machine boots fine but I cannot see any of my USB drives connected. Even if I add them to the USB filters and VBox see them. The drive does not appear in Mojave. I also have no sound output. Any idea on what to do?

  21. thank you. It works works very well. What i have to do, to update 10.14 |–> 10.14.1

    • astr0baby says:

      Just run the macos updater and once the system reboots (you might have to force shutdown it in the console because it can get stuck) you need to load the macos-installer partition in clover, then wait till it finishes, reboot and load macos via clover normally. It works.

  22. Dr. Fred Albrecht says:

    thank you. It works perfekt.

  23. Benjamin says:

    Thanks a lot astr0baby! Very nice tutorial with all the bells and whistles

  24. Nico says:

    Hi, I get a black screen when I boot after swapping the Mojave.iso with Clover.iso

    • astr0baby says:

      Did you set the screen parameters correctly for your Mojave VM ?
      #!/bin/bash
      readonly VM_RES=”1680×1050″
      readonly NAME=”Mojave”

      VBoxManage modifyvm “$NAME” –usbxhci on –firmware efi –chipset ich9 –mouse usbtablet –keyboard usb
      VBoxManage setextradata “$NAME” “CustomVideoMode1” “${VM_RES}x32”
      VBoxManage setextradata “$NAME” VBoxInternal2/EfiGraphicsResolution “$VM_RES”
      VBoxManage modifyvm “$NAME” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
      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” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
      VBoxManage setextradata “$NAME” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

  25. Nilo Coelho Junior says:

    Thanks! It’s work for me

  26. Pingback: Valuable News – 2018/12/08 | 𝚟𝚎𝚛𝚖𝚊𝚍𝚎𝚗

  27. Eby says:

    Just in case anyone has similar issues, I’ll put these together as they are scattered around comments. I’m on a Lenovo laptop.

    – I was installing from USB and you need the VirtualBox extension pack for USB devices to be available
    – If you have a black screen on clover boot make sure OSX High Sierra is your box setting. I had OSX 64 bit generic which some other screenshots/tutorials showed.
    – If no keyboard/mouse interaction with the installer recreate the VM and rerun the script. I’m not sure if turning on the VM before the script causes something or if creating it before the extension pack was an issue but doing a fresh box with the script before running it fixed the issue.

  28. Terry Lake says:

    Locks up with last line displayed: load /sbin/launchd
    Also shows an icon under ‘activities’ tab which is a circle with a line thru it.

    Any ideas?
    thx

  29. ccc.nrc says:

    I followed the steps but when i hard restart the CLOVER shows me no Boot macOS install from Mojave but only the other 3 options. Do you have a clue?

    Thanks a lot in advance

    • astr0baby says:

      What 3 other options do you see ? Can you post a screenshot ?

      • ccc.nrc says:

        It doesn’t allow me to post photos, anyway they are:
        – “Boot macOS preboot from preboot”
        – “Boot macOS installer from Mojave”
        – “Boot macOS recovery from recovery”
        alongside the “optical” one.
        I think I see the same options as you but without the “Boot macOS from Mojave”

        Moreover when I install Mojave passing through Clover it get stuck at “about 15 minutes remainig”.

        Thank a lot again

      • astr0baby says:

        There are 2 installer stages, first one is fast takes a bout 10 minutes , second is much longer about 30 minutes. I think you have not passed through the second stage, so load the “BBoot macOS installer from Mojave” and wait for it to finish.

    • micke says:

      > Moreover when I install Mojave passing through Clover it get stuck at “about 15 minutes remainig”.

      I also get stuck at 15 min remaining :/ On ubuntu 1804

  30. I running the VBoxManage commands and the installation not working. Freeze before load the installation menu. Here is the picture: http://p.coldline.hu/2019/01/17/3037028-20190117-eBXQCn.png

  31. micke says:

    Thank you so much for this tutorial, I think you’re right. Even though my computer is good, zenbook deluxe with SSD, the loading bar is now half way after about 2 hours – But it is still moving! :D

  32. eliaho says:

    thank you for this tutorial, I managed to virtual mojave thanks to you, but i cannot connect to the internet from the guest vm
    in the configuration when i set : brctl addif br0 enp0s25 vboxnet0
    i get – interface enp0s25 does not exist!

    when i run ifconfig -a
    I see i have enp3s0 instead
    running on ubuntu 16.04
    any idea what can i do to solve it?

    Thanks

    • astr0baby says:

      Just remove the enp0s25 from the command this is my local ethernet card, you probably don’t have this. So you can use the simplified network script below – make sure you change wlp9s0 (this is my wireless interface) to one you are using (wlan0…)

      #Setup tap and bridge
      tunctl -t tap0 -u user
      ifconfig tap0 up
      brctl addbr br0
      brctl addif br0 vboxnet0
      brctl setfd br0 0
      ifconfig br0 10.0.2.2 netmask 255.255.255.0 broadcast 10.0.2.255 up
      brctl addif br0 tap0 vboxnet0
      ifconfig tap0 0.0.0.0
      sysctl net.ipv4.ip_forward=1
      iptables –table nat -A POSTROUTING –out-interface wlp9s0 -j MASQUERADE

  33. Can you provide a torrent for the iso file?

  34. octapod says:

    @astr0baby, the script which calls ‘hdiutil’ is to be run on another MacOS machine, right ? AFAIK that utility is not available on Linux. So essentially this procedure requires another MacOS machine, right ?

    • astr0baby says:

      Hi yes, if you do not have a virtual macos, you can just download the clover.iso and then install macos, and run the script from there.

      • octapod says:

        Thank you. Any chance if you could clarify if the VM’s display resolution could be changed to another value s.a. 1920×1080 or say 1600×900 ?

      • astr0baby says:

        If you want 1920×1080 please use this clover4k.iso https://drop.me/M3pZW7 and adjust your VirtualBox settings accordingly as follows :
        #!/bin/bash
        readonly VM_RES=”1980×1080″
        readonly NAME=”Mojave”

        VBoxManage modifyvm “$NAME” –usbxhci on –firmware efi –chipset ich9 –mouse usbtablet –keyboard usb
        VBoxManage setextradata “$NAME” “CustomVideoMode1” “${VM_RES}x32”
        VBoxManage setextradata “$NAME” VBoxInternal2/EfiGraphicsResolution “$VM_RES”
        VBoxManage modifyvm “$NAME” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
        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” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
        VBoxManage setextradata “$NAME” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

  35. Abdulrahman Hassoun says:

    I am still unable to get the mouse and keyboard to work despite running that script without errors. I am stuck on the installation screen.

    The host machine is Antergos Linux 4.19.19
    VB is 6.0.4
    Extension pack is installed and up-to-date.

    Any suggestions?

    • astr0baby says:

      Make sure your USB controller is xHCI and Operating system (VirtualBox) is set to MacOS High Sierra 64bit

      • Abdulrahman Hassoun says:

        Thanks for the super quick response, the problem is solved!
        Both settings were OK. My problem was with (Pointing Device) in System settings.
        By default, it was ‘USB Multi-touch tablet’, what worked for me is ‘USB Tablet’

        Thanks for the tutorial!

      • astr0baby says:

        Strange, on Linux VirtualBox 6.x default is USB Tablet under pointing device. Great that its working for you now.

  36. octapod says:

    Thanks a lot again @astr0baby.
    Noticed that the VM start with a 30GB virtual-disk. My SSD is beginning to get a little cramped, so wondering if there is a possibility to start with a smaller disk (say 15-20GB), and later add another virtual-disk (say on my HDD partition) ? Is it possible to use the App Store with this ISO ? Finally, are Guest Additions available for the resulting VM ?

    • astr0baby says:

      You can experiment with various disk sizes, but generally it better to use larger disk, later you will run out of space, you can add of course additional disk, but it will be a secondary SCSI drive. Yes AppStore works with this, installation is vanilla macOS.

  37. octapod says:

    Is it normal that after the first time running standard setup through clover (i.e. 1st time Clover is used), one stays in the **Installing on “Mojave”** screen for a very very long time ? I was on “About 12 minutes remaining” after about 15 minutes of starting the setup, and was on “About 11 minutes remaining” after about another 20-25 minutes. Is the progress on that screen expected to be very slow ?

    • astr0baby says:

      Yes the second stage install takes some time, depends on the speed of your HDD/SSD … on my SSD it takes roughly 40 minutes to install

    • octapod says:

      Thanks much to @astr0baby! The phase-2 took about 7 hours for me (everything on SSD), however worth the wait. Regular desktop apps seem to have fairly acceptable performance so far. Plan to install Garageband and see what the performance is like. Few additional questions @astr0baby —
      1. Does Clover.iso always need to remain mounted, and I shall always need to boot into Mojave using Clover ? Or can Clover be removed ?
      2. Did my initial installation using the Clover with “1680×1050” set as display resolution and not the 4K one that you shared. Is there a way to change the display resolution now, without reinstalling MacOS ?
      3. Is it safe to enable auto update of MacOS on this setup, or there are chances of kernel panics or crashes ?
      4. Is it possible to add a virtual disk, to this VM and make it visible to MacOS ? Perhaps a disk that I’d use to store large audio/video files instead of keeping them on the current virtual-disk which is on the SSD ?

      • astr0baby says:

        1.) You only need the Clover.iso during boot (keep that in mind)
        2.) If you wish to use another resolution you need to customize clover.iso to include the fixed size (Clover4k.iso is for 1920×1080)
        and adjust VirtualBox Mojave settings accordingly
        3.) Its perfectly safe to install updates, nothing will crash and all kernels work fine, as long as you boot it with Clover.iso
        4.) Of course, you need to use DiskUtility and format it accordingly once inside macos

  38. octapod says:

    @astro0baby, sorry that I posted the question#4 above before I saw your response on the topic, kindly ignore the same. OTOH, the download of Garageband went fine, but found that my Mojave installation has no audio input or output devices. Searching around I came across several posts that seem to hint at potential solution — but my knowledge of Clover, editing plists, adding/removing kexts is pretty limited. Wondering if something seems obvious to you that I might try to get the sound devices in this Mojave setup ?

    Links found:
    https://www.tonymacx86.com/threads/solved-mojave-audio-only-hdmi-no-other-devices-found.261579/
    https://www.tonymacx86.com/threads/mojave-and-audio-alc887.260505/
    https://www.tonymacx86.com/threads/no-sound-output.259222/
    https://www.tonymacx86.com/threads/no-audio-devices-applehda-realtek-audio.234729/

    Why I considered those relevant is because my desktop is indeed 8th Gen intel, and mobo is H310 with Realtek ALC887 Codec, and the initial symptoms are very similar.

    • astr0baby says:

      For audio you are on your own, search the threads here, there was somebody who got it working … good luck ;)

      • octapod says:

        Thank you again @astr0baby. I found your post on usage of Clover and currently going through it. I will take a snapshot before I experiment further and hope to get audio working, perhaps even the USB audio interface. Regarding having the Clover.ISO always mounted, I suppose that with the optical drive occupied, there is no way to add the guest-additions since that too is mounted as an optical drive, right ?

      • astr0baby says:

        Of course you can unmount it, Clover is only needed for the initial boot process, afterwards just unmount it. Make sure next time you boot, you have it ready

  39. octapod says:

    Thanks a lot for your helpful and pertinent answers. It’s a shame that Wikipedia doesn’t have threaded discussions. I seem to have missed your response by a whisker, yet again.

  40. octapod says:

    Sorry to have to ask one more question. Is it possible to use MultiBeast (s.a. v11) somehow with the combination of Clover.iso and already installed MacOS setup in Virtualbox using the method described by this article ? I’ve gotten around to spending good part of the day to get a handle on what might be the Hackingt0sh setup 101 (in fact, I compiled a document together — happy to share with anyone interested), and I think I understand kexts, Clover itself, Clover Configurator app, EFI partition, SMBIOS, and to some extent even DSDT and SSDT patching. However, still a bit confused (and unsure) where to start. Any thoughts ?

  41. mike says:

    Hi astr0baby and thanks for your guides,
    when i launch the script in fedora 29 i ve got the error
    VBoxManage: error: Could not find a registered machine named ‘Mojave’
    my $ VBoxManage list vms
    “Mojave” {0cdd5f96……….
    i can’t understand, it’s fedora issue or i miss something?
    here the script:
    #!/bin/bash
    readonly VM_RES=”1680×1050″
    readonly NAME=”Mojave”

    VBoxManage modifyvm “$NAME” –usbxhci on –firmware efi –chipset ich9 –mouse usbtablet –keyboard usb
    VBoxManage setextradata “$NAME” “CustomVideoMode1” “${VM_RES}x32”
    VBoxManage setextradata “$NAME” VBoxInternal2/EfiGraphicsResolution “$VM_RES”
    VBoxManage modifyvm “$NAME” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
    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” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
    VBoxManage setextradata “$NAME” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

    • astr0baby says:

      What is your VirtualBox VM name ? In the script I am using “Mojave” as an example, please check in your ~/”VirtualBox VMs” directory the name of the Mojave instance.

  42. mike says:

    Ok, i get it now…….i was launching the script as sudo……..that was me :)

  43. P K says:

    Tried everything but mouse and keyboard does not work Ubuntu 18.10 with Virtualbox 5.2/6.0 .

  44. Help. I don’t see “Boot MacOS from Mojave” option on clover. I initially set the version to Mac OS X but it gets black screen. Then I changed the version to High Sierra, I see the clover ui but I don’t see the “Boot MacOS from Mojave” option.

    • astr0baby says:

      Not sure what you have done, maybe its better to erase the VM from VirtualBox and start over ? Please follow the instructions, make sure you have the proper settings in place, it must work for you (I have verified the setup numerous times on my Linux Mint)

  45. Can I use any other VM resolution smaller than 1680×1050? The resolution of my laptop is 1366×768.

  46. Eduardo Lopes says:

    Hi, when I run the script it always gives me errors, can you help me?

    [eduardolp3@eduardolp3-manjaro Documenti]$ ./Mojave.sh
    ./Mojave.sh: riga 2: readonly: “=”: non è un identificatore valido
    ./Mojave.sh: riga 2: readonly: “1680×1050”: non è un identificatore valido
    ./Mojave.sh: riga 3: readonly: “=”: non è un identificatore valido
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 520 of file VBoxManageModifyVM.cpp
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 934 of file VBoxManageMisc.cpp
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 934 of file VBoxManageMisc.cpp
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 520 of file VBoxManageModifyVM.cpp
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 934 of file VBoxManageMisc.cpp
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 934 of file VBoxManageMisc.cpp
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 934 of file VBoxManageMisc.cpp
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 934 of file VBoxManageMisc.cpp
    VBoxManage: error: Could not find a registered machine named ‘$ Mojave’
    VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
    VBoxManage: error: Context: “FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())” at line 934 of file VBoxManageMisc.cpp
    [eduardolp3@eduardolp3-manjaro Documenti]$

  47. Eduardo Lopes says:

    Hi, I managed to start the script without errors, I started installing Mojave but when I get to the screen to choose the system language neither the mouse nor the keyboard are recognized and the trackpad doesn’t even work so I can’t go continue with the installation. What can I do?

  48. Eduardo Lopes says:

    524/5000
    I managed to install Mojave. It is not very clear to me what I have to do now that the system is restarted and I returned to the first screen or MACOS UTILITIES. I have to shut down the system (how, with bad manners?) and then start it with clover.iso (do I have to change the boot ISO in STORAGE?). It is essential to start the script for clover.it or by downloading it from the link you released, https://drop.me/MRqW76, is everything ok already? If I have to run the script do I have to close Virtualbox? Thanks for your patience, it is just a little away!

  49. TonyA says:

    Can’t finish part 1 of Mojave installation on Dell XPS 13 running Ubuntu 18.04 and VB 5.2.18 with extension pack 5.2.18. Neither keyboard nor mouse can select the language and the continuation buttom at first Mojave installation screen.
    Vbox commands were all executed before and USB-3 devices are visible.

    • TonayA says:

      After putting myself in the vboxuser group and starting all over, I managed to proceed one step further. Now the installation hangs at the clover.iso boot cycle on the “Installing Mojave” screen at 16 minutes. It does not proceed and after a hard reset it always ends up at this place.
      Any suggestions?

    • astr0baby says:

      Please first boot with normal Mojave and do non-clover 1st stage install (short) – then reboot/force reset, insert clover and boot second stage installer

      • TonayA says:

        I did follow your instructions step by step, also the above ones. After the short installation, which works as described, I RESET and boot Mojave with clover.iso from the disk and I only committed the network part, as I’m using NAT. Could that have an influence? Is there any way of getting a verbose mode during boot-up or at least a log to see where it’s not progressing? Would I perhaps need to update Clover and how would I do that? I have downloaded the ISO via your link.
        Thank you!

  50. TonyA says:

    After I changed VM settings from default to the values suggested in https://techsviewer.com/install-macos-10-14-mojave-virtualbox-windows/, I was finally able to proceed and got Mojave to run.
    Thank you very much!

    • astr0baby says:

      The required settings for the VirtualBox should be in the installation articles I wrote, not sure why it was missed, but Im glad it worked for you. Please remember you can update Mojave normally from AppStore, but you will need to load the update installer from clover boot menu

  51. TonyA says:

    Is it possible to change the screen resolution, after a successful installation? If yes, what steps are necessary?

  52. TonyA says:

    I tried to boot with the modified clover.iso with 1980×1080 executing the necessary VB command before, but this has messed up the screen of the Mojave VM and I can’t get it back to normal. Going back to the standard Clover.iso did not work. Then I removed the VM and tried to create a new one with the 1980×1080 clover.iso. Same result, just white noise on the black screen after booting up. How can I get this corrected?

    • astr0baby says:

      You have to have exact same values in VirtualBox as well as Clover. For the 1980×1080 you need to do the following:
      #!/bin/bash
      readonly VM_RES=”1980×1080″
      readonly NAME=”Mojave” <—- CHANGE HERE TO WHAT YOU HAVE NAMED YOUR VM !!!!!

      VBoxManage modifyvm “$NAME” –usbxhci on –firmware efi –chipset ich9 –mouse usbtablet –keyboard usb
      VBoxManage setextradata “$NAME” “CustomVideoMode1” “${VM_RES}x32”
      VBoxManage setextradata “$NAME” VBoxInternal2/EfiGraphicsResolution “$VM_RES”
      VBoxManage modifyvm “$NAME” –cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
      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” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”
      VBoxManage setextradata “$NAME” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

  53. TonyA says:

    That’s what I followed strictly, but I can’t get it back to work. Even going back to the original clover.iso with 1680×1050 does not work any more even though I execute the corresponding command at the top of this article. Looks like something in VirtualBox must have been changed and does not change back. Other VM, like Sierra do work. Any ideas?

    • astr0baby says:

      Can you post VBoxManage showvminfo NAMEOFVM ?

      Like this
      user@panasonic ~ $ VBoxManage showvminfo Mojave2
      Name: Mojave2
      Groups: /
      Guest OS: macOS 10.13 High Sierra (64-bit)
      UUID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      Config file: /home/user/VirtualBox VMs/Mojave2/Mojave2.vbox
      Snapshot folder: /home/user/VirtualBox VMs/Mojave2/Snapshots
      Log folder: /home/user/VirtualBox VMs/Mojave2/Logs
      Hardware UUID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      Memory size 4096MB
      Page Fusion: disabled
      VRAM size: 128MB
      CPU exec cap: 100%
      HPET: enabled
      CPUProfile: host
      Chipset: ich9
      Firmware: EFI
      Number of CPUs: 2
      PAE: enabled
      Long Mode: enabled
      Triple Fault Reset: disabled
      APIC: enabled
      X2APIC: disabled
      Nested VT-x/AMD-V: disabled
      CPUID Portability Level: 0
      CPUID overrides: Leaf no. EAX EBX ECX EDX
      00000001/000 000106e5 00100800 0098e3fd bfebfbff
      Boot menu mode: message and menu
      Boot Device 1: Floppy
      Boot Device 2: DVD
      Boot Device 3: HardDisk
      Boot Device 4: Not Assigned
      ACPI: enabled
      IOAPIC: enabled
      BIOS APIC mode: APIC
      Time offset: 0ms
      RTC: UTC
      Hardw. virt.ext: enabled
      Nested Paging: enabled
      Large Pages: disabled
      VT-x VPID: enabled
      VT-x unr. exec.: enabled
      Paravirt. Provider: Default
      Effective Paravirt. Prov.: Minimal
      State: powered off (since 2019-03-28T00:03:22.000000000)
      Monitor count: 1
      3D Acceleration: enabled
      2D Video Acceleration: disabled
      Teleporter Enabled: disabled
      Teleporter Port: 0
      Teleporter Address:
      Teleporter Password:
      Tracing Enabled: disabled
      Allow Tracing to Access VM: disabled
      Tracing Configuration:
      Autostart Enabled: disabled
      Autostart Delay: 0
      Default Frontend:
      Storage Controller Name (0): SATA
      Storage Controller Type (0): IntelAhci
      Storage Controller Instance Number (0): 0
      Storage Controller Max Port Count (0): 30
      Storage Controller Port Count (0): 3
      Storage Controller Bootable (0): on
      SATA (0, 0): /home/user/VirtualBox VMs/Mojave2/Mojave2.vdi (UUID: xxxxxxx-xxxx-xxxx-xxx-xxxxxx)
      SATA (1, 0): /home/user/ROMs/APPLE/clover-1280-SIP.iso (UUID: 38abed8f-4cfd-4852-8c8c-4d5b956fe1eb)
      NIC 1: MAC: 080027D67657, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82545EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
      NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
      NIC 2: disabled
      NIC 3: disabled
      NIC 4: disabled
      NIC 5: disabled
      NIC 6: disabled
      NIC 7: disabled
      NIC 8: disabled
      NIC 9: disabled
      NIC 10: disabled
      NIC 11: disabled
      NIC 12: disabled
      NIC 13: disabled
      NIC 14: disabled
      NIC 15: disabled
      NIC 16: disabled
      NIC 17: disabled
      NIC 18: disabled
      NIC 19: disabled
      NIC 20: disabled
      NIC 21: disabled
      NIC 22: disabled
      NIC 23: disabled
      NIC 24: disabled
      NIC 25: disabled
      NIC 26: disabled
      NIC 27: disabled
      NIC 28: disabled
      NIC 29: disabled
      NIC 30: disabled
      NIC 31: disabled
      NIC 32: disabled
      NIC 33: disabled
      NIC 34: disabled
      NIC 35: disabled
      NIC 36: disabled
      Pointing Device: USB Tablet
      Keyboard Device: USB Keyboard
      UART 1: disabled
      UART 2: disabled
      UART 3: disabled
      UART 4: disabled
      LPT 1: disabled
      LPT 2: disabled
      Audio: enabled (Driver: PulseAudio, Controller: HDA, Codec: STAC9221)
      Audio playback: disabled
      Audio capture: enabled
      Clipboard Mode: disabled
      Drag and drop Mode: disabled
      VRDE: disabled
      OHCI USB: disabled
      EHCI USB: disabled
      xHCI USB: enabled

      USB Device Filters:

      Bandwidth groups:

      Shared folders:

      Capturing: not active
      Capture audio: not active
      Capture screens: 0
      Capture file: /home/user/VirtualBox VMs/Mojave2/Mojave2.webm
      Capture dimensions: 1024×768
      Capture rate: 512kbps
      Capture FPS: 25kbps
      Capture options:

      Guest:

      Configured memory balloon size: 0MB

      • TonyA says:

        Below are my VB values for the 1980×1080 case. Is there any way of verifying the configuration of the Clover.iso? I’m asking because the one I produced with your clover.sh script for 1980×1080 was the initial cause of my problem and starts with an initial boot screen way too large, so I need to center before I even see the boot options and arrow keys do not work either.

        user@home:~$ VBoxManage getextradata “Mojave” enumerate
        Key: CustomVideoMode1, Value: 1980x1080x32
        Key: GUI/LastCloseAction, Value: PowerOff
        Key: GUI/LastNormalWindowPosition, Value: 67,57,1853,1023
        Key: GUI/LastScaleWindowPosition, Value: 217,133,1328,847
        Key: GUI/Scale, Value: true
        Key: VBoxInternal/Devices/efi/0/Config/DmiBoardProduct, Value: Iloveapple
        Key: VBoxInternal/Devices/efi/0/Config/DmiSystemProduct, Value: iMac11,3
        Key: VBoxInternal/Devices/efi/0/Config/DmiSystemVersion, Value: 1.0
        Key: VBoxInternal/Devices/smc/0/Config/DeviceKey, Value: ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc
        Key: VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC, Value: 1
        Key: VBoxInternal2/EfiGraphicsResolution, Value: 1980×1080

        user@home:~$ VBoxManage showvminfo Mojave
        Name: Mojave
        Groups: /
        Guest OS: macOS 10.13 High Sierra (64-bit)
        UUID: 4342d05b-823e-4204-a367-eecf2f474c22
        Config file: /home/user/VirtualBox VMs/Mojave/Mojave.vbox
        Snapshot folder: /home/user/VirtualBox VMs/Mojave/Snapshots
        Log folder: /home/user/VirtualBox VMs/Mojave/Logs
        Hardware UUID: 4342d05b-823e-4204-a367-eecf2f474c22
        Memory size: 4096MB
        Page Fusion: off
        VRAM size: 128MB
        CPU exec cap: 100%
        HPET: on
        Chipset: ich9
        Firmware: EFI
        Number of CPUs: 1
        PAE: on
        Long Mode: on
        Triple Fault Reset: off
        APIC: on
        X2APIC: off
        CPUID Portability Level: 0
        CPUID overrides: Leaf no. EAX EBX ECX EDX
        00000001/000 000106e5 00100800 0098e3fd bfebfbff
        Boot menu mode: message and menu
        Boot Device (1): DVD
        Boot Device (2): HardDisk
        Boot Device (3): Not Assigned
        Boot Device (4): Not Assigned
        ACPI: on
        IOAPIC: on
        BIOS APIC mode: APIC
        Time offset: 0ms
        RTC: UTC
        Hardw. virt.ext: on
        Nested Paging: on
        Large Pages: off
        VT-x VPID: on
        VT-x unr. exec.: on
        Paravirt. Provider: Default
        Effective Paravirt. Provider: Minimal
        State: powered off (since 2019-04-17T20:59:01.000000000)
        Monitor count: 1
        3D Acceleration: on
        2D Video Acceleration: off
        Teleporter Enabled: off
        Teleporter Port: 0
        Teleporter Address:
        Teleporter Password:
        Tracing Enabled: off
        Allow Tracing to Access VM: off
        Tracing Configuration:
        Autostart Enabled: off
        Autostart Delay: 0
        Default Frontend:
        Storage Controller Name (0): SATA
        Storage Controller Type (0): IntelAhci
        Storage Controller Instance Number (0): 0
        Storage Controller Max Port Count (0): 30
        Storage Controller Port Count (0): 2
        Storage Controller Bootable (0): on
        SATA (0, 0): /home/user/VirtualBox VMs/Mojave/Mojave.vdi (UUID: 2cd7ef82-7a06-4259-a3f7-60344a04e7ad)
        SATA (1, 0): /home/user/Downloads/clover_1.iso (UUID: 763a2792-6951-4dd4-9542-f99de424a55c)
        NIC 1: MAC: 080027215BD7, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82545EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
        NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
        NIC 2: disabled
        NIC 3: disabled
        NIC 4: disabled
        NIC 5: disabled
        NIC 6: disabled
        NIC 7: disabled
        NIC 8: disabled
        NIC 9: disabled
        NIC 10: disabled
        NIC 11: disabled
        NIC 12: disabled
        NIC 13: disabled
        NIC 14: disabled
        NIC 15: disabled
        NIC 16: disabled
        NIC 17: disabled
        NIC 18: disabled
        NIC 19: disabled
        NIC 20: disabled
        NIC 21: disabled
        NIC 22: disabled
        NIC 23: disabled
        NIC 24: disabled
        NIC 25: disabled
        NIC 26: disabled
        NIC 27: disabled
        NIC 28: disabled
        NIC 29: disabled
        NIC 30: disabled
        NIC 31: disabled
        NIC 32: disabled
        NIC 33: disabled
        NIC 34: disabled
        NIC 35: disabled
        NIC 36: disabled
        Pointing Device: USB Tablet
        Keyboard Device: USB Keyboard
        UART 1: disabled
        UART 2: disabled
        UART 3: disabled
        UART 4: disabled
        LPT 1: disabled
        LPT 2: disabled
        Audio: enabled (Driver: PulseAudio, Controller: HDA, Codec: STAC9221)
        Audio playback: disabled
        Audio capture: enabled
        Clipboard Mode: disabled
        Drag and drop Mode: disabled
        VRDE: disabled
        USB: disabled
        EHCI: disabled
        XHCI: enabled

        USB Device Filters:

        Bandwidth groups:

        Shared folders:

        Guest:

        Configured memory balloon size: 0 MB

  54. TonyA says:

    Finally found the error. The Clover.iso I’ve created on the VM Mojave with your script had a config.plist with only the line: “404: Not Found”. Hence it did not work. I went back and tried with your Clover4k.iso and this time it went fine. I also realized, that when I paste the VB shell commands in a terminal they did not change the resolution values set before unless I logged out and back in.
    Thank you very much for all your support.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

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