derpuma

Okay, I would like to test opencore instead of clover. How would I install opencore into the qcow2 EFI partition and the main OS system? Manual install like you mentioned before with clover by copying the files by hand? Do you have also an opencore Zip to share? I guess the opencore config.plist file should be a new one witch fits the new bootloader. Talking about Quirks: I have read in the hackintosh forum that the newest clover does not need any quirk for Big Sur (Version 5123+). I'd like to try it with clover first, so which quirks should be set in clover configurator.

Thx for the image. I was able to update clover manually with all the files from the zip. It also boots fine into Catalina with the updated files. But installing the update from Catalina to Big Sur from the macOS update center fails and after the first restart the system first boot up after the Big Sur Intallaion Window and dialog it boots up into the apple logo and from there nothing happens. I kept my previous config.plist file in my clover folder, thinking this should be ok. All kexts I used prior are updated to the latest version! Did you update to Big Sur already? If so, how have you done it? Regards!

As Big Sur is now on the road, it looks like Macinabox needs a clover update in order to update from a running Catalina and boot into the preeboot updater of Big Sur update. I managed to load the latest kexts needed for Big Sur into the EFI/CLOVER/kexts/other folder. But I need to update clover and it's boot files to. How can I update clover while I am booted up into VM Catalina? Clover configurator and the update from there fails. THX FOR HELP!

Think I am going for an USB3 card too. I found only 2-port Cards from Inatek with KT4006. But Inateck PCIe USB 3.0 Karte 4 Ports KTU3FR-4P with eSata Power hast Fresco chipset too, so might work also without tweaking.

I guess I messed up at this part, thinking I have to put a new EFI on the VDISK EFI Partition. I simply did not copy the EFI Folder from the SSD to clover.qcow2 EFI Folder and this is why Clover was empty trying to find the SSD. I will do that again and see if I get it there right now. Thx a lot! Also I am still on USB2 setting in my XML. That USB3 is prefered? quemu or nec?

@ghost82 Thx for your reply! Appreciate it... I will try the S3 plugin. This would be a better solution then the script with it's power off/on. 1) Resizing: I tried that wit Carbon Copy Cloner. Made a complete backup of my initial 64G VDisk Catalina installation. Created a new 500G VDisk from scratch with Macinabox without installing anything on it. Next I copied Clover.qcow2 and the other files from my 64G installation next to the new VDisk. Then I mounted the VDisk and cloned the 64G Image back to the 500G Partition. After Cloning if mounted the EFI partition of the new 500G Vdisk and copied the 64G EFI over to the new installation. Unfortunately this did not work and I did not see the Vdisk in clover while booting the new VM. 2) I would like to boot from my older hackintosh OS X, macOS Systems which are all on SSDs. Reason: I have an older Silicon Image e-SATA controller which is not supported anymore (since Mojave). Mojave and Catalina are not able to boot up, if the controller card is on board (kernel panic). With Unraid, booting up virtually this is no problem, and it would be great to boot in an older system, to get support of this card and have access to a buch of HDD Housings, connected to that card. I am completly new into Opencore, but I will def. give it a try. So far I am pretty impressed that everything out of the Macinabox installation (plus replacing some kexts and small config.list changes and passthrough GPU and USB) gives me such a stable and fast running system...

One question, I have my macOS 10.15.5 now running with USB and GPU passthrough. All stable and reliable, I worked a couple of days now with the system. Also benchmarks of CPU and GPU are fast. Seems like Gigabyte Z570 Aeros Pro and its IMMOU Grouping makes passthrough very easy. My GPU is a RX 5700 XT and I do have the AMD reset bug. Using the script from SpaceinvaderOne makes it poccibel to restart macOS VM without rebooting UNRAID server: My question regarding to your quote (sorry I am relativly new into Virtualisation): I am still on Clover.qcow2 with an individually updated EFI Folder on my macOS VDISK. (newes Whatever... Lilu... etc. kexts)... Can you explain what you mean with "put the machine into s3 sleep (the sleep button in the action page)". I don't get exactly what you mean! Is those only opencore related or do you mean I have to send UNRAID Server into S3 with a another script, similar to the script I already use (or is it exactly the same script)... Sorry for my confusion. And I do have two other questions: What are the option to resize an APFS partition of an already installed macOS? I failed using Disk Utility and diskutil via terminal using: diskutil apfs resizeContainer /dev/disk2S 0 And is it possible to boot from SSD with EFI Folder on it and a preinstalled Hackintosh Installation from an older system? I guess I have to update the Clover or Opencore QCOW2 image somehow and made changes there to fit the needs of the system from SSD? What would be the best procedure to get this external system booted? thx in advance!

