If no, your issue will be c. By Ive tried host, Penryn, and Haswell-noTSX with no avail. I've made sure all my kexts and drivers are up to date and compatible with the macOS version I'm trying to install. 1 warning generated. Navigate through the device tree to EFI/OC/OpenCore.efi and select it, name this new option OpenCore or similar. Any suggestions on what to look for in the config.plist or elsewhere in my setup would be much appreciated! bogomips : 4802.25 Installed 0.3.1 to USB, has "EFI boot" icon, able to boot into Monterey installation screen, procced to upgrade from Big Sur, the installation will fail at about 13 minutes remaining with error "An error occurred loading the update.". Sorry, I havent attempted this yet. 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. Thanks! 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. Because there is no guest video acceleration available for macOS, video performance is poor. CPU op-mode(s): 32-bit, 64-bit Metal 3 is just an API feature set, and is actually limited to newer GPUs only: Currently Apple has removed the following drivers: They will need to be reinjected to resolve USB 1.1 support for pre-Ivy Bridge units. AMD Navi Graphics Cards are still currently unsupported. The RAM disk is located under the SharedSupport.dmg: Early research notes attached with regards to Ventura acceleration: With regards to the introduction to Metal 3, this has little effect on us. power management: Any thoughts what I should set for the -cpu flags? That did the trick for me as well. However as Ventura has changed much of the patcher landscape for us, there's still some critical issues we'll need to work through to get the current patcher working. const mach_port_t kIOMasterPortDefault Apple earlier today released new Rapid Security Response updates for iOS 16.5.1, iPadOS 16.5.1, and macOS Ventura 13.4.1 users, but Apple has pulled the software, likely due to an issue that . I used a pcie to an Apple Native Card brcm94360 (which works perfectly on my other Hackintosh). memory: 4096 Hi there, Im having the exact same issue when passing through a GPU. Downgrading IOPlatformPluginFamily.kext does not seem to resolve, further research required. All have failed. Information below is now for reference purposes. Oddly enough the thunderbolt 3 functions of the card work in the guest. Apple Provides Instructions to Fix macOS Reinstallation - MacRumors If not you might be on an older kernel version. initial apicid : 121 I've researched and worked through many potential solutions but have reached a point where I could use some guidance. An error occurred preparing the software update when installing hackintosh on Asrock A320M By Build For Dev, April 10 in Desktop Reply to this topic Start new topic Build For Dev Members 5 Posted April 10 has anyone experienced the same thing? An error occured preparing the software update Hey I just tried to update my macOS yesterday from Majove to Big Sur. You also need a real Mac available in order to fetch the OSK key. Boot your Mac normally. It just references general guides and isnt specific. Vulnerability Itlb multihit: Not affected My current proxmox configs work for Windows VM passthrough no problem, but nothing ive tried works for MacOS Ventura. Monterey Installer app fails preparing installation At the very start of guest boot, hit F2 to enter guest UEFI settings. qemu-img convert BaseSystem.dmg -O raw Ventura-recovery.dmg 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 instead (mines called Main). Intel Ivy Bridge, Haswell, Broadwell, Skylake. same. typical LVM or ZFS usage) rather than qcow2. Then I suppose this guide is not for me. [ 5] 6.00-7.00 sec 3.17 GBytes 27.3 Gbits/sec Error_7E7AEE96CA I viewed a discussion here in community that was suggested download a update combo for solve this issue, but I downloaded it, and tried install the update combo on my mac, but unfortunately this not working for me, I receive a message that the disk cannot receive that update. Will try 0.8.6. When i boot (first time) I dont get colored install macOS Ventura but rather gray disk image with macOS Base System. I have to reboot the host in between uses of my RX 580. My qemu config is pretty much identical to your examples but have tried with/without passing the AMD rom file. agent: 1 I've tried to upgrade from Catalina. I have keep searching for some help but no luck. L3 cache: 16 MiB Issue has been resolved. Ive put the -D in the arguments but the log file doesnt say whats failing. I tried switching gpu to the 2nd slot, same. However the guest is eventually up, I can remote into it just fine. Dec 11 20:18:29 Kevins-iMac powerd[44]: Assertion Released. Hi Nick, do you have a specifics of your exact setup for your RX 580 passthrough in Proxmox 7? Modern AMD CPUs also support AVX2 and should work with this guide. Download complete! 2. Yeh my host is using the iGPU and Ive blacklisted my other 2 GPUs appropriately. Check if your Mac supports Monterey / Ventura 2. Delete or back up your data and check if you can update your Mac. Host is ASRock Z790m-ITX, i3-13100, 64GB DDR5. On-line CPU(s) list: 0-11 2. macOS doesnt like it if the core count isnt a power of 2 (1, 2, 4, 8), but it doesnt mind odd socket counts. But I am still getting the same error message "an error occurred loading the update." I did hear someone say that only passing the GPU device (and not ticking the All Functions box to pass the HDMI audio too) made vendor-reset work for them. The new QEMU 8 would have introduced a version 8 machine model too. I doubt youll be able to boot macOS with no monitor plugged into the guest GPU, the GPUs refuse to accelerate when no monitor is present. scsihw: virtio-scsi-single Now instead, developers are required to download and install the Kernel Debug Kit from Apple's Developer Site anytime they wish to create a new Boot and System Kernel Collection. You need to reboot for your changes to take effect. As mentioned in the above posts, the discontinuation of OS support for the MacPro6,1 has meant Apple is no longer required to support pre-AVX2.0 binaries. Additionally Kernel Debug Kits are per-build specific, as using an older build will mean using older kernels, etc. Shut down Mac and wait a second 3. If this GPU is your hosts boot GPU then yes, youll need to supply a vBIOS or otherwise the guest wont be able to init it. If an error occurred while updating or installing macOS The message might say that an error occurred while downloading, preparing, or installing, or that the installer is damaged or could not be verified. My config has nothing special in it, just straight old passthrough and it works, I have config file details here: https://www.nicksherlock.com/2018/11/my-macos-vm-proxmox-setup/. I dont know how third-parties have built their installer images, if you use an image not built using the instructions in my tutorial youll have to ask them. Use sudo dd if= of= to copy the EFI partition from the OpenCore CD and overwrite the EFI partition on the hard disk. Thanks for the information. You can look up the memory address range from the BAR error in the output of cat /proc/iomem to discover which host driver is causing the problem. [ 5] 1.00-2.00 sec 8.18 GBytes 70.3 Gbits/sec 0 3.07 MBytes With Ventura, our _cs_require_lv patch broke which we rely on to pass our shim'd binaries as allowable in macOS under their security policy. Nick- Thank you for all of the excellent work on this and your earlier macOS Proxmox Hackintosh tutorials. Note: Your post will require moderator approval before it will be visible. We will be researching more, however, for the initial beta cycle, we expect to require KDKs to be installed by the end-user before running. Machine Model iMac15,1 Application Version Latest Release Application Variant GUI (Graphical User Interface) Have you verified whether this issue has been opened before? Vendor ID: AuthenticAMD Has the recovery image been flagged or something or has something changed since Sonoma was released? In a command prompt, change into the same directory as that file and run: Itll print out the 64 character OSK for you. As mentioned above, Ventura no longer ships with a non-AVX2.0 dyld shared cache on Intel. Look below at the models that will be eligible to install Ventura: hi, Nick. Join the conversation. I saw one of your posts about (un)binding in the hookscript and Ive even tried that. BlueToolFixup.kext vga: vmware cpu: Haswell GPU: RX 570 We read every piece of feedback, and take your input very seriously. 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). its been one month and the issue still there. What to do if your Ventura update is stuck Can't update your Mac? Do you see the Proxmox boot logo on the guest screen during boot? Ive tried flashing several different ROMs, including ones that were supposedly known to work with Macs. Then in Proxmoxs terminal edit the VMs config (in /etc/pve/qemu-server) to replace media=cdrom with cache=unsafe for the OpenCore drive. Note: The total download size is 675.56 MB The q35 version didnt seem to have any impact. Hello everyone,I've been trying to install macOS Ventura on my Dell T3500 using OpenCore, but I'm running into some problems. You can remove the +invtsc feature from the -cpu list if your CPU doesnt support it, or if you want to be able to migrate a running VM between Proxmox nodes. However, after restarting and launching "Install macOS", it's getting rebooting loop without any process. Downloading 002-75524 You can also pass through USB devices by passing through an entire USB controller using Proxmoxs PCIe passthrough feature, which gives much better compatibility. The text was updated successfully, but these errors were encountered: As you have read in the OP, a cryptex contains the dyld shared cache and other smaller parts of userspace. Tried with both a Ventura and Monterey install (full and recovery image) and different versions of opencore. Under v8.0-3 I tried various versions of Opencore but they didnt seem to be a problem as I could get restored VM that I had previously backed up to work just not the working version I had when I upgraded Proxmox. Maybe you could help? [ 5] local 192.168.99.15 port 49764 connected to 192.168.99.2 port 5201 Apple Footer. Mac: An Error Occurred Preparing the Software Update to your account, Using the latest release 0.3.1 because after installing nightly build 0.3.2 to USB, there is no "EFI boot" icon when holding [option] key on startup. This is usually because the host has already trashed the shadow copy of the cards vBIOS in memory by using it to init the card during its own boot. Now find the lines that define the two ISOs (ide0 and ide2), and remove the ,media=cdrom part from them. It is more strange, because on this mac I had the . As expected, Apple has also removed graphics support for Haswell through Skylake as well as GCN1 through 3. Required fields are marked *. Ventura now requires that your CPU has support for AVX2, so for Intel your CPU would have to be at least as new as Haswell. If you have an account, sign in now to post with your account. CPU max MHz: 3200.0000 Get your hand on an external drive (ideally, an SSD). so the only problem now is the wifi-card to the Ventura. Step 3: To manage the usage, click on the Manage option. It works fine on a Win X vm. The main affected units would be all discontinued Mac Pros, as they can no longer use socketed cards or eGPUs to retain native graphics acceleration. If it possible to emulate M1 or M2 on Proxmox ? Thus to disable Library Validation and AMFI in general, you'll need: We will be researching what other patches can be used in the future to alleviate this. Nope, not getting any BAR errors when booting. Dell T3500 - Bloomfield. It requires a custom vBIOS so that OVMF can init the iGPU for macOS: People report stability problems after install, though. [ 5] 0.00-1.00 sec 8.10 GBytes 69.6 Gbits/sec 0 3.07 MBytes If this happens again you may need to manually enter the efi and point it in the right direction. Mac15,1 5K - "An error occurred loading the update." when - GitHub guest hangs only if I dont explicitly define the romfile in the hostpci0 line. macOS Ventura and OpenCore Legacy Patcher Support, Extracting the non-AVX2.0 dyld shared cache, https://github.com/khronokernel/khronokernel.github.io/blob/legacy-metal/_posts/2022-08-01-2022-LEGACY-METAL.md, Ventura Boot Issues with certain GPU/Firmware combinations, Additional notes by Syncretic regarding AVX1.0 and 2.0 in Ventura, recent success of graphics acceleration on macOS Ventura, Legacy Metal Graphics Support and macOS Ventura, sys_patch: Allow KDK-less root patching on Intel iGPUs and Nvidia Kepler, 2013 Mac Pro and macOS Ventura Boot Issues, macOS Ventura 13 bootloop (Library not loaded: /usr/lib/libSystem.B.dylib), vmware workstaton pro 16.2.3 macOS Ventura beta and it's stuck in a reboot loop. https://www.techpowerup.com/vgabios/208710/sapphire-rx580-8192-180719. Click "Details" beneath "This Mac is enrolled in the Apple Beta Software Program." Tap "Restore Defaults." After leaving the beta program, you can retry installing macOS Ventura or another version in Software Update. With Ventura, AMFI can no longer be disabled in Safe Mode, as well when CSR_ALLOW_UNTRUSTED_KEXTS is not toggled (we assume this is related to DriverKit). OpenCore Legacy Patcher - MacUpdate How to fix macOS Big sur an error occurred applying the software update. Have unplugged all USB devices except the bootable install USB thumb drive. I am running into an issue with the installer receiving the Error Preparing the Installation with 12 minutes remaining. L1i cache: 384 KiB After updating that, reboot to make sure that you can still boot Monterey. Thats the best Ive been able to get with any of the official TPU images. Failed to personalize the software. 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 dont need to hold it down). Grab a Thunderbold cable and connect the problematic Mac to a desktop computer. Currently there are 2 straight forward methods to obtain it: The simplest way to extract the OS.dmg is to download the IPSW listed on Apple's Developer Portal and grab the correct beta you'd like (labeled Mac computers with the Apple silicon). privacy statement. Below is simply for reference and research purposes. Keep pressing the keys until you are able to see the Apple logo on your Mac's screen. AppleIntelI210Ethernet.kext (transitioned to DriverKit), Newer hardware generally won't experience this issue, Extract OS.dmg from an Apple Silicon IPSW, Rip OS.dmg from active Apple Silicon installation, Kernel space may also ramp up AVX2.0 usage as betas continue, iMacs would need to drive an external display if using eGPU, internal display cannot be accelerated with an eGPU without modding. I have tried 2 different MacOS Ventura images (one from MacOS Archives, other from a friend) and in both cases, the VM starts, UEFI shows up, but I am not presented with Ventura installer option, but only UEFI Shell and Reset NVRAM options. Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constan