![]() I also passedthrough an NVME drive for video editing. I managed to get it working for me, however, i had to pass the rom file and enable multifunction, I didnt have to do this in windows. I just need to know how everything connects. Would it be generally possible to modifiy the files manually and boot like I'd like to? When I tried to boot up, I saw clover boot options from my VDISK installation, so I guess Clover.qcow2 linked to that image? Or would it be necessary to edit something in the Clover.qcow2 File too? So my question is: Does the Clover.qcow2 take any information from the EFI Folder of the linked new SSD Boot device? ![]() 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 I have a couple of disks with Mojave and High Sierra and it would be nice to boot from Unraid via SSD. What I would like to do is boot from my older OS X installations from SSD. I guess the main Clover Partition is in the Clover.qcow2 file. I saw others successfully using Carbon Copy Cloner too. In the end, it was just easier to fresh install and use migration assistant. Spent hours trying to resize the partition, couldnt get it working. 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.Ĭause 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.Īnyhow, I would like to understand how booting works to get manual access to some operations via CCC f.ex. It would be nice, if someone could explain me how booting is done step by step. Clover was empty and I was not able to select the boot devices. Unfortunately the system was not able to boot afterwards. I also copied the Clover.qcow2 image and the ovmf folder of my smaller working macOS Vdisk over to the new bigger VDsik. 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 ist and updated some kexts. 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). ![]() ![]() 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |