Installing macOS Mojave 10.14 on Proxmox 5.2

This tutorial was updated on 2018-10-01 for the final release of Mojave

This tutorial for installing macOS Mojave has been adapted for Proxmox 5.2 from Kholia’s GitHub project for installing into vanilla KVM. There is more documentation there which will help out with enabling extra features and diagnosing problems!

Requirements

I’ll assume you already have Proxmox 5.2 installed. You also need a real Mac available in order to download Mojave from the App Store and build the installation ISO.

Your Proxmox host computer must have an Intel CPU (I believe you would need a custom Mac kernel in order to use an AMD CPU). Your CPU must be at least as new as Nehalem, which was the first CPU generation to bear the “Core” i5/i7 branding. Older CPUs will cause the finder to repeatedly crash after installation completes (with an Illegal Instruction exception in the graphics code).

First step: Create an installation ISO

On a Mac machine, use the App Store to download the Mojave 10.14 installer:

Now run this script in order to create Mojave.iso from the installer. The ISO should get saved to your desktop. Upload the ISO to your Proxmox server’s ISO store (typically /var/lib/vz/template/iso).

Note: Apparently if the Mac you’re using for the download is already running Mojave, this won’t let you download the installer properly. There is some advice and workarounds in this Reddit thread.

Prepare a Clover image

We’ll be using Clover as a bootloader for Mojave.

Download this Clover disk image (that I built using kholia’s build script from Clover r4674), unpack it, and upload it to Proxmox’s ISO store at /var/lib/vz/template/iso. Although it has a .iso file extension, this is actually a hard disk image. (I do it this way because Proxmox has nicer tools for storing and picking .iso files for us)

Fetch the OSK authentication key

macOS checks that it is running on real Mac hardware, and refuses to boot on third-party hardware. You can get around this by reading an authentication key out of your real Mac hardware (the OSK key). Run the first bit of C code from this page (you’ll need XCode installed) and it’ll print out the 64 character OSK for you. Make a note of it.

Every Mac uses the same OSK, so don’t be surprised if it doesn’t look like a random string!

Create the VM

From the Proxmox web UI, create a new virtual machine as shown below.

In the Options page for the VM, make sure “use tablet for pointer” is set to “Yes”. Change “BIOS” to “OVMF (UEFI)”.

In the Hardware page for the VM, change the the Display to Standard VGA (std). Add a second DVD drive at IDE0, set it to use your Mojave.iso. Add an “EFI Disk” too.

Don’t try to start the VM just yet. First, SSH into your Proxmox server so we can make some edits to the configuration files.

Edit /etc/pve/qemu-server/YOUR-VM-ID-HERE.conf (with nano or vim). Add these two lines, being sure to subtitute the OSK you extracted earlier into the right place:

machine: pc-q35-2.11
args: -device isa-applesmc,osk="THE-OSK-YOU-EXTRACTED-GOES-HERE" -smbios type=2 -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check

We’re telling macOS that the CPU is Penryn (it doesn’t seem to like booting otherwise), but we’re enabling all the new CPU features found in Nehalem which macOS will require, plus some optional features found in later generations (AVX/AES).

Find the line that defines the Clover ISO (ide2), and remove the “,media=cdrom” part from it. Add “,cache=unsafe” in its place.

On the net0 line, change “e1000” to “e1000-82545em”. This variant is supported by OS X.

Save your changes, return to the Options tab, and change the boot order to put IDE2 (the Clover image) first.

Configure Proxmox

On Proxmox, run “echo 1 > /sys/module/kvm/parameters/ignore_msrs” to avoid a bootloop during macOS boot. To make this change persist across Proxmox reboots, run:

echo "options kvm ignore_msrs=Y" >>/etc/modprobe.d/kvm.conf && update-initramfs -k all -u

You must now install a patched version of Proxmox’s OVMF library in order to be able to boot Mojave.

Install Mojave

