Installing macOS 12 “Monterey” on Proxmox 7

A new version of this tutorial is now available for the release of macOS 13 Ventura, you can see that here

This tutorial for installing macOS 12 Monterey has been adapted for Proxmox from Kholia’s OSX-KVM project and Leoyzen’s OpenCore configuration for KVM. You can get the full sourcecode of my OpenCore release on my GitHub here.


I’ll assume you already have Proxmox 7 installed. You also need a real Mac available in order to fetch the OSK key.

Your Proxmox host computer’s CPU must support SSE 4.2, so for Intel 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 Illegal Instruction crashes when apps/extensions attempt to use these missing instructions.

Modern AMD CPUs also support SSE 4.2 and will work with this guide.

First step: Create an installation ISO

Download my copy of the OSX-KVM repository using the download button, and unzip it:

First we need to install some build requirements. If you will be building the installer ISO on macOS, open up the Terminal and run this command to install the commandline tools:

xcode-select --install

If you’re building the ISO on Linux, you instead need to run this command (these are the package names for Ubuntu or similar distributions, they may need adjustment on other distributions):

sudo apt install qemu-utils make

Now in the Terminal, from the root of OSX-KVM, run:

cd scripts/monterey
make Monterey-recovery.img

This will download the Monterey installer from Apple’s software distribution servers and build a Monterey-recovery.img file for you. Upload this file to your Proxmox’s ISO store directory (typically /var/lib/vz/template/iso). Although we’re putting it in the ISO directory so that we can use it with Proxmox’s ISO picker later, this a raw disk image rather than a true ISO.

If you’re building the installer on macOS, you can build a full installer instead of just a recovery, which will mean that macOS won’t have to download Monterey files during installation, and so won’t require an Internet connection. Simply ask it to build Monterey-full.img instead:

cd scripts/monterey
make Monterey-full.img

This option is not available when building the installer on Linux.

Prepare an OpenCore image

Download the OpenCore.iso.gz file from the newest release in my repository (you want v15 or newer), double click it to 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.

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). Save the first block of C code from this page as smc_read.c. In a command prompt, change into the same directory as that file and run:

xcode-select --install # If you don't already have gcc
gcc -o smc_read smc_read.c -framework IOKit

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 that 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, ensure that “use tablet for pointer” is set to “Yes” (this is the default).

In the Hardware page for the VM, add a second DVD drive at IDE0, set it to use your Monterey-full.img or Monterey-recovery.img.

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 (e.g. with nano or vim). Add this line, being sure to substitute the OSK you extracted earlier into the right place:

args: -device isa-applesmc,osk="THE-OSK-YOU-EXTRACTED-GOES-HERE" -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -global nec-usb-xhci.msi=off -global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off

A USB keyboard is added here because macOS doesn’t support QEMU’s default PS/2 keyboard.

MSI has been disabled for the USB controller to fix QEMU panics when USB 3 devices are passed through.

ACPI PCIe hotplug support needs to be disabled for VMs with passthrough devices since QEMU Q35 machine model 6.1, which is what that final argument does. (You could instead choose Q35 6.0 for your Machine type on the Hardware tab). If you haven’t updated your QEMU to version 6.1 yet then remove this argument from the args. (Proxmox 7 ships with 6.0 and updated to 6.1 later on)

Ensure the args are all on a single line!

We also need to add a -cpu argument. If your host CPU is Intel, add this to the end of the “args” line:

-cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc

This will pass through all of the features that your CPU supports. OpenCore’s config will pretend to macOS that the CPU’s model name is Penryn for compatibility.

If your host CPU is AMD, or the above argument doesn’t work for you, use this more-compatible alternative:

-cpu Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check

This pretends that your CPU is Penryn, which will keep macOS happy even if your host CPU is AMD, and adds a bunch of newer required and optional CPU features on top. Features that your host CPU doesn’t support will be ignored (a warning will be printed to the console during launch with qm start 1xx), but note that macOS won’t work without SSE4.2 support.

You can remove the “+invtsc” feature from the list if your CPU doesn’t support it, or if you want to be able to migrate a running VM between Proxmox nodes.

