wintervaler

Not sure if you ended up resolving this, it's certainly been a few months, but I thought that on the offchance folks like me find this while searching for a solution, this post helped me: Basically, had to nuke the existing network config files and then reboot. My Mellanox NIC then showed up in the "Interface Rules" list. If you've made changes to the behavior of your network settings or the other NICs, you'll need to redo those with this fix. But in my case that wasn't super difficult.

Thank you very much for the suggestions. Unfortunately, still no dice. I went the reinstall route - I had messed up something in OCLP anyway and figured I'd start from scratch. But when I try to pass the GPU without VNC even before the first boot/install, I still get no display output and a pegged CPU core. Do you think there is something in my OC config.plist I should be changing before booting for the first time? It occurs to me that my working VM with this card -- Catalina -- was created when Macinabox was still using Clover, not OpenCore. Should that give any clues as to what might be missing for the initial boot? Should I try the boot arg you reference above in the pre-install stage or was that only if I had the OS up and running with VNC already?

Sure, thanks. Attached. nonworking_diagnostics-20220926-1511.zip working_diagnostics-20220926-1515.zip

Thanks very much for taking a look. I understand that Monterey doesn't support the card, hence my use of OCLP to patch it. System report picks up the GPU just fine, I get display output, and acceleration is enabled. But only when I also have VNC graphics setup. Doesn't boot otherwise, just hangs with the CPU core pegged and no activity. So unless I'm misunderstanding, I think I took the steps to solve the problem you're suggesting and in fact something else is going on? But I might be off base there.

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

Well, this is embarrassing. They're all back. Not sure what was going on.

Hey folks, I apologize in advance for what must be an absolutely ridiculous question. I removed my SWAG container and image a little while ago because I wanted to nuke and pave my setup (had a cert problem that I couldn't solve and I suspect I borked it while messing with the config last week and wanted to just start from scratch). Previously, I had a working SWAG container with several proxied subdomains working just fine. Now, I can't find the SWAG docker in Community Applications. Has it disappeared? Or am I being unbelievably thick? I can't seem to find any other dockers from the lsio repository either, come to think of it. I can get them from the Docker Hub results, just not from the main Community Apps index.