It should be possible if you do it right! Be carefull, that you create a new, non existing name and that the <uuid> is unique. What error message shows up? Are you able to update and only the name does not show up? Look if you do not mess up with <name>MacinaboxCatalina</name> and <description>MacOS Catalina</description>...

I saw others successfully using Carbon Copy Cloner too. I guess the main Clover Partition is in the Clover.qcow2 file. What I would like to do is boot from my older OS X installations from SSD. I have a couple of disks with Mojave and High Sierra and it would be nice to boot from Unraid via SSD. I tried that with the /dev/disk/by-id/ata-Crucial_CT500MX200SSD1_15040E7D6DF8 but it did not boot up and get stuck while the loading bar under the Apple logo appeared. So my question is: Does the Clover.qcow2 take any information from the EFI Folder of the linked new SSD Boot device? Or would it be necessary to edit something in the Clover.qcow2 File too? When I tried to boot up, I saw clover boot options from my VDISK installation, so I guess Clover.qcow2 linked to that image? Would it be generally possible to modifiy the files manually and boot like I'd like to? I just need to know how everything connects... Thx!

As I was not able to manage it, to resize the apfs partition of may macOS after I have installed it (it does not work for me with disk utility and neither with diskutil apfs resizeContainer /dev/diskXsX 0 via terminal), I would like to get rid of some unclarity in regards of booting into the macOS VM. I tried to clone my small 64G partition via Carbon Copy Cloner into a new 500G VM disk of a fresh macOS Catalina install (mounted via Diskimagemounter in macOS). This worked fine so far, I also mounted the EFI partition of the new cloned and larger VDISK and replaced the EFI Folder with the one of my 64G Disk where I have made some changes in the config.plist and updated some kexts. I also copied the Clover.qcow2 image and the ovmf folder of my smaller working macOS Vdisk over to the new bigger VDsik. Unfortunately the system was not able to boot afterwards. Clover was empty and I was not able to select the boot devices. What am I missing? It would be nice, if someone could explain me how booting is done step by step. What is where, what's the rule of the Clover.qcow2 image? I thought all booting information is in the EFI Folder of the corresponding VM OS VDISK Drive. Cause I failed, I did another fresh install of macOS into a 500G fresh VDisk and migrated the system via Apples Migration Assistant, which worked flawless. Anyhow, I would like to understand how booting works to get manual access to some operations via CCC f.ex. Thanks in advance for some explanation!

I also failed using terminal and diskutil:

Failing to expand my Macinabox System macOS partition! Diskutility won't let me do it. I expanded my VDISK under UNRAID form 64G to 400G. Booting back into macOS it shows the free space, if I delete the free space and try to expand the system disk to max new space, diskutility gives me an error saying "disk already has the space"... which it doesn't, it still stays at 54G. What am I doing wrong?

Finally I got my macOS working on my Ryzen 3900X, Gigabyte Aorus Pro Z570 setup. I had some trouble with my RX 5700 XT and spent hours after I found out, that it has a black screen of death at its diplay ports. So if you guys have troubel, try over HDMI or get a HDMI-dummy-dongle to avoid these problems. Also I had to modify the cClover config.plist and to add some bootargs, deselct ATI Inject and insert the loading of the VBios. Also I updated all the three kexts in the EFI kext folder under "other" and added the vodoHDA.kext to get Audio to work. So far all is running rocksolid. Next thing I will try is to clone my macOS VM, get rid of the VDISK there replace it and boot macOS from an installed unassigned SSD devie with a macOS on it. Any help how I can assign this APFS drive to this VM and boot from it? Is it enough to set the right path in the XML file to it's disk location? Like /dev/sdx and it will boot from APFS then? Cheers and happy days!

Your GPU will not work, as it is not supported by macOS! Unfortunately there is no way to make use of your card so under macOS. Get a supported GFX like mentioned here... Also older NVIDIA GPUs will work, GTX 1070, 1080, etc. with webdriver. All GTX780 will work OOB without the need of any NVIDIA webdrivers.

Same Problem here and I did not solved it jet. Can someone please explain what exatly to do to get rid of the unknow device? I did not found any driver located in the mounted virtio-win disk folders. thx in advance!