david279

You might want to google editing clover plist then....hackintoshing comes with a bit of upkeep.

Did you go into your cloverEFI plist and change the resolution to what you changed it to in the OVMF settings? It needs to at least match to get rid of the garbled screen.

Yeah i kinda see this same thing. Mac OS sees it as a ssd but there is no real way to see if any trim is actually happening. I do keep sata and virtio versions of my VMs to handle trimming of my vdisk if needed.

<disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/cache/domains/Catalina/catalina.opencorev0591.qcow2'/> <target dev='hdc' bus='usb'/> <boot order='1'/> <address type='usb' bus='0' port='1'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native' discard='unmap'/> <source file='/mnt/disks/MKNSSDRE500GB_MK170901100386B42/Hackintosh/Catalina.img'/> <target dev='hdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk>

Im using a raw image file in catalina and a qcow2 image file for big sur. No passed through disk..

Virtio network does not work like it should but virtio disk works for me on catalina and big sur. Running 0.5.9 opencore on Catalina and 0.6.0 dev opencore on big sur.

rx 560... Up to a rx 580. Cheap with good performance.

Download a gparted iso, add it as the install iso on a new VM and add any other vdisk on your system as a secondary vdisk. When you boot the VM just use gparted as any other live cd and you can manipulate the vdisk you added any way you want.

I was able to expand a vdisk today, i took a couple of steps but it worked for me. I had to use a gparted VM i have for doing some vdisk work. ...Expand the vdisk in the unRAID GUI ..boot the expanded vdisk in a Gparted VM ..Gparted will alert you that the gpt of the vdisk does not recognize all the free space on the disk and will fix it. Allow it to do so. Shutdown the Gparted VM. ..Boot you macOS VM with the Newly expanded vdisk. ..In the terminal do diskutil list and find the Apple_apfs Container disk. it will probably be disk1 ..Run the command-- diskutil apfs resizeContainer /dev/diskx 0. It should expand you vm to use all available space. Worked for me in but if its a bit scary for you use the migration assistant or disk utility in recovery partition using the restore function. And always keep backups.

I had this running in pop os as well so I don't know how old the ovmf files in unRAID are but it may be worth taking a look at them. The are some beta AMD patches out for opencore and the topology patch in it looks the same as the one we are using.

Ok to get this started i had to use some files from http:// https://github.com/kholia/OSX-KVM/tree/master/OpenCore-BS Big shout out time kholia because without his files I would have not been able to get this started. A couple files needed from there are OVMF_VARS-1024_768.fd, OVMF_CODE.fd and his Opencore.qcow2 made for Big sure. The opencore img thats used is kinda bear with only the options included needed to boot but it works. First thing you are going to need is an installer image. I created one by using the gibMac script on my Catalina VM to pull down the developer preview. The files that will be downloaded will not be a straight up installer. With the set of files that will be downloaded the main one we need is a package called InstallerHelper. Install that pkg and it should add a Install Mac os beta app into your Application folder. Use that app to create a installer disk. I added a 16GB vdisk to my Catalina VM and used that to make the installer disk. You can use the disk utility to make a disk image on the VM and use that to make a installer disk if you perfer. I used the createmediainstaller command to make the installer disk. https://support.apple.com/en-us/HT201372 I had to use 16 GB for the image size, anything less than that the command would not bless and make the installer image bootable, strange bug. So do not try 8GB or something. Once you have the installer image created its time to use that make the VM. Create Your VM like a normal Hackintosh style VM...with all the hackintosh needed bits. Instead of going with the normal OVMF paths unRAID adds use the files from Kholia link above and add there paths to them on your unRAID system. The files are from proxmox but they are needed to boot the Big Sur installer/system. Unraids OVMF crash right after you set the install boot selection so for right now we can not use it. Use his opencore image as the main boot image , add a vdisk for the systems main disk and add the installer image as the third disk to install Big Sur. Boot up the VM, select the big sur installer and install as a normal hack VM. Once you have you system setup you will needed to make a couple edits to your opencore config.plist to make kext injection work. The system does not needed any kext to install or function in pure vnc form but if you plan on passing thru a GPU or onboard sound, hardware etc....You will need kext like lilu, whatevergreen or applealc. You will need versions of lilu, whatevergreen and applealc with the big sur bits for it to work with big sur. I found them here https://onedrive.live.com/?authkey=%21APjCyRpzoAKp4xs&id=FE4038DA929BFB23%21455036&cid=FE4038DA929BFB23 Also you need version 0.60 of opencore with added support for big sur. This one should work. https://1drv.ms/u/s!AiP7m5LaOED-npRyiiFiyxR0R46u3g All this stuff can be found thru the Hackintosh discord. Now to editing your config.plist. All the lines with the booter-fileset-basesystem, booter-fileset-kernel need to be added as seen above. Also for lilu to work you need the -lilubetaall boot-arg for it to work in big sur. With those edits made then update opencore to 0.60. Now shutdown your VM. At this point if you try to boot right back into Big Sur it will crash. For whatever reason after adding the patches above will cause a kernel panic with a topology crash so you will need to remove all the topology lines from your VM. I tried to use the topology patch we have used here but it still did not work. Once you remove the topology line the VM will boot right up with working kext injection. I have a full VM setup with a GPU, usb pci-e wifi bluetooth card, onboard sound all working great. The system right pretty good right now. You will find apps that straight up crash like maps but this is a dev preview. Opencore should get some fixes soon that will make kext injection work without the config.plist edits made above. Also as opencore is updated maybe we can go back to unRAIDs OVMF files for bootup. OVMF_CODE.fd OVMF_VARS-1024x768.fd

I'll write up something in the morning. Been messing with this all day and just got it right.

Time to start it up...

Ok im downloading the dev preview using gibMacOS now. Gonna give it the good ole college try...

Nobody in the hackintosh discord has it booting yet so don't be disappointed

You tried to update from Catalina? I need copy of that installer disk.

Any AMD card rx 560 and up should be fine just make sure you have a HDMI dummy plug connect or you probably will not get a video out from the GPU.

This world make using PFsense VMs a lot less chaotic when bringing down the array.

Pfsense VM works now without any xml modification on the new 6.9 beta22

I updated to it earlier. Not many changes needed. I want to try out the Virtio support it added but do not have the time right now. Also 10.15.5 supplemental update released.

Headless will not get any sound without using some kinda fancy audio software to route the sound. So you have a little hill to climb.

You have it working but you are not going to get audio out thru nomachine, the hdmi2k has to be selected. Also the audio is going to come directly from the HDMI so a monitor or sound out from that monitor is where the sound is going to come from. Is the hdmi2k a dummy plug or something?

Updated all good over here. I'm on opencore 0.5.8.

I've had that setup for since forever but making a backup a vdisk is dead easy.

10.15.5 is out make your backup and be safe out there.