wbsmolen

@hiptoss exactly what I was looking for. Thank you!

Hyper-V recently added support for nested AMD virtualization. Requesting Unraid build feature parity. https://techcommunity.microsoft.com/t5/virtualization/amd-nested-virtualization-support/ba-p/1434841

Didn't pursue it. My system is amd-based and has a lot of issues with kvm nested virtualization.

I've been looking into this for months. I don't understand why vmware can do this without issue but kvm can't.

Hoping the patch described in this post can be applied to unraid OOB.

+1

Appreciate it, sincerely. That sounds like the standard AMD reset but that can be fixed via kernel path or user scripts. I’m hitting something that may be specific to my board

No. Force stop and then start the vm. hit esc rapidly on the bios boot logo screen to open bios settings. from there, go to device manager and change ovmf's resolution to match clover (1920x1080 default)

then my "power state d3" failures aren't related to bios. I'm up to date there

Enrolling a guest win10 vm in Intune or Azure AD Join triggers application and credential guard -- both use hyper-v technology. OOB, Unraid's hyper-v compatibility doesn't support this scenario. The result is a BSOD on every boot with "HYPERVISOR ERROR" as the message. I realize I'm requesting something nontrivial, but I can't imagine I'm the only person who would appreciate it.

FWIW -- this is what I was getting at. I added more cache storage and called it a day. I'm guessing kvm perf navigating multiple disk drivers across multiple physical drives would be suboptimal, if at all possible.

Was anyone hitting this bug with the x570 taichi board from asrock? I'm hitting similar symptoms. Before I start trial/error downgrading to various revisions, I'm hoping someone else knows which bios ver works

No luck, thanks anyways.

You are a saint. I’m going to boot into VNC, copy/paste your EFI into mine, then look for gaps in our XML and take action. I’ll report back in a bit.