First, SSH into your Proxmox server so we can make some edits to the configuration files.Įdit /etc/pve/qemu-server/nf (e.g. In the Hardware page for the VM, add a second DVD drive at IDE0, set it to use your Ventura-full.img.ĭon’t try to start the VM just yet. In the Options page for the VM, ensure that “use tablet for pointer” is set to “Yes” (this is the default). Choose VirtIO (paravirtualized) for the network model Set the number of cores for the VM, use a power of two (e.g. Keep a note of your VM’s ID Select the OpenCore ISO you uploaded and set OS type to “Other” Set graphics to “VMWare Compatible”, set BIOS to OVMF (UEFI), set Machine to Q35, tick QEMU Agent, tick Add EFI Disk and pick storage for it. You must untick “pre-enroll keys” Set the size of the hard disk (64GB or greater, 32GB is too small). Make a note of it.Įvery Mac uses the same OSK, so don’t be surprised that it doesn’t look like a random string! Create the VMįrom the Proxmox web UI, create a new virtual machine as shown below. It’ll print out the 64 character OSK for you. Gcc -o smc_read smc_read.c -framework IOKit In a command prompt, change into the same directory as that file and run: xcode-select -install # If you don't already have gcc Save the first block of C code from this page as smc_read.c. You can get around this by reading an authentication key out of your real Mac hardware (the OSK key). MacOS checks that it is running on real Mac hardware, and refuses to boot on third-party hardware. iso file extension, this is actually a hard disk image. Prepare an OpenCore imageĭownload the file from the newest release in my repository (you need v17 or newer), double click it to unpack it, and upload it to Proxmox’s ISO store at /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. Upload this file to your Proxmox’s ISO store directory (typically /var/lib/vz/template/iso). This will a Ventura-full.img file for you. Now in the Terminal, from the root of OSX-KVM, run: cd scripts/ventura On macOS, open up the Terminal and run this command to install the command-line tools: xcode-select -install Just exit out of the install wizard when it says “to set up the installation of macOS 13 Beta, click Continue” and you should be left with an “Install macOS 13 Beta” app in your Applications folder.ĭownload my copy of the OSX-KVM repository using the download button, and unzip it:įirst we need to install some build requirements. Since Ventura is still in closed Developer Beta, you need to opt-in to the Apple beta program and grab Ventura from System Update. Since Ventura is still in Beta and support for it is preliminary in OpenCore, don’t expect full functionality (Beta software makes for a poor daily-driver). Modern AMD CPUs also support AVX2 and should work with this guide. Older CPUs will panic and reboot while trying to boot the installer. Your Proxmox host computer’s CPU must support AVX2 (a new restriction in Ventura), so for Intel your CPU must be at least as new as Haswell. You also need a real Mac available in order to build the installer and fetch the OSK key. I’ll assume you already have Proxmox 7.2 installed. Since Ventura is still in closed Developer Beta, you need to be an Apple Developer and have access to a Mac (or Mac VM) to download it. You can get the full sourcecode of my OpenCore release on my GitHub here. This tutorial for installing macOS 13 Ventura has been adapted for Proxmox from Kholia’s OSX-KVM project and Leoyzen’s OpenCore configuration for KVM. With the public release of macOS 13 Final, this beta guide is now obsolete, please see the new guide here instead Recovering lost GPG public keys from your YubiKey.Installing macOS 12 “Monterey” on Proxmox 7.Expanding the disk of your Proxmox macOS VM.Driving a 4-pin computer PWM fan on the BTT Octopus using Klipper.Installing macOS 13 Ventura Developer Beta on Proxmox 7.2.Installing macOS 13 Ventura on Proxmox 7.2.Fixing Xcode on Monterey under OpenCore Legacy Patcher.The testing continues.the issues will always arise. Our other JAMF server has had to be rolled back to version 10.41 as the new version completely remove the use and functionality of JAMF Remote - which is highly used in our environment. We have had a few Macs already in JAMF give Device Signature errors that can be easily fixed by removed the MDM Profile and re-enrolling and installing the SSL-updated MDM Profile on the Mac. So all seems to work so far with Ventura as it now "trusts" the MDM Profile upon enrollment. Within JAMF you set the Apache Tomcat Settings with the CA and the User Initiated Enrolment and also set the Security for SSL to be "Always" for JAMF version less than 10.42. IIS on the server has a CA assigned to it and the same CA from the server is converted to a pfx for input into JAMF. OK - It seems to be sorted for one of our prod JAMF Servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |