|
14 | 14 | <a href="/LICENSE"></a> |
15 | 15 | <a href="/docs/CHANGELOG.md"></a> |
16 | 16 | <a href=""></a> |
17 | | - <a href="https://github.com/acidanthera/OpenCorePkg/releases"></a> |
| 17 | + <a href="https://github.com/acidanthera/OpenCorePkg/releases"></a> |
18 | 18 | <a href="https://github.com/Qonfused/OSX-Hyper-V/actions/workflows/oce-build.yml"></a> |
19 | 19 |
|
20 | 20 | </div> |
@@ -614,6 +614,9 @@ First check that you've [enabled Hyper-V](https://learn.microsoft.com/en-us/virt |
614 | 614 | > .\Scripts\create-virtual-machine.ps1 -name "Catalina" -version 10.15 -cpu 4 -ram 16 -size 128 |
615 | 615 | > ``` |
616 | 616 |
|
| 617 | +> [!IMPORTANT] |
| 618 | +> Newer macOS versions (Big Sur and newer) require 6-8 GB of RAM to boot the installer. If you are using an older version of macOS, you can use less RAM (4 GB is the minimum). |
| 619 | +
|
617 | 620 | Below outline the steps to manually create a new virtual machine for macOS: |
618 | 621 |
|
619 | 622 | --- |
@@ -698,16 +701,67 @@ Then configure the below options under the Hardware section: |
698 | 701 |
|
699 | 702 | Refer to the [Installation Process][Dortania-Guide/Installation-Process] section of the Dortania Guide. Some additional post-install sections are provided to facilitate with Hyper-V (or project) specifics. |
700 | 703 |
|
| 704 | + <!-- |
| 705 | + Another user's suggestion for installation steps (for reference): |
| 706 | + 1. Run PS script to create VM |
| 707 | + 2. Start VM, open Console |
| 708 | + 3. boot to EFI (dmg) to launch recovery menu |
| 709 | + 4. Enter Disk Utility |
| 710 | + 5. Choose "Msft Virtual Disk Media", Select "Erase" |
| 711 | + 6. Name new drive "MyInteralDrive", choose AFPS for filesystem format |
| 712 | + 7. Execute Erase |
| 713 | + 8. Quit Disk Utility |
| 714 | + 9. Back at main menu for the Recovery program, choose "Reinstall macOS " |
| 715 | + 10. Select your newly minted AFPS-formatted disk |
| 716 | + 11. Let macOS do it's thing for approx 2 hours. |
| 717 | + --> |
| 718 | +
|
| 719 | +A basic summary of the installation process is as follows: |
| 720 | +
|
| 721 | +1. Start the virtual machine and select the `EFI (dmg)` from the OpenCore boot menu. |
| 722 | + - If you created a separate macOS installer VHDX, this may also show up as `macOS Base System (External)` or `Install macOS Big Sur (External)` depending on the version of macOS you are installing. |
| 723 | +2. Once the installer loads, open Disk Utility from the Utilities menu. |
| 724 | + - Select the `Msft Virtual Disk Media` (your main virtual hard disk) from the list of disks. |
| 725 | + - Click `Erase` to format the disk. |
| 726 | + - Name the disk as desired (e.g., `macOS` or `Macintosh HD`, etc.). |
| 727 | + - For macOS 10.13 and newer, use the `APFS` format. For older versions, use `Mac OS Extended (Journaled)`. |
| 728 | +4. Quit Disk Utility and return to the main installer menu. |
| 729 | +5. Select `Reinstall macOS` to start the main installer. |
| 730 | + - Follow the prompts to install macOS on your newly formatted disk. |
| 731 | + - Make sure to target the disk you just formatted (e.g., `macOS` or whatever you named it), not the EFI disk. |
| 732 | + - Note that this process may take a while (upwards of 30 minutes to 2 hours). |
| 733 | +6. Once the installation is complete, the virtual machine will reboot and you should see the OpenCore boot menu again. |
| 734 | + - This may require multiple reboots to install additional components and finalize the installation. |
| 735 | +7. Select the newly installed macOS disk (or whatever you named it) from the OpenCore boot menu to boot into macOS. |
| 736 | + - If you are still unable to boot into your macOS installation, you may need to select the installer disk again. |
| 737 | + - You can set this as the default boot entry by holding the `Ctrl` key while selecting the disk. |
| 738 | +
|
| 739 | +The EFI virtual disk created by this project bundles a post-installation script responsible for installing the **MacHyperVFramebuffer** driver and configuring daemons for additional Hyper-V service support. This is required to support resolution changes and the hardware cursor in macOS. |
| 740 | +
|
| 741 | +To run this script, execute the `post-install.sh` script from the EFI disk located in the `Scripts/` directory. For example, you can run the following command in Terminal after booting into the macOS installer: |
| 742 | +
|
| 743 | +```bash |
| 744 | +cd /Volumes/EFI # Change to the EFI disk |
| 745 | +bash ./Scripts/post-install.sh |
| 746 | +``` |
| 747 | +
|
| 748 | +You can also optionally run the `optimize-vm.sh` script to disable Spotlight indexing, reduce disk I/O, and turn off system animations. This is recommended for virtual machines with CPU-rendered graphics and limited disk performance. |
| 749 | + |
| 750 | +```bash |
| 751 | +cd /Volumes/EFI # Change to the EFI disk |
| 752 | +bash ./Scripts/optimize-vm.sh |
| 753 | +``` |
| 754 | + |
701 | 755 | [Dortania-Guide/Installation-Process]: https://dortania.github.io/OpenCore-Install-Guide/installation/installation-process.html |
702 | 756 |
|
703 | 757 | #### Limitations |
704 | 758 |
|
705 | 759 | There are some known limitations with the base configuration for Hyper-V: |
706 | 760 |
|
707 | 761 | - Display Resolution |
708 | | - - The default virtual display resolution is set to a 1024x768 resolution and is not resizable. |
| 762 | + - The default virtual display resolution is set to a 1024x768 resolution, but can be reconfigured by modifying the `SupportedResolutions` entry in MacHyperVFramebuffer's Info.plist file. See issue #6 for more details. |
709 | 763 | - Graphics Acceleration |
710 | | - - By default, macOS will run without graphics acceleration using VESA graphics drivers (CPU). Additionally, display graphics is limited to 3 MB of video memory. |
| 764 | + - By default, macOS will run using the MacHyperVFramebuffer synthetic graphics driver, which provides basic graphics support (with 8 MB of video memory). This driver is sufficient for basic tasks, but does not provide hardware acceleration or advanced graphics features. |
711 | 765 | - GPU acceleration is possible through [Discrete Device Assignment (DDA)][aka.ms/dda] using a supported GPU, however there exist a couple major caveats: |
712 | 766 | - AMD GPUs (particularly Navi and older GPUs) generally have poor compatibility with macOS through DDA. Natively supported NVIDIA GPUs (using driver v465 or later on Windows) tend to have the best results. |
713 | 767 | - GPU patching with Lilu and WhateverGreen is currently not supported (refer to [#2299](https://github.com/acidanthera/bugtracker/issues/2299) for tracking). This also applies to other kexts like NootedRed/NootedRX that use Lilu. |
|
0 commit comments