Now find the lines that define the two “ISOs” (ide0 and ide2), and remove the “,media=cdrom” part from them. Add “,cache=unsafe” in its place. This will treat these as hard disks rather than DVD drives.

Save your changes, return to the Options tab, and change the boot order to put IDE2 (the OpenCore image) first. Your final VM configuration file should resemble this:

args: -device isa-applesmc,osk="..." -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc -global nec-usb-xhci.msi=off -global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off
agent: 1
balloon: 0
bios: ovmf
boot: order=ide2
cores: 4
cpu: Penryn
efidisk0: vms-ssd-enc:vm-171-disk-1,efitype=4m,size=1M
ide0: isos:iso/Monterey-full.img,cache=unsafe,size=14G
ide2: isos:iso/OpenCore-v15.img,cache=unsafe,size=150M
machine: q35
memory: 4096
name: macos-monterey
net0: virtio=...,bridge=vmbr0,firewall=1
numa: 1
ostype: other
virtio0: vms:vm-171-disk-0,cache=unsafe,discard=on,size=64G
scsihw: virtio-scsi-pci
smbios1: uuid=...
sockets: 1
vga: vmware

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

Install Monterey

Now start up your VM, it should boot to the OpenCore boot picker:

Press enter to boot the “Install macOS Monterey” entry and the installer should appear. (If your keyboard isn’t working, leave the Proxmox Console page and re-enter it)

OpenCore’s “OpenCanopy” boot picker

If you built a recovery installer, the icon will instead be an image of a hard disk and be labelled “MacOS Base System”.

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 you can quit Disk Utility from the top menu (Disk Utility > Quit Disk Utility), and we’re ready to begin installation!

After the first stage of installation, the VM will reboot 2 or 3 times in quick succession, and each time you must manually pick the “macOS Installer” entry (the second one here, with the hard disk icon) to continue installation. It will not be selected for you automatically:

If your keyboard isn’t responding on this screen, exit the Console tab in Proxmox and re-enter it. If you get a “prohibited” sign like this appearing, hit the Reset button on the VM to try again:

Now the installation is nearly complete and the macOS Installer entry disappears, so pick the name of your main disk to boot (mine’s called Main).

There’s just one more reboot to come. Afterwards pick the “Main” entry again and this time you’ll finally boot into Monterey!

Answer the initial install questions, and you’ll be logged on! Note that you will want to hold off on logging into your Apple ID until you’ve configured your Mac’s serial number in OpenCore (because otherwise a Mac with the default shared serial number in my OpenCore image will be added to your Apple ID).

It works!

Note that it will be really sluggish for a few minutes after the first boot while the system performs housekeeping tasks.

Make the OpenCore install permanent

We’re currently booting using OpenCore from the attached OpenCore ISO. 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 OpenCore CD and overwrite the EFI partition on the hard disk. The OpenCore CD is the small disk (~150MB) that only has an EFI partition on it, and the main hard disk is the one with the large (>30GB) 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” (note that if you get these names wrong, you will overwrite the wrong disk and you’ll have to start the installation over again!).

Now shut down the VM, and remove both the OpenCore and the Monterey installer drives from the Hardware tab. On the Options tab, edit the boot order to place your virtio0 disk as the first disk. Boot up. If everything went well, you should see the OpenCore boot menu, and you can select your “Main” disk to boot Monterey:

Sleep management

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

qm monitor YOUR-VM-ID-HERE 

Editing your OpenCore/EFI settings

The Configuration.pdf that explains the OpenCore config.plist file can be found along with the OpenCore release on my GitHub.

To mount your EFI partition in macOS so you can edit your config.plist, first check the “identifier” of your EFI partition in the terminal:

~$ diskutil list
/dev/disk0 (external, physical):
   #:                   TYPE NAME              SIZE       IDENTIFIER
   0:  GUID_partition_scheme                  *512.1 GB   disk0
   1:                    EFI EFI               209.7 MB   disk0s1
   2:             Apple_APFS Container disk1   511.9 GB   disk0s2

Then you can mount it like so:

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

Now you can edit /Volumes/EFI/OC/config.plist with your favourite text editor to make your changes. (TextEdit is not a great choice because it likes to insert curly quotes into the file and otherwise break things, there are some dedicated plist editors available such as XCode).

