Clover configurator sierra1/4/2024 We need to edit that to add +invtsc to enable invariant timestamp counter support, add the vmware-cpuid-freq option, and turn kvm back on (exposing the fact that this is a virtual machine to macOS): -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on Install Clover to the EFI partitionĪt this point you might want to take a snapshot of your Sierra install, so you can roll things back if it goes wrong. You should currently have an “args:” option in your VM configuration that contains: -cpu Penryn,kvm=off,vendor=GenuineIntel In Proxmox 5, we don’t need to patch Clover, we just need to enable the vmware-cpuid-freq feature on the CPU in our VM’s configuration. Proxmox 5: Enabling vmware-cpuid-freq support This will produce an installable package for us in “edk2/Clover/CloverPackage/sym/Clover_v2.4k_r4061.pkg.”. The default options, which use XCode to build an X64 bootloader, are perfect for us.Īfter that completes, run “cd CloverPackage. Change into that directory and run: svn patch clover-r4061-qemu-cpu-speed-patch.diff Build CloverĬhange into the “edk2/Clover” directory, and run. User “arne ziegert” over on the Clover issue tracker came up with a patch to fix the CPU speed issue on QEMU, which we’ll apply before we build Clover.ĭownload this patch to “edk2/Clover”. You can skip the line that runs “./buildgcc-4.9.sh”, since we’ll be using XCode instead. When it checks out the latest Clover source: svn co svn://.net/p/cloverefiboot/code CloverĬheck out revision 4061 instead: svn co -r 4061 svn://.net/p/cloverefiboot/code Clover On the line that fetches EDK2: svn co -r 18198 svn://.net/p/edk2/code/trunk/edk2 edk2įetch EDK2 revision 24132 instead: svn co -r 24132 svn://.net/p/edk2/code/trunk/edk2 edk2 Fetching Clover sourceįollow steps 1-3 from the section “ compiling from source“, with some changes: Note that when the instructions say to make a directory called “src” in your home directory, you should listen! There are hardcoded paths that will look for built tools in that directory, so it’s much easier to just go with the flow here. Run “sudo xcode-select –install” to ensure the command-line tools are installed. Run “sudo xcodebuild -license” to accept the license agreement. Install XCode from the App Store before you start. We’ll be following the official Clover building instructions, but we’ll be modifying those slightly. You can either just download my prebuilt patched Clover r4061 / EDK2 r24132 installer, or follow the instructions in this section to patch and build Clover yourself. Building your own copy of Clover with the QEMU CPU speed patch for Proxmox 4.4 So on Proxmox 5, we can just edit the VM configuration to enable this feature, and afterwards we can install an unmodified official Clover release (I’m using r4097) using the install instructions further down this page. Proxmox 5 has support for telling macOS exactly what the CPU’s frequency is, by exposing a VMWare-style interface that macOS knows how to read. On Proxmox 4.4, we have to patch Clover to fix this, follow the instructions in the next section. This makes window animations, the system clock, movie players, typematic repeat, etc., run much too fast or too slow. However, there’s an issue at the moment with Clover and QEMU which causes macOS’s detected CPU speed to be wrong. This requires us to use a macOS bootloader that supports UEFI. So if your video card’s firmware supports UEFI/EFI boot (my R9 280X already does), you can switch the guest to boot using OVMF instead. UEFI boot doesn’t suffer from this problem, since it does away with the legacy VGA interface. From what I understand, the video cards in the host and guest can end up both contending to own the VGA resources, which can cause a deadlock on boot. When a Sierra guest loads its video driver during boot, my Proxmox host hangs, and the screen fills with black and white bars. One of the problems with legacy BIOS boot and GPU passthrough is VGA arbitration. I managed to fix these by updating to UEFI boot with Clover. However, I had some real struggles getting the graphics card passthrough to work reliably. Since then, I’ve been using it as my daily-use desktop, and it has generally been working out great for me. My previous Proxmox post described how to install Sierra into Proxmox using the Enoch bootloader (SeaBIOS boot). Magic Trackpad 2 causes kernel heap corruption when passed to a Proxmox guest, GPFs.Installing macOS 12 “Monterey” Developer Beta on Proxmox 6.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.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |