Hey all, first of all thank you so much for the incredible community here - I've learned so much. I have a problem I've been spending hours and hours with and figured it might finally be time for a forum post to see if anyone else is seeing this issue with Macinabox and Monterey.
My Unraid server is running a Xeon E3-1230 v2, and I have a very stable Catalina VM with an Nvidia GT 710 passed through.
I decided I'd try a Monterey VM -- not upgrading, but doing an entirely new VM. Installation was totally fine. The VM works completely normally until I try to pass through the GT 710. When I do that and fix the XML, I end up with these errors in the log while one thread of my CPU pegs at 100% utilization:
2022-09-26T03:00:01.928280Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
2022-09-26T03:00:01.928334Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.bmi1 [bit 3]
2022-09-26T03:00:01.928340Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx2 [bit 5]
2022-09-26T03:00:01.928346Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.bmi2 [bit 8]
2022-09-26T03:00:01.928353Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-09-26T03:00:01.929543Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
2022-09-26T03:00:01.929555Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.bmi1 [bit 3]
2022-09-26T03:00:01.929559Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx2 [bit 5]
2022-09-26T03:00:01.929562Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.bmi2 [bit 8]
2022-09-26T03:00:01.929565Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-09-26T03:00:01.930381Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
2022-09-26T03:00:01.930397Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.bmi1 [bit 3]
2022-09-26T03:00:01.930404Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx2 [bit 5]
2022-09-26T03:00:01.930410Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.bmi2 [bit 8]
2022-09-26T03:00:01.930416Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-09-26T03:00:01.931230Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
2022-09-26T03:00:01.931242Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.bmi1 [bit 3]
2022-09-26T03:00:01.931245Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx2 [bit 5]
2022-09-26T03:00:01.931248Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.bmi2 [bit 8]
2022-09-26T03:00:01.931252Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
So, then I tried using both VNC and passthrough graphics, and that boots well (the errors above still show, but it ignores them this time). I could view VNC graphics and macOS was detecting the card in System Profiler but not directing any output there.
With the VM booted in this mode, I ran the post-install root patch from OCLP and upon reboot, presto! Display output from the 710, with macOS essentially outputting to "two" displays - VNC and the GPU. But once again, when I shut it back down and removed the VNC graphics from the XML, the boot would hang and peg that lonely CPU core again.
I'm reading that Monterey dropped support for Kepler cards like mine, but this feels like something else is going on -- namely the QEMU complaints that my CPU doesn't support FMA, AVX2, BMI, etc. I didn't think that would be an issue, but is it the case that maybe my CPU is just a bit too old to be messing with Monterey? I notice distinctly fewer QEMU CPU args are passed to my stable Catalina VM, so I tried removing some of the Monterey `-cpu` args. The errors go away, and it looks like a normal boot from the log, but single CPU core once again pegs and there is no display output. BUT it seems like if it were an issue with CPU functionality then I'd also be having trouble with VNC. It seems like plenty of people are running Monterey on Sandy Bridge / Ivy Bridge CPUs like mine, but maybe they're messing deeper with OC patches than I am.
I'm attaching my current XML - the working version with both VNC and GPU pass - as well as the version that hangs when I remove the VNC graphics.
Any new directions I should be exploring here or should I live with Catalina until a hardware upgrade?
Thanks in advance for any help you can be.
NOTWORKING-pass-only.xml
WORKING-vnc+pass.xml