Lee.B

Good news this time, I tried to be more systematic in how I approached this to try and figure out what was broken. So from a working state; - Added switched to opencore and booted to make sure it worked fine (it did) - Rolled back to the updated Clover qcow2 - Updated to UnRaid 6.8.3, VM now booted fine - Updated to Catalina 10.5.4, VM now booted fine So I'm now on 6.8.3 & 10.15.4 without issue. Without going back and doing more testing the thing seems to be having the updated clover during the update process has fixed the issue. No idea why that would be that case *shrug* Thanks a lot for your help, especially around the quick responses and generating the qcow files it saved me a lot of time. Can I tip you a coffee?

So mixed news Firstly the qcow2 you generated, the VM started and Clover was updated so thanks for that it saved me a lot of time. Unfortunately no change to the behaviour. I've restored from a TimeMachine backup and the VM is running fine again now however I'm still stuck with the core problem that if I update UnRaid or Catalina it breaks the VM and both exhibit the same issue which I find confusing.

Thanks, I'm guessing I can use the pre-macinabox spaceinvaderone videos guide how to go about this? I'll give this a crack tomorrow as it's night here :)

2.5k rev 5097

I'm having some issues with my VM and I'm hoping someone can help me I've been happily running the VM for a while now but it doesn't seem to like upgrades First I tried going from UnRaid 6.8.2 to 6.8.3, once it was back up I couldn't get the VM to load properly anymore. It would open up but instantly it would peg it's first assigned core to 100%, it would slowly make it to the login screen with a graphical issue. If you type the password it would start loading and then just reboot. To fix this I rolled back to 6.8.2 and restored the instance from TimeMachine. Everything was ok... Until I tried to update Catalina to 10.15.4 (I was on the previous version 10.15.1?), after a restart it lets me know the update failed to apply and exhibits exactly the same behaviour. If I boot the VM into recovery mode it doesn't peg the CPU and works normally. edit: forgot to mention I'm not doing any GPU passthrough.