Gitchu

I've been doing some digging, and there are two relevant known issue on reddit: https://www.reddit.com/r/VFIO/wiki/known_issues First is IRQ issue on QEMU 4.0+ (Unraid 6.8.0 stable uses QEMU 4.1.something). Second is the BIOS update AGESA issues, which the wiki says are similar to the old threadripper reset bug. https://www.reddit.com/r/VFIO/wiki/known_issues I may just try to roll back to an older version of unraid and see if it resolves the QEMU issues and lets me boot..

I'm not sure if I'm 100% on topic or should start a new thread, but I recently upgraded my x370 board and things have been interesting. I have an Asus Prime x370 Pro which was working fine with my Ryzen 1700 for a long time on an older BIOS from 2018, with decent IOMMU grouping for USB passthrough to VMs. I ordered a Ryzen 3900x and upgraded BIOS while I waited for it to come in the mail, and ran into the same problem as Spaceinvader One in the video below. (I think this is what @mhentschke is getting) Luckily, plugging in the 3900x mostly fixed things, but my IOMMU groups totally changed (I don't have a single usb controller that's in it's own IOMMU group anymore, so that sucks). It sounds like for that part of the problem, the solution is either upgrading the CPU or installing the custom kernel per previous posts. After the BIOS and CPU upgrade hardware addresses for some of my devices changed and had to be updated in the VM XMLs for things to work. For example, an address that used to direct to a discrete USB controller I installed turned into some other PCI bridge or something, and that was listed under "Other PCI devices" on bottom of the edit VM page. I suspect this was part of the problem @klingon00 described, the other part being the AMD reset bug causing his GPU to hang after having a VM crash and having to force stop. BTW, Klingon00, I would manually check your hackingtosh XML, as I know with my setup based on a Spaceinvader One tutorial, if you change anything at all from the GUI menu it deletes some of the special QEMU arguments that let the MAC boot. Now, what I'm getting is my two windows VM's with nvidia cards passed through still work fine, but I've tried to passthtough the secondary card to a Mac VM and several linux distros including the latest stable Ubuntu 18.04 LTS, and all will apparently crash on boot and just give me a black screen/no signal. The monitor will actually go to low power mode, and I can't remote in via splashtop, so I don't think anything is actually booting. It seems like this all could be related to Ryzen 3000 BIOS update issues, but if anyone has any hints for me about why GPU passthrough would work for windows and not linux/mac, that would be awesome. I think the next thing I will do is try passing through GPU on linux VMs with different machine types and switching between SeaBIOS and OVMF. Sorry for the novel, but I'm really suspicious that all these different issues have the same root cause..

Hey @wesker316, sorry for digging this one out of the grave, but your script idea looks like exactly what I was looking for. I'm a total linux noob though... I tried running the script from the /boot folder as you suggested, but got permissions errors. Ran chmod -x switchvm.sh and still wouldn't run, so I moved it to my domains folder, and after doing chmod -x again it at least ran, but i get the error "error: Failed to get option 'domain': Option argument is empty". WOuld you be able to enlighten me on how the VM-1 & VM-2 paramter works (am i supposed to put the full vm name here?), and anything else I might be doing wrong? Thank a lot!

@bland328 I'm using VMXNET3 on the 6.8.0 RC9 build. Seems to be working well still, including iMessage. I don't think i tried the e1000 NIC after switching to RC9, since everything just started working, but I know none NIC options were working before the update, for one reason or another. I was looking into using other kexts as well, but didn't end up trying it before moving to the RC. I have my mac VM set up as a Q35-3.1 machine, if that makes a difference.

I was having the exact same issue as OP, and updating Unraid to 6.8.0 RC9 resolved it. Before that, I tried switching from VMXNET3 (which was working minus apple server connectivity) to e1000-82545em, which just gave me a never ending beach ball. Haven't tried imessage, but app store is working.