If you’re unable to boot macOS, you can edit the config.plist using the “UEFI Shell” option in the OpenCore boot menu instead.

Enter “FS0:” and press enter to open up the first available filesystem, then run “edit EFI\OC\config.plist” (if the file isn’t found, try switching to another filesystem like fs1:). When you’re done editing, press control+Q to exit, “Y” to save, then run “exit” to return to the OpenCore menu. You need to reboot for your changes to take effect.

If you prefer, you can edit config.plist from the comfort of your Proxmox host instead. If you’re booting from an attached OpenCore.img file, you can mount that file as a disk on the host. If you’re booting from the VM’s disk instead, it must be in raw format in order to be mounted (e.g. typical LVM or ZFS usage) rather than qcow2.

# Mount an OpenCore image:
losetup --partscan /dev/loop0 /var/lib/vz/template/iso/OpenCore-v15.img
# or a VM boot disk:
losetup --partscan /dev/loop0 /dev/zvol/tank/vms/vm-100-disk-1

mount /dev/loop0p1 /mnt

Now the contents of that first partition are available in /mnt, so you can edit /mnt/EFI/OC/config.plist in your favourite editor. When you’re done, do this to unmount the disk:

umount /mnt
losetup --detach /dev/loop0

Automatic boot

In config.plist, you can set Misc/Boot/Timeout to a non-zero value to allow the default boot option be chosen automatically after that delay in seconds. I’ve disabled this by default because it causes the installer ISO to re-enter its main menu instead of continuing the second stage of installation.

You can set the default boot option by pressing control+enter on it.

Verbose boot

To boot macOS in Verbose mode to diagnose boot problems, at the OpenCore boot menu press Cmd+V before pressing enter to boot macOS (you don’t need to hold it down).

If there is a kernel panic during boot and it reboots too quickly to be read, edit config.plist to add “debug=0x100” to the kernel arguments.

Changing screen resolution

To change macOS’ screen resolution, you need to edit the UEFI/Output/Resolution setting in config.plist, the default is 1920×1080@32.

You should be able to change this to any of the modes that the system OVMF menu offers (hit F2 at the start of guest boot and choose “Device Manager/OVMF Platform Configuration” to see which resolutions are available).

Video performance

Because there is no guest video acceleration available for macOS, video performance is poor.

In Google Chrome in the guest you will need to toggle off the setting to “use hardware acceleration when available” to improve issues with elements not being drawn or flickering (especially video). Safari may be a better choice.

macOS’s built in “Screen Sharing” feature offers dramatically better framerates and latency than Proxmox’s browser-based VNC console, so if you have a real Mac to act as a viewing console, you can enable that in the VM’s “Sharing” settings and connect to the VM using the Screen Sharing app from your Mac instead:

Apparently Screen Sharing is also compatible with VNC clients like RealVNC, so you should be able to connect to it from Linux or Windows consoles using RealVNC.

The real magic bullet for video performance is to pass through a compatible video card using PCIe passthrough (though note that macOS now only supports a handful of very old NVidia cards). This offers near-native performance. You can read more about how I’m using PCIe passthrough on my own installation here.

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. You need to reboot 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, which gives much better compatibility.

Odd core counts

If your host CPU is AMD, you might have a core count which is divisible by 3, like 6 cores. macOS doesn’t like it if the core count isn’t a power of 2 (1, 2, 4, 8), but it doesn’t mind odd socket counts.

So in order to pass 6 total cores, configure the VM for 3 sockets and 2 cores per socket.

Fixing “guest boots to UEFI shell”

If your guest ends up booting to the UEFI shell instead of showing the OpenCore boot menu, especially if you’ve just updated OpenCore to a new version, you’ll need to edit the guest’s UEFI boot entries to fix this.

At the very start of guest boot, hit F2 to enter guest UEFI settings.

First we’ll remove the old entries. Choose the Boot Maintenance option, then Boot Options -> Delete Boot Option. Use the spacebar to tick any old Clover or OpenCore entries (avoid ticking the EFI Internal Shell option, you want to keep that!). Select “Commit Changes and Exit”.

