![]() 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. first : how can Protective MBR contain bootstrap code without being hybrid ? ( gdisk says that it's not hybrid ) second : is clover 32 bit booting under Legacy mode ? third : how can Clover 32 bit be booted using "bootia32.efi" that exist in EFI Partition and how can clover 32 execute other "bootia32.efi" when my laptop's UEFI is 64 bit and can only execute "boot圆4.My previous Proxmox post described how to install Sierra into Proxmox using the Enoch bootloader (SeaBIOS boot). I installed Hackintosh using custom installer made by niresh on UEFI laptop with gpt disk and i had hackintosh 64 bit and windows 7 64 bit installed and boot using clover 64 bit but windows was very laggy ( my laptop usually running slow especially on 64 bit systems ), so i decided to install and run windows 8.1 32 bit but it was a challenge for me because UEFI is only boot 64 bit efi files and can't boot "bootia32.efi" at all so i thought i can use hybrid MBR/GPT to boot windows 32 bit using legacy mode and hackintosh 64 bit using UEFI mode but i realized that Clover itself was installed in very strange way, it has code in MBR's bootstrap and at the same time it has EFI files on EFI Partition that it's file system is HFS+ !!!!, i knew later that clover 32 can be triggered by pressing 3 number on the keyboard and clover 64 can be triggered by pressing 6, finally i was able to boot windows 8.1 by "bootia32.efi" on Clover 32bit, the problem is that i can't understand few things here.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |