This shows you the differences between two versions of the page.
| proxmox:virtual:monterey [2024/07/28 11:51] – created dirk | proxmox:virtual:monterey [2024/07/28 12:13] (current) – dirk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Install MacOS as Proxmox Virtual Machine ====== | ====== Install MacOS as Proxmox Virtual Machine ====== | ||
| - | I have yet to install MacOS on Proxmox from the scratch... I converted the existing Unraid VM to Proxmox. The below steps outline that process and I hope to update this page with instructions for a fresh install. If not, do it on Unraid and then follow the below :D | + | I have yet to install MacOS on Proxmox from the scratch... I converted the existing Unraid VM to Proxmox. The below steps outline that process and I hope to update this page with instructions for a fresh install. If not, do it on Unraid and then follow the below :D. If you are attempting to install a fresh copy... try this: https:// |
| ===== Proxmox Settings ===== | ===== Proxmox Settings ===== | ||
| Line 30: | Line 30: | ||
| * Don't start vm after creation | * Don't start vm after creation | ||
| * Finish | * Finish | ||
| + | |||
| + | ===== Passthrough some stuff ===== | ||
| + | * Wait to do the GPU until the end (or try it now, I dunno. I did the GPU after successful boot but I think I did the USB stuff first to have keyboard and mouse access) | ||
| + | * Datacenter -> Node name -> VM | ||
| + | * Click Hardware | ||
| + | * Click Add | ||
| + | * PCI Device | ||
| + | * Raw Device | ||
| + | * Device: Select the Device you want to add based on its address | ||
| + | * All Functions: CHECKED | ||
| + | * Click OK | ||
| + | * I did this for USB and Wifi (though I turned Wifi off because I'm tracking down a webpage loading issue... not sure if it's PiHole or Wifi/Eth conflicts. | ||
| ===== Move virtual disk over ===== | ===== Move virtual disk over ===== | ||
| Line 83: | Line 95: | ||
| * link: https:// | * link: https:// | ||
| - | < | + | ===== GPU Passthrough |
| - | < | + | * Datacenter |
| - | < | + | * Click Hardware |
| - | < | + | * Click Add |
| - | < | + | * PCI Device |
| - | < | + | * Raw Device |
| - | < | + | * Device: Select |
| - | < | + | * All Functions: CHECKED |
| - | < | + | * Primary GPU: CHECKED |
| - | < | + | * Click OK |
| - | < | + | |
| - | < | + | |
| - | < | + | |
| - | < | + | |
| - | | + | |
| - | | + | |
| - | < | + | |
| - | < | + | |
| - | to | + | |
| - | < | + | |
| - | < | + | |
| - | * Now your install media in the boot loader should load. Select it, then your hard drive during each restart until it boots up! | + | |
| - | Links: https:// | + | |
| - | + | ||
| - | ===== Update to Sonoma ===== | + | |
| - | * After completing all the steps to get a working copy of Ventura... I updated to Sonoma using the Update feature in system preferences. | + | |
| - | * You can probably follow the steps listed in the above section (Update to Ventura) and just select Sonoma and it will probably upgrade from Monterey to Sonoma... I might check that sometime in the future. | + | |
| - | * I've been running Sonoma all of 10 minutes now and everything " | + | |
| - | * Wifi seems to cause everything to crash when you select the network tab (may be the same issue that was present in Ventura with having to hard restart the server to get wifi to not radio kill or whatever. | + | |
| - | * SMB shares are painfully slow to connect / don't work most of the time. | + | |
| - | * bluetooth doesn' | + | |
| - | * Installing a fresh copy and going straight from Monterey to Sonoma to see if that helps. | + | |
| - | * Fresh copy going straight from Monterey to Sonoma seems to have been MUCH better. | + | |
| - | * Wifi still has same issue as above (maybe need a newer kext when it comes out) | + | |
| - | * SMB shares work great now. | + | |
| - | * bluetooth still doesn' | + | |
| - | ===== Fixes and Tidy Up ===== | + | |
| - | Some of these may not apply to you but here's what I had to do to fix certain things as well as some things I did to tidy up my install | + | |
| - | * GPUs | + | |
| - | * AMD Radeon RX 6600 XT (works for Monterey and Ventura and Sonoma) | + | |
| - | * use OpenCore Configurator to mount EFI as above | + | |
| - | * open EFI/ | + | |
| - | * go to nvram | + | |
| - | * go to your nvram (the bottom one in UUID usually) | + | |
| - | * go to boot-args and add the value agdpmod=pikera | + | |
| - | * (It should now be agdpmod=pikera keepsyms=1) | + | |
| - | * Shut down VM | + | |
| - | * Edit your XML like above in the beginning for the GT710 but instead of using the GT710 slot, make it use the 6600xt. | + | |
| - | * Link: https:// | + | |
| - | * NVidia GeForce GT710/GT730 (only tested on Monterey and less) | + | |
| - | * Download OpenCore Legacy Patcher (https:// | + | |
| - | * Open it and click on Post install Root Patch | + | |
| - | * Start Root Patching | + | |
| - | * Yes | + | |
| - | * password for root | + | |
| - | * Restart | + | |
| - | * Profit!!! | + | |
| - | * video of this: [[https:// | + | |
| - | * Ultra Wide monitor? (works for Monterey and Ventura and Sonoma) | + | |
| - | * download DisableMonitor from [[https:// | + | |
| - | * Apple Login (works for Monterey and Ventura and Sonoma) | + | |
| - | * Download hackintool (optional but makes things easier). ([[https:// | + | |
| - | * open it (using same steps as you first used to open OpenCore Configurator) and go to System -> Peripherals | + | |
| - | * Network interfaces should have a en0 but the built in is unchecked (mine was actually checked on future installs so i don't know if the following steps were still required but i did them anyway | + | |
| - | * open opencore -> mount EFI -> open config.plist | + | |
| - | * go to DeviceProperties and select ethernet controller from list of PCI Devices at bottom (if it's not listed already) | + | |
| - | * click the + on the far bottom right of the right box to add a property to the ethernet controller. | + | |
| - | * For " | + | |
| - | * For " | + | |
| - | * For " | + | |
| - | * save and reboot | + | |
| - | * log in to apple services! | + | |
| - | * The hackintool technically isn't needed but it provides an easy graphical way to see if that " | + | |
| - | * Intel Bluetooth (only follow these steps for an Intel based Bluetooth card) (works for Monterey and Ventura) | + | |
| - | * Download IntelBluetooth-v2.2.0 from https:// | + | |
| - | * Download BrcmPatchRAM-2.6.4-RELEASE from https:// | + | |
| - | * Download Lilu-1.6.2-RELEASE from https:// | + | |
| - | * unzip all | + | |
| - | * open opencore -> mount EFI -> Mount Partition -> Open Partition -> Go to OC folder | + | |
| - | * copy IntelBTPatcher.kext and IntelBluetoothFirmware.kext from IntelBluetooth zip file into Kext folder | + | |
| - | * copy BlueToolFixup.kext from BrcmPatchRAM zip file into Kext folder | + | |
| - | * copy Lilu.kext from Lilu-1.6.2 zip file into Kext folder | + | |
| - | * open config.plist -> go to Kernel | + | |
| - | * drag from Kexts folder the .kext files that are NOT in the list under Kernel. | + | |
| - | * IntelBTPatcher and IntelBluetoothFirmware were the only two not already there for me. | + | |
| - | * Put IntelBTPatcher above IntelBluetoothFirmware above BlueToolFixup | + | |
| - | * Uncheck all the rest of the BCRM ones (not using them... i'm using Intel) | + | |
| - | * Save, reboot, profit. | + | |
| - | * Intel Wireless (works for Monterey and Ventura until the VM is rebooted... then requires server reboot and will work again until VM rebooted... still working | + | |
| - | * Download Airportitlwm_v2.1.0_stable_Monterey.kext.zip from https:// | + | |
| - | * Unzip folder | + | |
| - | * open opencore -> mount EFI -> Mount Partition -> Open Partition -> Go to OC folder | + | |
| - | * copy Airportitlwm.kext from zip into Kext folder | + | |
| - | * open config.plist -> go to Kernel | + | |
| - | * drag from Kexts folder the airportitlwm.kext file in the list under Kernel. | + | |
| - | * I put it all the way to the bottom. | + | |
| - | * Go to Misc -> Security | + | |
| - | * Change SecureBootModel to Default | + | |
| - | * Save -> Shutdown | + | |
| - | * Update VM xml file to passthru the wifi card < | + | |
| - | <driver name=' | + | |
| - | < | + | |
| - | <address domain=' | + | |
| - | </ | + | |
| - | <address type=' | + | |
| - | </ | + | |
| - | * Profit | + | |
| - | * Fix Memory Modules Misconfigured warning (suppress it) (only required when using Ventura and Sonoma with MacPro7, | + | |
| - | * download RestrictEvents kext from [[https:// | + | |
| - | * Open OpenCore Configurator and go to Kernel | + | |
| - | * Go to Download/ | + | |
| - | * Not sure of proper position in the list but I moved it to bottom | + | |
| - | * Go to NVRAM then UUID (at bottom of list) then boot-args | + | |
| - | * Add " | + | |
| - | * Go to PlatformInfo -> DataHub - Generic and check the " | + | |
| - | * Save and reboot. | + | |
| - | * Move VM disks | + | |
| - | * This one is easy and just puts my mind at ease to create future Mac VMs without overwriting data AND to make everything look the same in my vms folder. | + | |
| - | * copy the vm folder that contains your macos_disk.img file to it's new name. < | + | |
| - | * make sure you edit the xml file to point to the new location. | + | |
| - | * you can also change permissions to match other folders and edit groups and users. | + | |
| - | * Move NVRAM to normal location. | + | |
| - | * open up XML to get the UUID of the vm. | + | |
| - | * copy the custom NVRAM currently used to the default NVRAM folder for unraid and use that UUID while following the naming convention. < | + | |
| - | * make sure you edit the xml file to point to the new location. | + | |
| - | * Point OVMF to normal location. | + | |
| - | * For this one, you can copy your custom one into the default folder. < | + | |
| - | * OR you can do what I did and use the one that is already in there (unraid' | + | |
| - | * make sure you edit the xml file to point to the new location. | + | |
| - | * csr-active-config | + | |
| - | * This was set to 260F and I changed it to 00000000 to get rid of the error in the OpenCore Validator. I only did this in Sonoma and I haven' | + | |
| - | * Will report back! | + | |