Now we’ll add the correct entry for OpenCore back in. Select Add Boot Option. Navigate through the device tree to EFI/OC/OpenCore.efi and select it, name this new option “OpenCore” or similar. Again Commit Changes and Exit.

Go to the Change Boot Order and move OpenCore to the top. Commit Changes and Exit.

Now back out to the main menu and choose Reset, and you should successfully boot into OpenCore this time.

Fixing iMessage

iCloud and the App Store should already be working for you, but for iMessage support you must follow these steps to mark your network adapter as built-in:

Disabling SIP (System Integrity Protection)

You can disable SIP by selecting the Recovery option from the OpenCore boot menu, then use the top menu to open the Terminal and run csrutil disable --no-internal. Then reboot.

This may be needed to run unsigned kexts or perform other hacks.

Upgrading OpenCore

Sometimes you need to update OpenCore to a new release in order to support a new macOS update. I’ll assume you don’t have any customisations to config.plist you want to save.

First take a snapshot! It’s great to be able to roll back if something goes wrong.

If you’re still able to boot macOS, you can update it from within the guest. Follow the instructions in the “Editing your OpenCore/EFI settings” section to mount your EFI partition. Then you can delete the EFI folder in there and replace it with the one from the file from my OpenCore release (you’ll probably need to empty the trash first to make room for the new folder). You’re done!

If you aren’t able to boot macOS, unpack and upload the new OpenCore ISO to Proxmox’s ISO store instead. Add a new CD drive to the VM that uses that ISO. Then in Proxmox’s terminal edit the VM’s config (in /etc/pve/qemu-server) to replace “media=cdrom” with “cache=unsafe” for the OpenCore drive. Now on the “Options” tab, change the boot order to put the new OpenCore drive first.

Start the VM and boot into macOS using the new OpenCore drive. From within macOS you can now follow the instructions from the “Make the OpenCore install permanent” section to install the new OpenCore image to your main macOS disk, after which the OpenCore drive can be detached from the VM.

Upgrading from macOS Big Sur

First make a backup or snapshot of your system! Being able to roll back when the upgrade goes wrong is a real lifesaver.

You’ll need to update OpenCore to my v15 release before the upgrade. You can follow the instructions in the “Editing your OpenCore settings” section above to mount your EFI disk. Then you can replace the OpenCore files in the mounted “EFI” disk with the ones from the file in my newest OpenCore release.

Reboot to make sure that you can still boot Big Sir.

If you’re using any PCIe passthrough devices (particularly video cards) you’ll want to disable those and set “vga: vmware” instead, so you can install using Proxmox’s web console from a different machine during the upgrade. This avoids installer problems triggered by flaky video card passthrough, especially host lockups caused by the AMD Reset Bug.

Now you can upgrade to Monterey using Software Update or from the App Store like you would on a real Mac.

If the update fails to appear, your SIP mode might be set to “Apple Internal”. You can check this by running “csrutil status” in the Terminal.

To fix this, reboot your VM and at the OpenCore menu select Recovery. Open up the Terminal, and in there run “csrutil enable --no-internal” (“csrutil disable --no-internal” is fine too), then reboot back into macOS and try again.