Now start up your VM.

Go to the Console tab, quickly hit Escape at the Proxmox logo to enter the OVMF configuration. If your keyboard doesn’t work, leave the Console tab, stop the VM, start the VM, then re-enter the console tab. If pressing escape still doesn’t enter the menu, make sure you are using “machine: pc-q35-2.11” in your VM config and you do not have a USB keyboard defined in pve-q35.cfg (it seems that the OVMF menu only supports the default PS/2 keyboard at the moment).

Follow the steps above to set the screen resolution to 1024×768 and “reset” to apply the new settings (not “continue”). This step is required to avoid scrambled graphics on boot and a hang (Clover resolution must match OVMF resolution).

Mojave doesn’t support QEMU’s PS2 keyboard and mouse, but it does support the USB tablet we’ve selected on the Options page. Edit /usr/share/qemu-server/pve-q35.cfg and add a USB keyboard to the bottom of the file to replace the PS/2 one it would provide by default:

[device "keyboard1"]
 driver = "usb-kbd"
 bus = "ehci.0"
 port = "2"

(Port 1 is occupied by the USB tablet that Proxmox will provide for us)

We’ve added this to the config file instead of to the VM’s args directly. If we were to add it to the VM’s args, then when Proxmox constructs its call to KVM to launch the VM, the device definition would appear before the pve-q35.cfg file is included, which defines the USB busses. However, the device definition must appear after the definition of the USB bus that it refers to.

Note that this file is whitespace-sensitive, make sure you don’t add any blank lines that have extraneous spaces on them.

Stop the VM and start it again to pick up this new keyboard config. It should now boot into Clover.

Clover boot screen

Press enter to boot the “Boot macOS Install from Install macOS Mojave” entry and the installer should appear. Choose your language.

Our virtual hard drive needs to be erased/formatted before we can install to it, so select the Disk Utility option. Follow the steps below to format the disk:

Now we’re ready to begin installation!

After the first stage of installation, the VM should reboot itself and automatically continue installation by booting from the hard drive, then reboot itself a second time and automatically boot from “filevault prebooter”.

Answer the initial install questions, and you’ll be logged on! (Note that you’ll probably want to hold off on logging into your iCloud account until you’ve configured your SMBIOS to your liking in Clover Configurator)

Make the Clover install permanent

We’re currently booting using Clover from the attached CD image. Let’s install that to the hard drive instead. Pop open Terminal and run “diskutil list” to see what drives we have available.

Use “sudo dd if=<source> of=<dest>” to copy the “EFI” partition from the Clover CD and overwrite the EFI partition on the hard disk. The Clover CD is the small disk with the “linux filesystem” on it, and the main hard disk is the one with the large Apple_APFS “Container” partition on it.

In my case these EFI partitions ended up being called disk1s1 and disk0s1 respectively, so I ran “sudo dd if=/dev/disk1s1 of=/dev/disk0s1” (N.B. if you get these names wrong, you will erase the wrong disk and you’ll have to start the installation over again!).

Now shut down the VM, and remove both the Clover and the Mojave CDROM drives from the Hardware tab. On the Options tab, edit the boot order to place SATA0 as the first disk. Boot up. If everything went well, you should see the Clover boot menu, and you can select “Boot macOS from Main” to boot Mojave.

Choose “boot macOS from Main”

Sleep management

I found that I was unable to wake Mojave from sleep using my mouse or keyboard. You can either disable system sleep in Mojave’s Energy Saver settings to avoid this, or you can manually wake the VM up from sleep from Proxmox by running:

qm monitor YOUR-VM-ID-HERE
system_wakeup
quit

Editing your Clover/EFI settings

You can use the Clover Configurator tool (Global Edition) to edit your Clover “config.plist” configuration file, which is stored in the hard drive’s EFI partition. This tool should mount the EFI partition for you. If you want to mount it without using Clover Configurator, first check the device name of the EFI partition in the terminal:

~$ diskutil list
/dev/disk0 (external):
   #:             TYPE   NAME           SIZE       IDENTIFIER
   0: GUID_partition_scheme             512.1 GB   disk0
   1:              EFI   EFI            209.7 MB   disk0s1
   2:        Apple_HFS   Main           511.8 GB   disk0s2

Then you can mount it like so:

sudo mkdir /Volumes/EFI
sudo mount -t msdos /dev/disk0s1 /Volumes/EFI

USB passthrough

Since I want to use this as my primary computer, I want to use a USB keyboard and mouse plugged directly into Proxmox, rather than sending my input through the web VNC console.

Proxmox has good documentation for USB passthrough. Basically, run “qm monitor YOUR-VM-ID-HERE”, then “info usbhost” to get a list of the USB devices connected to Proxmox:

qm> info usbhost
 Bus 3, Addr 12, Port 6, Speed 480 Mb/s
 Class 00: USB device 8564:1000, Mass Storage Device
 Bus 3, Addr 11, Port 5.4, Speed 12 Mb/s
 Class 00: USB device 04d9:0141, USB Keyboard
 Bus 3, Addr 10, Port 5.1.2, Speed 12 Mb/s
 Class 00: USB device 046d:c52b, USB Receiver
 Bus 3, Addr 9, Port 14.4, Speed 12 Mb/s
 Class 00: USB device 046d:c227, G15 GamePanel LCD
 Bus 3, Addr 8, Port 14.1, Speed 1.5 Mb/s
 Class 00: USB device 046d:c226, G15 Gaming Keyboard

In this case I can add my keyboard and mouse to USB passthrough by quitting qm, then running:

qm set YOUR-VM-ID-HERE -usb1 host=04d9:0141
qm set YOUR-VM-ID-HERE -usb2 host=046d:c52b

This saves the devices to the VM configuration for you. It’s possible to hot-add USB devices, but I just rebooted my VM to have the new settings apply.

You can also pass through USB devices by passing through an entire USB controller using Proxmox’s PCIe passthrough feature.

83 thoughts on “Installing macOS Mojave 10.14 on Proxmox 5.2”

  1. Hi Nicholas,
    thank you very much, installation runs smooth. Have you tried GPU passthrough?
    Michael

    1. I’ve heard that the Nvidia drivers don’t offer acceleration yet (even after hacking them to force installation on the unsupported OS). I think we’ll have to wait for some time after the retail release before we get those.

      I have an AMD card I could try, I’ll report back with details.

      1. Hi Nicholas,

        At the end of the guide and in some comments, you talk about to use this VM to make it your primary computer.
        So on Firefox and Atom I have some strange graphics behavior (you too ?) did you find anything to improve the performances of the VM ?

        I have no GPU passthrough (no GPU card on the host).

        1. Without a passthrough GPU you’ll have no graphics acceleration, which as far as I know dooms you to slow glitchy graphics.

          1. Ok i see, you said “I have an AMD card I could try, I’ll report back with details.” can you tell us about that ?
            thanks

          2. Yep I’m now running Mojave with an R9 280x, however it has visual glitches and kills the host the second time the VM is booted. I’ve had the same problems with this card in previous macOS versions. I believe there are much better supported cards available now.

  2. I was able to use GPU passthrough – but I haven’t found a solution to the frequently crashing finder – maybe I run proxmox on a Westmere CPU?

      1. Although being root I get a “-bash: /proc/cpuinfo: Permission denied”??
        Anyway: I am using an Intel Xeon X5660…

        1. That’s bizarre, I’ve never seen an error like that while trying to access cpuinfo. Are you missing the “cat” on the start of that command?

          Your CPU *should* be supported, because it’s a die-shrink of Nehalem and I’d expect it to have the same features.

          You might have to cat /proc/cpuinfo | grep flags and check if it lists ssse3 (note, three ‘s’s), sse4_2 and popcnt (the new features that Nehalem introduced over Penryn).

  3. Shame on me: to dumb for copy/paste!
    12x model name : Intel(R) Xeon(R) CPU X5670 @ 2.93GHz
    flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm pti tpr_shadow vnmi flexpriority ept vpid dtherm ida arat
    … everything there.
    Please ignore my stupid response.

  4. I’ve followed all steps above but for some bizarre reasons can’t get Clover to recognize the Mojave iso mounted on IDE0. I’m on the latest version of Proxmox (5.2-5) with all updates applied.
    Has anything changed recently that could cause this issue?

    1. And of course, right after I posted this comment, I found the solution.

      I mistakenly changed “media=cdrom” to “cache=unsafe” for BOTH ide0 and ide2. This is only necessary for ide2 (Clover), not ide0 (Mojave).

      Thanks for the great tutorial!

    1. I haven’t been able to get this working yet. I think there is an EFI driver needed for the keyboard.

      You can boot into the recovery mode to unlock the disk I believe (that’s a full copy of the OS so it supports the keyboard properly).

  5. Hi,

    i have problem – on booting I get error message. Do you have any idea how to solve it?

    kvm: -device ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1: Can’t create IDE unit 1, bus supports only 1 units
    TASK ERROR: start failed: command ‘/usr/bin/kvm -id 101 -name MacOSX …’ failed: exit code 1

    1. From the message it sounds like you might have two ide devices on the same bus (e.g. 0 + 1). The second IDE drive needs to be assigned to number 2 rather than 1. (drive #1 would be the slave of #0, which isn’t supported).

        1. Edit the config file for the VM using SSH (it’s in /etc/pve/qemu-server) and rename the config line for ide1 to ide2.

  6. Now it looks like this – so what I need to change – because there is already ide2…?

    ide0: local:iso/osx.iso,cache=unsafe,size=5600M,media=cdrom
    ide1: local-lvm:vm-101-disk-1,cache=unsafe,size=64G
    ide2: local:iso/clover-r4428-amd64.iso,cache=unsafe

    Thanks in advance!

  7. Now it’s:

    ide0: local:iso/HighSierra.iso,cache=unsafe,size=5600M,media=cdrom
    ide1: local-lvm:vm-101-disk-1,cache=unsafe,size=64G
    sata0: local:iso/clover-r4428-amd64.iso,cache=unsafe

    and error still appears:
    kvm: -device ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1: Can’t create IDE unit 1, bus supports only 1 units

  8. And there is next problems…

    1) Keyboard is ultra sensitive – it works, but single keypress effect 3-4 chars in system,
    2) After first step of installation and reboot it freezes on apple logo. I have double checked resolution, I try to setup it just before restart, I try to reboot after change – nothing helps…

    Aby suggestions?

    1. It sounds like you have forgotten to add the “cpu” argument to the args, which is required for proper timing, so the clock runs fast and the key repeat is accelerated.

      1. I have (from beginning) setup 1 socket, 4 cores, Penryn. Is there any other option?

        Is it connected with boot problem or its different problem?

        1. You are missing this in the “args” in your VM config file:

          -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check

  9. I installed HighSierra from iso and just having this enoch_rev2898_boot.
    I was enable to install Mojave like this from iso, but after the installation the os disk is not available in the boot menu (I can only see the install media)
    Do you know how this can be resolved?
    PS did not use clover things etc.

  10. Diving straight in as a new Proxmox user I decided to follow this guide and install the now launched Mojave. Having checked my working twice now I can’t find any mistakes but find myself stuck on the apple logo right at the stage of selecting boot macOS install from clover. Seems to sit there indefinitely – longer than I have patience for! with no errors visible. Any suggestions welcomed – even if it’s just to look elsewhere for error logs!

    Proxmox syslog shows this (Mojave is VM 103):
    Sep 30 15:44:28 pve systemd[1]: Started 103.scope.
    Sep 30 15:44:28 pve systemd-udevd[23051]: Could not generate persistent MAC address for tap103i0: No such file or directory
    Sep 30 15:44:29 pve kernel: device tap103i0 entered promiscuous mode
    Sep 30 15:44:29 pve kernel: vmbr0: port 4(tap103i0) entered blocking state
    Sep 30 15:44:29 pve kernel: vmbr0: port 4(tap103i0) entered disabled state
    Sep 30 15:44:29 pve kernel: vmbr0: port 4(tap103i0) entered blocking state
    Sep 30 15:44:29 pve kernel: vmbr0: port 4(tap103i0) entered forwarding state
    Sep 30 15:44:29 pve pvedaemon[14600]: end task UPID:pve:000059FD:0386B2A0:5BB0E14C:qmstart:103:root@pam: OK
    Sep 30 15:45:00 pve systemd[1]: Starting Proxmox VE replication runner…
    Sep 30 15:45:00 pve systemd[1]: Started Proxmox VE replication runner.
    Sep 30 15:45:13 pve pvedaemon[14600]: successful auth for user ‘root@pam’
    Sep 30 15:46:00 pve systemd[1]: Starting Proxmox VE replication runner…
    Sep 30 15:46:00 pve systemd[1]: Started Proxmox VE replication runner.
    Sep 30 15:46:15 pve pvedaemon[14600]: starting task UPID:pve:000064B2:0386DC71:5BB0E1B7:vncproxy:103:root@pam:
    Sep 30 15:46:15 pve pvedaemon[25778]: starting vnc proxy UPID:pve:000064B2:0386DC71:5BB0E1B7:vncproxy:103:root@pam:
    Sep 30 15:46:23 pve pvedaemon[14600]: end task UPID:pve:000064B2:0386DC71:5BB0E1B7:vncproxy:103:root@pam: OK

    Here’s my .conf file (OSK edited):
    machine: pc-q35-2.11
    bios: ovmf
    boot: cdn
    bootdisk: ide2
    cores: 4
    cpu: Penryn
    args: -device isa-applesmc,osk=”64proprietarychars” -smbios type=2 -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check
    efidisk0: ZFS1:vm-103-disk-1,size=128K
    ide0: local:iso/Mojave.iso,media=cdrom,size=7000M
    ide2: local:iso/clover-r4542-amd64.iso,cache=unsafe
    memory: 8192
    name: MacOSMojave
    net0: e1000-82545em=52:DE:77:8B:DB:DE,bridge=vmbr0
    numa: 0
    ostype: other
    sata0: ZFS1:vm-103-disk-0,cache=unsafe,size=64G
    scsihw: virtio-scsi-pci
    smbios1: uuid=9cb82b25-d0be-4e32-8448-fd75b57f7a25
    sockets: 1
    vga: std

    1. Your config looks good, try pressing space on the installer option in Clover and choosing Verbose Boot, this’ll reveal at what point it locks up.

      I’ll probably be rewriting this tutorial soon for the final release of Mojave, so if you get completely stuck, come back here later and see if I have figured everything out :).

    2. I’ve updated the tutorial now for the final release of Mojave, and I didn’t find any surprises (though I am now including a newer release of Clover, try that one).

      Make sure that you have installed the patched UEFI package into Proxmox, it causes a hang on Mojave boot if it’s missing.

      1. That’s it – had missed the instruction to patch UEFI, and even on verbose boot I didn’t get any error messages! Once applying the patched file I was up and running in no time at all. Many thanks!

  11. Just wanted to throw a feedback that it is also working with the live version. However I had to use a different strategy to get the .iso.

    Thanks mate for the nice howto.

  12. First, thanks take the time writing these up. I’d used your guide to install High Sierra before with great luck before (on a different Proxmox host machine).

    I’m having trouble with Mojave, however, running into an issue with a boot loop. This is the error message I’m getting:

    Start ProcessOptions
    End ProcessOptions
    RegisterRestartDataProtocol: called. Ox7dI4ad9O
    Restartnata protocol installed successfully.
    Start SetConsoleMode
    End SetConsoleMode
    Start ReadllernelCache
    End ReadllernelCache
    Start UncompressllernelCache
    End UncompressllernelCache
    Start CalculateAdler32
    End CalculateAdler32
    Start LoadllernelFromStream
    End LoadllernelFromStream
    Start InitBootStruct

    root device uuid is ‘ACB39C20-0C7B-3B0C-OB03-79EAOBBE3302.
    End InitBootStruct
    Start LoadRAMDisk
    End LoadRAMDisk
    Start FinalizeBootStruct
    Start RandomSeed
    End RandomSeed
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++

    Some searching seems to suggest it might be a ram issue? I’m really not sure though, or how to fix it. If you had any suggestions, I’d appreciate it.

    1. Yeah, dying so early seems to mean that OsxAptioFix3Drv failed to create a workable memory layout. This is unusual on a VM however since we should all have the same emulated address space layout.

      Check that you have the required Proxmox version, your “machine” line is correct, and your CPU has the required features (SSE4.1 is most notable). Redownload my Clover image just in case.

      How much RAM are you giving the VM?

  13. Great set of instructions! Thank you for taking the time.

    2 questions / problems that I’m having if you can help.

    1. Do you need to set the OVMF resolution at boot-up everytime or is there a way to make this configuration permanent?
    – I’m able to set it to 1024×768 and press reset to avoid scrambled display but I need to do this every time starting the VM. Can this be set?
    – Also is this is the only way to increase resolution beyond 1024×768?

    2. I’m experiecning a VM lock-up / hang many times after the VM has been running for a bit. No crash but a complete lock with no mouse/keyboard input possible. Any ideas?

    Thanks again!

    1. Make sure you have added the EFI disk to allow it to store the UEFI settings permanently.

      Yes, to increase screen resolution further, you need to use Clover Configurator to set your Clover GUI response higher, then set UEFI resolution to match.

      Not sure on those lock-ups, sorry, unless it’s dying when it goes into sleep mode (disable sleep in power management settings)

  14. I’m having the same issue getting stuck after “End RandomSeed”. I have the most recent version of Clover that you had attached, with a fresh install of Proxmox 5.2. I have it configured for 64G RAM and dual 6 core CPUs (running as sole guest on a dual 6 core xeon machine). I’ve checked and my cpus support SSE4.1. Any ideas? – desperate to get this working!

    VM Config:
    args: -device isa-applesmc,osk=”redacted:)” -smbios type=2 -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check
    balloon: 0
    bios: ovmf
    boot: cdn
    bootdisk: ide2
    cores: 6
    cpu: Penryn
    efidisk0: local-lvm:vm-100-disk-2,size=128K
    ide0: local:iso/Mojave.iso,media=cdrom,size=6G
    ide2: local:iso/clover-r4674-amd64.iso,cache=unsafe
    machine: pc-q35-2.11
    memory: 65536
    name: macServer
    net0: e1000-82545em=42:A0:CB:B1:EA:34,bridge=vmbr0
    numa: 0
    ostype: other
    sata0: local-lvm:vm-100-disk-1,size=250G
    scsihw: virtio-scsi-pci
    smbios1: uuid=0a1a565e-f14d-4212-8b15-5b2d89b48234
    sockets: 2
    vga: std

    1. Try passing through a different core count (like 4), it doesn’t seem to like some combinations (probably something that could be fixed by changing the CPU ID that Clover reports).

      Make sure you’ve installed the patched firmware deb into Proxmox.

  15. Has anyone noticed that the os x guest doesn’t appear to fully utilize the underlaying hardware? In my case when I look at my guest CPU utilization while performing an intensive task (video encoding for example) the guest appears to be utilizing 100% CPU. During the same time when I look at the host utilization in proxmox it appears to be lower. Its hard to see for certain. This is a single guest on the host.

    1. You’re probably just seeing the difference in the way that CPU usage is reported. macOS calls one core being fully saturated “100%” usage, but with a 4 core guest, Proxmox would call that only 25% usage.

      I can happily use “98% of 32 CPUs” as reported by Proxmox when running a CPU benchmark in the guest.

  16. Hi,

    Many thanks for this amazing how to ! I was able to have a machine up and running in no time !

    I entended to use this VM as a MacOS server cache, and time machine backup. But, I’m not able to activate the cache content (for iCloud and so) in preference/sharing…

    Do you have any ideas with is it not working ? I didn’t find any clues on internet

    Thomas.

    1. I tried activating it from the command line, and it shows a proper error message:

      $ sudo AssetCacheManagerUtil activate
      2018-10-25 20:47:39.911 AssetCacheManagerUtil[37766:1427282] Failed to activate content caching: Error Domain=ACSMErrorDomain Code=5 “virtual machine” UserInfo={NSLocalizedDescription=virtual machine}

      Looks like it refuses to enable the caching if it detects you’re running under a virtual machine, very curious.

      It’s possible that you can avoid having the VM detected by macOS by setting “vmware-cpuid-freq=off” in the args (instead of “on”) and “kvm=off”. However in this case the timing in the guest will be off (you’ll probably notice window animations playing at the wrong speed and the realtime clock will drift etc), so it might only be useful for non-interactive usage.

      1. Hum,

        Thanks for the quick reply.

        I tried with kvm=off and vmware-cpuid-freq with no success, same error !

        Maybe I can do something with Clover ? FakeSMC or something

  17. Hi,

    For me, no booting from clover ISO :(.
    Proxmox 5.2, Installing the fixed OVMF.

    I used my Mojave.iso and Clover.iso to build a VM in virtual box on one iMac and Ubuntu hosts, so I think is not the ISO files. I don’t know where is my mistake. I also tried with this clover, but no boot either.

    thanks

      1. No Clover menu and i test without media=cdrom like this :
        ide0: local:iso/10.14_Mojave.iso,size=8000M
        ide2: local:iso/Clover.iso,cache=unsafe,size=13050K
        But Shell EFI is the only one.

        Thanks for the help

          1. Still a Shell EFI, how I can check if your fixed OVMF is really installed maybe I have some errors here…
            Because when I change the resolution in the bios, and reset. (i try to remake and re install)
            When I reboot is the default settings getting back. Anyway, my main problem is no boot from clover…
            Is your CD/HDD is IDE or SATA ? and witch numbers ?

            Thanks for your help.

          2. On Proxmox, run dpkg -l pve-edk2-firmware. You need to see 1.20180612-1, and not 1.20181023-1, which is a newer version from Proxmox that I haven’t released a patch for yet.

            Make sure you’ve added an “EFI Disk” to your virtual machine, because it’s needed to remember your screen resolution settings.

            IDE and SATA both work, but use what the tutorial suggests, because that’s had more testing.

          3. Yes is was the right one :
            pve-edk2-firmware 1.20180612-1

            Args added…
            bios: ovmf
            boot: cd
            bootdisk: ide2
            cores: 2
            cpu: Penryn
            efidisk0: local-lvm:vm-114-disk-1,size=128K
            ide0: local:iso/Mojave.iso,size=8000M,media=cdrom
            ide2: local:iso/Clover.iso,cache=unsafe,size=13050K
            machine: pc-q35-2.11
            memory: 4096
            name: macOS-Mojave
            net0: e1000-82545em=A2:61:00:E7:92:80,bridge=vmbr0
            numa: 0
            ostype: other
            sata0: local-lvm:vm-114-disk-0,cache=unsafe,size=50G
            scsihw: virtio-scsi-pci
            smbios1 uuid …
            sockets: 1
            vga: std

            Hard to find the mistake.
            thanks

          4. Yes it’s beacause I use my clover, so i change to use your clover.iso.
            from :
            ide2: local:iso/clover-r4674-amd64.iso,media=cdrom,size=256M
            to:
            ide2: local:iso/clover-r4674-amd64.iso,cache=unsafe,size=256M
            And after commit save, I used the last menu boot manager to add new value to boot on the disk with clover and after reset it’s a boot !
            I dont kown why my clover is not booting but i think the EFI disk is not saving configs for me.
            Thanks a lot !

  18. Hi Nicholas,

    I was able to set everything up but when I booted the installing from clover it will load the apple symbol and then I will get the crossed circle half way through loading in.

    Did I miss something?

    regards

    Toan

    1. Hit space at the Clover screen and enable the verbose mode so you can see what it’s stuck on. Double check that you installed the required firmware deb package.

      1. Hi Nicholas,

        I think its gets stuck when looking for root device, and I think I installed the right .deb files. I used the one from the link you suggested the pve-edk2_1.20180612-1_all.deb.

        Other then that I’m out of ideas what it might be.

        regards

        Toan

  19. Do not upgrade to 10.14.X (for me it’s 10.14.1) you will lose the access to the disk with the crossed circle half way through loading on boot after install.

      1. I found why, it’s the backup I made do this on the VM.
        And when I restore it’s was working again, but I have scrambled graphics on boot and session…
        Maybe it’s more don’t use backup mode “stop”.

          1. Yes I already try to change it but i have rebuild a fresh one with no backup this time.
            Anyway, did you will make a clover build guide?
            (Since my clover is only boot in virtualbox… and yours is 256M not like me 13M…)
            Thanks a lot for your help this tutorial is very cool ! thanks !

  20. I’m not getting the “Boot macOS Install from Install macOS Mojave” icon in Clover. Nothing shows up when I stop/start after the resolution change it just has the original menu items still.

      1. args: -device isa-applesmc,osk=”…” -smbios type=2 -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check
        bios: ovmf
        boot: cdn
        bootdisk: ide2
        cores: 4
        cpu: Penryn
        efidisk0: local-lvm:vm-108-disk-1,size=128K
        ide0: local:iso/Mojave.iso,media=cdrom,size=6G
        ide2: local:iso/clover-r4674-amd64.iso,cache=unsafe
        keyboard: en-us
        machine: pc-q35-2.11
        memory: 4096
        name: mojave001
        net0: e1000-82545em=2A:B3:33:ED:95:F2,bridge=vmbr0
        numa: 0
        ostype: other
        sata0: local-lvm:vm-108-disk-0,cache=unsafe,size=64G
        scsihw: virtio-scsi-pci
        smbios1: uuid=869fb78e-9f1e-4e62-be96-4ce56eb1db34
        sockets: 1
        vga: std
        vmgenid: ce623c6b-5eb6-489b-9f09-da81d97be6ab

          1. The ISO would have to be pretty malformed to not appear as a boot option, what do you get if you run “file Mojave.iso” from Proxmox’s ISO directory.

  21. root@proxmox:/var/lib/vz/template/iso# file Mojave.iso
    Mojave.iso: Apple Driver Map, blocksize 512, blockcount 12582912, devtype 0, devid 0, driver count 0, contains[@0x200]: Apple Partition Map, map block count 3, start block 1, block count 63, name Apple, type Apple_partition_map, valid, allocated, contains[@0x400]: Apple Partition Map, map block count 3, start block 64, block count 262144, type Apple_Free, contains[@0x600]: Apple Partition Map, map block count 3, start block 262208, block count 12320704, name disk image, type Apple_HFS, valid, allocated, readable, writable, mount at startup

Leave a Reply

Your email address will not be published. Required fields are marked *

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