772 thoughts on “Installing macOS 12 “Monterey” on Proxmox 7”

  1. Hi Nicholas,

    Thank you for creating this guide. I’ve come from some success hackintoshing a few laptops with opencore but when I found this post I’ve been so glued to it.

    I’m attempting to passthrough a couple pcie devices. A half height MSI RX 560 4GB GPU and a WD Black SN 750 M.2 NVMe SSD. Both of which should be compatible according to the dortania guides. I verified IOMMU is enabled, added this to my /etc/default/grub file
    GRUB_CMDLINE_LINUX_DEFAULT=”quiet intel_iommu=on pcie_acs_override=downstream,multifunction video=efifb:off” rootdelay=10″
    blacklisted the radeon, nouveau, nvidia drivers,
    added the vfio, vfio_iommu_type1, vfio_pci, vfio_virqfd modules. Lastly I added the vendor and device IDs to the /etc/modprobe.d/vfio.conf file. Then I rebooted.

    So for the NVMe ssd, MacOS doesn’t see it when i’m in recovery mode using disk utility. Do I need to modify the opencore config.plist file to get this seen by macos?

    Then my GPU, when I pass it through, I stuck at the apple boot screen, the loading bar does not complete. I get the monterey background on my external display and in the console display I see that apple logo with a partially loaded bar. It never completes or fully boots into the OS. Is that another case where I need to edit the Opencore config.plist?

    Thank you for your guidance so far.

    1. You shouldn’t need to edit the opencore config to have the NVMe SSD work, show your VM’s config maybe. Sometimes in the installer you need to tick “show all devices” for drives to appear.

      Also check “dmesg” for passthrough errors, particularly “BAR” errors.

      You need to disable the emulated VGA adapter on the hardware tab (disabling the console) for macOS to boot.

      Is that the primary GPU in your machine? There are extra considerations for GPUs which are set as your primary display in your host UEFI settings.

      1. Thank you for the quick reply and guidance! I tried my best to look around the internet for solutions but my searches kept coming back to you. In the macos recovery env with disk utility I did select that drop down to view all devices and didn’t see nvme ssd.

        I did a dmesg | grep -iC 3 “BAR on the server but didn’t see any errors. I did find this block of errors when I was looking through dmesg alone

        [68005.297036] pcieport 0000:00:1d.0: DPC: containment event, status:0x1f11 source:0x0000
        [68005.297040] pcieport 0000:00:1d.0: DPC: unmasked uncorrectable error detected
        [68005.297047] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Receiver ID)
        [68005.297051] pcieport 0000:00:1d.0: device [8086:a330] error status/mask=00200000/00010000
        [68005.297053] pcieport 0000:00:1d.0: [21] ACSViol (First)
        [68006.558091] vfio-pci 0000:04:00.0: not ready 1023ms after FLR; waiting
        [68007.614078] vfio-pci 0000:04:00.0: not ready 2047ms after FLR; waiting
        [68009.918088] vfio-pci 0000:04:00.0: not ready 4095ms after FLR; waiting
        [68014.270117] vfio-pci 0000:04:00.0: not ready 8191ms after FLR; waiting
        [68022.718128] vfio-pci 0000:04:00.0: not ready 16383ms after FLR; waiting
        [68040.382201] vfio-pci 0000:04:00.0: not ready 32767ms after FLR; waiting
        [68075.198306] vfio-pci 0000:04:00.0: not ready 65535ms after FLR; giving up

        When I disable vga: none, there isn’t any output on the display at all so I can’t really tell what is going on. So in my config I still have it on, thought I would keep it on while troubleshooting but I didn’t realize it needed to be set to none in order to boot.

        My CPU does have integrated graphics but I did notice that once I installed the GPU when I plug in the HDMI cable into the GPU during proxmox boot I see proxmox booting and its on the display. The motherboard hdmi then doesn’t have any output for proxmox anymore when the GPU is installe din the system. I have a Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz.

        this is my 100.conf file
        agent: 1
        args: -device isa-applesmc,osk=”beepbeep” -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -global nec-usb-xhci.msi=off -global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off -cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc
        bios: ovmf
        boot: order=ide2;ide0;net0;hostpci0
        cores: 4
        cpu: Penryn
        hostpci0: 0000:00:14.3
        hostpci1: 0000:04:00,pcie=1
        ide0: local:iso/Monterey-recovery.img,cache=unsafe,size=3144712K
        ide2: local:iso/OpenCore-v17.iso,backup=0,cache=unsafe,discard=on,size=150M
        machine: q35
        memory: 12288
        meta: creation-qemu=6.2.0,ctime=1664126085
        name: nix-macos-monterey
        net0: virtio=32:65:A0:A5:CD:26,bridge=vmbr0,firewall=1
        numa: 0
        ostype: other
        scsihw: virtio-scsi-pci
        smbios1: uuid=12df11e8-086e-481b-9d8f-b592109ded39
        sockets: 1
        unused0: Sung850SSD:vm-100-disk-2
        unused1: Sung850SSD:vm-100-disk-1
        vga: vmware
        virtio1: Sung850SSD:vm-100-disk-0,cache=unsafe,discard=on,size=450G
        vmgenid: 2014d8d9-5533-48e7-b151-4f925d561720

        Thank you!

        1. In your host UEFI settings check if you have an option for selecting integrated or PCIe graphics as primary, selecting integrated will likely fix things for you.

          Is 04:00 your GPU? If so those error messages are a failure for the host to reset the card, i.e. the AMD Reset Bug. For cards affected by this bug, and if they’re a secondary GPU, it’s possible for it to be used a single time per host power cycle, if you can avoid the host initializing it at all.

          To do better than that you can try adding vendor-reset: . Vendor reset did not fix my RX580, so I can only use it a single time per host power cycle.

          1. Wow, this is super slick! It is truly a beaut! The setting that fixed my setup was going into the host UEFI settings and selecting the integrated graphics as the primary.

            This makes the mac so much more usable for me. I don’t think my card has the AMD reset bug. My RX 560 seems to come back after multiple reboots. So maybe i’m in the clear there.

            Now I just have to try to get the WD SN 750 passed through.

              1. It turned out for my specific case with the WD SN750 1TB NVMe drive not showing up in macos that it was the drive. I plugged in a WDSN750 SE 512 GB and it showed up right away, same with a Samsung NVMe 970 pro that I had as well, both showed up with the default open ore config.

  2. Hi Nick,
    I must start by taking my hat off. You da Man! Thanks for your dedication to us mere mortals.
    This is my first time attempting this, I followed every step and start over multiple times yet I continue to deal with the same issue. When I start the VM for the first time it goes to OpenCore as it should, I click on the macOS Base System Icon, I get the Apple logo and then it just stays there, stuck, with no sign of progress.
    This is my hardware:
    – ASUS ROG Strix gaming B-450
    – Ryzen 3 2200G (will soon upgrade)
    -16 GB 3200Hz RAM
    – 256 GB SATA SSD (100% dedicated to this project, my main storage is a 500 GB m.2)
    This is the VM config:
    GNU nano 5.4 /etc/pve/qemu-server/100.conf
    args: -device isa-applesmc,osk=”famouswordsby(c)AppleComputerInc” -smbios type=2 -de>
    balloon: 0
    bios: ovmf
    boot: order=virtio0;ide2;net0;ide0
    cores: 4
    efidisk0: local-lvm:vm-100-disk-0,efitype=4m,size=4M
    ide0: local:iso/Monterey-recovery.img,cache=unsafe,size=3144712K
    ide2: local:iso/OpenCore-v17.iso,cache=unsafe,size=150M
    machine: q35
    memory: 12288
    meta: creation-qemu=6.2.0,ctime=1665270880
    name: Monterey
    net0: virtio=A6:EE:3D:7E:BB:A1,bridge=vmbr0,firewall=1
    numa: 1
    ostype: other
    scsihw: virtio-scsi-pci
    smbios1: uuid=ec0e035c-fc87-44fa-8a3c-46a3a02c1229
    sockets: 1
    vga: vmware
    virtio0: local-lvm:vm-100-disk-1,size=150G
    vmgenid: ee4bc387-ebac-40fe-9ba7-468105c81cc3

    I’m really hoping that its some simple solution. Much thanks in advance for your time and attention.

    1. That’s an unusual failure! Config looks correct. Press Cmd/Win+V before selecting the Base System option to enable Verbose Boot, and the log that produces could reveal a cause.

  3. Is there a way to connect the iPad to the macOS through Proxmox?
    I tried using the usb passthrough section but it didn’t work.

    1. It seems that for the iDevices you need to PCIe-passthrough an entire USB controller instead of using USB device passthrough.

      1. Is there a way to virtualize the usb controller in Proxmox?
        I’m asking because on my Windows PC, I have installed VMWare which uses an USB Controller to hot plug from your host to the VM any USB device.

        1. Proxmox’s USB device passthrough doesn’t work with iDevices, so the best option is to PCIe passthrough the USB controller instead.

  4. Is there a way to increase the graphics memory from 7 MB to 128 MB?
    I tried in the hardware section to set it but when I start macOS it still shows 7 MB.

    1. You can, but it doesn’t achieve anything except for allowing the use of higher resolution displays. There is no 2D or 3D acceleration capability so it doesn’t get faster at all. The memory is only used to store the framebuffer.

      You need to PCIe-passthrough a compatible GPU to get better graphics performance.

      1. I’m not looking to play games or anything like that.

        I only need it to be able to use the command line and Visual Studio.
        After a few minutes, it’s very laggy when using the terminal. What I mean is I press the up arrow to get a previous command in the terminal and it’s taking up to one second to react.

        1. Changing the video memory will have no impact at all on that. That sounds more like it’s stalling waiting for disk IO

  5. I tried the whole setting in my Proxmox 7.2-7 or 7.2-11, but without a success. When I boot a VM there is no Install macOS option, only only UEFI shell and reset NVRAM. I tried OpenCore-v17.iso and OpenCore-v18.iso. My Proxmoxes runs on Intel platform. My conf is:
    agent: 1
    args: -device isa-applesmc,osk=”secret” -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -global nec-usb-xhci.msi=off -global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off -cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc
    balloon: 0
    bios: ovmf
    boot: order=ide2
    cores: 4
    cpu: Penryn
    efidisk0: local-zfs:vm-401-disk-0,efitype=4m,size=1M
    ide0: local:iso/Monterey-recovery.img,cache=unsafe,size=653763072
    ide2: local:iso/OpenCore-v17.iso,cache=unsafe,size=150M
    machine: pc-q35-6.0
    memory: 4096
    meta: creation-qemu=7.0.0,ctime=1665998872
    name: macOS
    net0: virtio=xxxxxxxxxxx,bridge=vmbr0,firewall=1
    numa: 1
    ostype: other
    scsihw: virtio-scsi-pci
    smbios1: uuid=xxxxxxxxxxxxxxxxxxxx
    sockets: 1
    vga: vmware
    virtio0: local-zfs:vm-401-disk-1,cache=unsafe,discard=on,size=64G
    vmgenid: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

        1. I found the problem part:
          qemu-img convert BaseSystem.dmg -O raw Monterey-recovery.dmg on OracleLinux produced 623MB output
          on Ubuntu 3GB output


      1. 40 x Intel(R) Xeon(R) CPU E5-2666 v3 @ 2.90GHz (2 Sockets)
        Kernel Version Linux 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200)
        PVE Manager Version pve-manager/7.2-3/c743d6c

        GPU: AMD Radeon RX 570 4 Gb.

  6. Hi, I followed the guide, and got macOS installed correctly. However, when I try to do the initial setup, the VM crashes after about 60 seconds, barely enough time to set the region.

    Any ideas on how to fix this?

    1. That would just about have to be a host TSC fault, run “dmesg | grep -i -e tsc -e clocksource” and see if it’s complaining that the TSC is broken and that it’s abandoning it for HPET instead. I don’t know how to fix that one.

  7. Hey Nick! I am having an issue that I might need somebody’s help with.

    So, I had this setup working great on my Proxmox 7 machine before, with no flaws. Unfortunately, my boot drive died on my server and I had to reinstall the OS. No problem I thought, I had the Mac Server all backed up, and it was just a restore away from working again.

    It was not… I have not been able to get it to boot ever since. It gets stuck in the starting stage, and I cannot stop it. It gives me nothing log-wise. I have tried reconfiguring everything just to how you had done so in your guide, with no success. I was using PCI-E passthrough on my old machine, so I thought it might be messing something up, but it got me nowhere.
    Anyways, I’ve been trying everything for about a week, and I am just stumped. Is there anything I can do?

    1. The VM never completes launching?

      Check that you’ve set up the update repo for Proxmox, you might have been using a newer QEMU version before.

      If you start the VM from the Proxmox console like “qm start 100” you can sometimes see more warnings that aren’t logged anywhere else.

      1. Hey Nick! Thanks for your quick response. Correct, yeah it does not complete the start command. I already tried “qm start”, and it just seems to hang. I do have my non subscription repo setup, and my system is all up to date, just as it was before. No idea!

        1. I think you already tried removing all the passthrough devices? Anything printed to dmesg?

          Share your VM config

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.