mafoster

@JorgeB I will try that, thank you. @trurl sorry it was an honest mistake that came out of the new "My Servers" feature where I have a separate account/email for that and accidentally posted logged into that account vs my forum account.

@JorgeB Thank you for the suggestion. Unfortunately that change did not solve my issue. Any other suggestions?

Replying from my usual account. Hi JorgeB, I don't think the Ryzen lock up issue is the cause of this as this server was running fine for years and this is a newer issue. I tried leaving the server with Dockers off for a few weeks and no crash happened during this time. I then turned back Docker back on and turned one docker app on at a time to see which causes it. Plex had no issue. It really is when SabNZB and Sonarr download content. Once the downloads finish, sometimes the server comes back from the dead, but everything hangs until then and most times I need to do a hard restart. I have reinstalled all the Docker apps without templates with no success. I am really stumped on this one and would really appreciate some help. I have attached the latest diagnostics. Thanks. diagnostics-20230107-2358.zip

@Endy great guide. Do you happen to know where the USB 2.0 headers sit in the IOMMU groups? I am trying to install a PCIe wifi/bluetooth card for my VM and the bluetooth portion isn't being reconsigned at all. The PCIe card has a cable that runs to a USB header on the board. I suspect I am passing through the PCIe card but not the USB 2.0 header that the card is connected to, and its failing to work. Any idea?

Thank you Ed for another amazing update! Getting easier by the update. Since the upgrade from the Clover to Opencore version from Catelina to Big Sur, I have been having fairly consistent crashes or kernel panics that do not stop the VM, it just hangs until I force close the VM so its hard to know what is causing it. It generally just goes to a black screen and isn't rebooting like it typically would. Everything works great in the VM except for these regular crashes. I wanted to see if anyone else is having this issue and what I could do to identify the root cause? I am running the following: MacOS 11.1 ASRock X570 Taichi AMD Ryzen 9 3950X 48 GiB DDR4 Multi-bit ECC MSI Radeon RX 570 8 GB UNRAID 6.8.3 I have pinned the CPU with 12 core and 32GB for the VM.

Hi everyone, @SpaceInvaderOne thanks for making an amazing docker! I recently migrated my Intel i5 server to a new Ryzen board and CPU and it hasn't been as a simple to get my Mac OS VM working. I have finally gotten my MSI Radeon RX 570 to passthrough, however I seem to get stuck on the Apple logo on boot for Catalina and cannot seem to figure out how to get passed it. It doesn't even show the progress bar. There is nothing I can see in my logs that hint at what the issue is. I have tried a clean install and get the same issue. My hardware is the ASRock X570 Taichi with Ryzen 9950X Below is my XML and attached is my server diagnosis file: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacinaboxCatalina</name> <uuid>483b033b-dafb-4ded-aac1-86fae9be9316</uuid> <description>MacOS Catalina</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="Catalina"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='10'/> <vcpupin vcpu='1' cpuset='26'/> <vcpupin vcpu='2' cpuset='11'/> <vcpupin vcpu='3' cpuset='27'/> <vcpupin vcpu='4' cpuset='12'/> <vcpupin vcpu='5' cpuset='28'/> <vcpupin vcpu='6' cpuset='13'/> <vcpupin vcpu='7' cpuset='29'/> <vcpupin vcpu='8' cpuset='14'/> <vcpupin vcpu='9' cpuset='30'/> <vcpupin vcpu='10' cpuset='15'/> <vcpupin vcpu='11' cpuset='31'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader> <nvram>/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='12' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/Clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/Catalina-install.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/macos_disk.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:2e:de:16'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' slot='0x00' function='0x0'/> </source> <rom file='/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/MSI.RX570.8192.180304.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x05ac'/> <product id='0x024f'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0043'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value=DELETED <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain> Any thoughts on what could be causing this? fosterserver-diagnostics-20200207-2259.zip

Thanks @Endy. I have tried everything in that @SpaceInvaderOne video but still get a blank screen on boot, the fan start on the GPU and get the error I mentioned in this post: Anyone else that could suggest something?

@Endy thank you for this very detailed guide. I have about the same configuration (ASRock X570 Taichi with 3950x) except that I have an AMD Radeon RX 570, and followed your instructions, and after many tries I haven't been able to get my GPU to passthrough correctly - I just get a black screen. I have also tried an Nvidia GTX 950 with the same results. I am on the latest bios version 2.70. I have posted thread about my issue and wanted to see if you could help?

@david279 I have removed the +pcid from the VM XML and stubbed the GPU using the VFIO-PCI CFG plugin and also adjusted the linuxsys to the following: label unRAID OS menu default kernel /bzimage append pcie_acs_override=downstream isolcpus=6-15,22-31 video=efifb:off pci=noaer initrd=/bzroot I added pci=noaer in addition to moving the video=efifb:off before the initrt as you mentioned. I am still not getting it to work but the amount of errors are reducing: -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-02-06 01:22:11.894+0000: Domain id=2 is tainted: high-privileges 2020-02-06 01:22:11.894+0000: Domain id=2 is tainted: custom-argv 2020-02-06 01:22:11.894+0000: Domain id=2 is tainted: host-cpu Any further ideas? Attached is my latest diagnostics files. fosterserver-diagnostics-20200205-2028.zip

Hi @david279, thank you for your help. What do you mean by stub the GPU? How would I go about in doing that?

Hi everyone, I have just migrated my Intel i5 6500 build to a new Ryzen build with the below hardware and haven't been able to figure out why my Mac OS Catalina VM is not allowing me to pass through my GPU. Hardware: ASRock X570 Taichi AMD Ryzen 3950X AMD Radeon RX 570 Unlike my previous Intel server, my monitor seems to show the UNRAID OS boot details on my monitor through my AMD Radeon RX 580 despite having video=efifb:off in my linuxsys configuration as follows: kernel /bzimage append pcie_acs_override=downstream isolcpus=6-15,22-31 initrd=/bzroot video=efifb:off I used @SpaceInvaderOne 's amazing Macinabox Docker as I usually have to build the Mac OS VM but seem to get stuck. The VM boots but now video appears aside from a black screen and the following log appears: 2020-02-05 01:50:36.083+0000: Domain id=7 is tainted: custom-argv 2020-02-05 01:50:36.083+0000: Domain id=7 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2020-02-05T01:50:36.106188Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.108014Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.108708Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.109366Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.110033Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.110706Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.111406Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.112062Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.112908Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.113615Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.114287Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.114963Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.115624Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.116318Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.117019Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.117708Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.118377Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.119080Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.119757Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:36.120423Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2020-02-05T01:50:37.720601Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0e:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest 2020-02-05T01:50:37.720695Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0e:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest As you can see from the above, there is "vfio_err_notifier_handler" that appears to reference my GPU. Here is my XML for my VM: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='4' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacinaboxCatalina</name> <uuid>16c4990b-e509-4928-ac06-72cc5857b010</uuid> <description>MacOS Catalina</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="Catalina"/> </metadata> <memory unit='KiB'>33030144</memory> <currentMemory unit='KiB'>33030144</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>20</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='22'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='23'/> <vcpupin vcpu='4' cpuset='8'/> <vcpupin vcpu='5' cpuset='24'/> <vcpupin vcpu='6' cpuset='9'/> <vcpupin vcpu='7' cpuset='25'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='26'/> <vcpupin vcpu='10' cpuset='11'/> <vcpupin vcpu='11' cpuset='27'/> <vcpupin vcpu='12' cpuset='12'/> <vcpupin vcpu='13' cpuset='28'/> <vcpupin vcpu='14' cpuset='13'/> <vcpupin vcpu='15' cpuset='29'/> <vcpupin vcpu='16' cpuset='14'/> <vcpupin vcpu='17' cpuset='30'/> <vcpupin vcpu='18' cpuset='15'/> <vcpupin vcpu='19' cpuset='31'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/16c4990b-e509-4928-ac06-72cc5857b010_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='20' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/Clover.qcow2' index='3'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/Catalina-install.img' index='2'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/macos_disk.img' index='1'/> <backingStore/> <target dev='hde' bus='sata'/> <alias name='sata0-0-4'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:98:49:a6'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-MacinaboxCatalina/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain> Any help would be greatly appreciated to help get me up and running again in Mac OS. Thanks in advance. fosterserver-diagnostics-20200204-2222.zip

@Leoyzen when you say add pci=noaer , do you mean to the syslinux? did this solve your GPU passthrough issue on your X570 board?

Thanks for the info @johnsanc After long debates with myself and researching boards, I ended up going with the ASRock X570 Taichi as it appears to be more documented on this forum. Plus I got my board for much less than this one. May add a TB3 and 10GBe card down the road however which should make the passthrough a bit easier.

Hi everyone Looking to upgrade my current Unraid server that I have been using for Plex and a MacOS VM. Given the performance on my old 6th gen Intel i5, I’m looking to upgrade to a Ryzen 3rd gen and thinking of getting the ASRock X570 Creator for its 10Gbe Ethernet and Thunderbolt 3. Curious if anyone has tried this motherboard and can report on what worked and want hasn’t in terms of pass through, ideally for MacOS. I would also like to see if someone can provide the IMMO groups. thanks in advance!

Hi everyone, I managed to setup a new VM with High Sierra but seem to be having issues booting now. All my VMs get stuck on the first black screen with the TianoCore logo. Any idea why that would be? I am running 6.4.0_rc14 and everything was working at one point and as I changed something in the EFI and rebooted, this happened. I tried restarting a new VM and creating a new vdisk for High Sierra without success. Here is what is generated in the logs when I start the VM: 2017-11-28 04:33:16.419+0000: Domain id=9 is tainted: high-privileges 2017-11-28 04:33:16.419+0000: Domain id=9 is tainted: custom-argv 2017-11-28 04:33:16.419+0000: Domain id=9 is tainted: host-cpu 2017-11-28T04:33:16.457300Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2017-11-28T04:33:19.867966Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism. 2017-11-28T04:33:20.933148Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism. Any idea?

Fixed my issue after changing my static IP. Strange but works now. Thanks.

Hi Squid, you are are right, I forgot I had to do this at boot. I have managed to login in GUI mode but it appears to not be connected to not be connect to the network and/or internet despite not showing any noticeable errors. Any idea?

I upgraded to 6.3.5 and have been unable to connect to my server via SSH or via the browser UI with all shares not working. Strangely the only thing that works is my MacOS VM through VGA passthrough that I have setup to automatically launch. I can't do anything else. I can't even see the UI if I plug a monitor to it. Any idea how I can solve this? First upgrade that's gone wrong.

I have been using the Sound Blaster Omni Surround 5.1 USB sound card. Works great

The group 7 has a device that starts with 00: Devices that start with 00: such as 00:1d.0 are generally built into the motherboard so as such can't be physically moved elsewhere Devices that start with another number such as 02:00.0 are discrete devices. Exactly it's a PCI-E root port, it usually corresponds to a PCI-E slot on the motherboard in my experience, if he finds it and install the USB controller in that slot he would be able to pass it to the VM. Thanks bubbl3 and gridrunner. Unfortunately I only have two PCIe slots (1 x16 and 1 x4), one for VGA and the other for this card so cannot try another. Is there any way to break the group manually? Bad design by SuperMicro... Alternatively, is there any way you see me being able to passthrough one of my integrated USB controllers (I have two as you can see from my PCI list)? What happens when you try to pass this one that is in your group 3? 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) bubbl3 your suggestion in addition to upgrading to 6.3-r5 worked. Thank you. It seems like 6.3 does a way better job of separating the groups.

The group 7 has a device that starts with 00: Devices that start with 00: such as 00:1d.0 are generally built into the motherboard so as such can't be physically moved elsewhere Devices that start with another number such as 02:00.0 are discrete devices. Exactly it's a PCI-E root port, it usually corresponds to a PCI-E slot on the motherboard in my experience, if he finds it and install the USB controller in that slot he would be able to pass it to the VM. Thanks bubbl3 and gridrunner. Unfortunately I only have two PCIe slots (1 x16 and 1 x4), one for VGA and the other for this card so cannot try another. Is there any way to break the group manually? Bad design by SuperMicro... Alternatively, is there any way you see me being able to passthrough one of my integrated USB controllers (I have two as you can see from my PCI list)?

Any help anyone? Thanks.

Hi everyone, I just got a PCIe USB 3.1 Card (http://www.newegg.ca/Product/Product.aspx?Item=9SIA93K4TK4521&_ga=1.219933210.2007223919.1409504610) so I can more easily passthrough a USB card in my Windows 10 and MacOS VMs and haven't been able to because of how my IOMMU groups are setup even with PCIe ACS Override turned on. My group 6 has a lot of integrated items in it. Any suggestions? Here is the card I am trying to passthrough: 02:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242] When I start the Windows 10 VM, I get a group error. Here is my PCI Devices: 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:191f] (rev 07) 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) 00:16.3 Serial controller [0700]: Intel Corporation Sunrise Point-H KT Redirection [8086:a13d] (rev 31) 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #6 [8086:a115] (rev f1) 00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #7 [8086:a116] (rev f1) 00:1c.7 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #8 [8086:a117] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a149] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-LM [8086:15b7] (rev 31) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:0fba] (rev a1) 02:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242] 3b:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03) 3c:00.0 PCI bridge [0604]: Tundra Semiconductor Corp. Device [10e3:8113] (rev 01) 3e:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242] IOMMU Groups: /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:02.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.2 /sys/kernel/iommu_groups/4/devices/0000:00:16.0 /sys/kernel/iommu_groups/4/devices/0000:00:16.3 /sys/kernel/iommu_groups/5/devices/0000:00:17.0 /sys/kernel/iommu_groups/6/devices/0000:00:1c.0 /sys/kernel/iommu_groups/6/devices/0000:00:1c.5 /sys/kernel/iommu_groups/6/devices/0000:00:1c.6 /sys/kernel/iommu_groups/6/devices/0000:00:1c.7 /sys/kernel/iommu_groups/6/devices/0000:02:00.0 /sys/kernel/iommu_groups/6/devices/0000:3b:00.0 /sys/kernel/iommu_groups/6/devices/0000:3c:00.0 /sys/kernel/iommu_groups/6/devices/0000:3e:00.0 /sys/kernel/iommu_groups/7/devices/0000:00:1d.0 /sys/kernel/iommu_groups/8/devices/0000:00:1f.0 /sys/kernel/iommu_groups/8/devices/0000:00:1f.2 /sys/kernel/iommu_groups/8/devices/0000:00:1f.3 /sys/kernel/iommu_groups/8/devices/0000:00:1f.4 /sys/kernel/iommu_groups/9/devices/0000:00:1f.6 /sys/kernel/iommu_groups/10/devices/0000:01:00.0 /sys/kernel/iommu_groups/10/devices/0000:01:00.1

Hi everyone, Any ideas on what could help fix my problem? Thanks No your id for the gpu is the same. So it should be fine. Questions. 1. So when you start the vm do you get anything show on the screen at all, before the osx starts loading or is the screen black all the time. 2. Is your igpu set as the primary graphics card for unRAID. (if you connect the monitor to the integrated graphics on motherboard you should see the console. If not please set your motherboard bios for onboard to be primary. One thing you could try is to change the installation to ovmf and use clover as bootloader. To see how please check the second video here.http://lime-technology.com/forum/index.php?topic=51915.0 Hi I dont think that you are going to be able to get onboard sound working. The sound chipset must be supported by osx, so it think it will be very difficult to achieve. Why not use the hdmi sound from the gpu? download this file . https://www.dropbox.com/s/tbyyaufc5elss22/HDMIAudio-1.0.dmg?dl=0 its a dmg file so mount it in the vm then run in terminal cd /Volumes/HDMIAudio then ./install.sh if it doesnt work that why then try copying the kext file out of the dmg and then open the efi partition and paste it in efi/clover/kexts/other reboot and you should have sound Sent from my iPhone using Tapatalk

Hi everyone, I recently setup a Mac OS X VM and Windows 10 VM and haven't been able to get a USB sound card (Creative Sound Blaster Omni 5.1 Surround) to pass through both VMs. Although I don't get any errors that prevent the VM to start, the following error shows up in the logs. I tried plugging in the sound card in a USB 2.0, 3.0 and 3.1 port with all the same result. Any idea as to what could solve this to make the sound card work? Thanks! Domain id=47 is tainted: custom-argv Warning: speed mismatch trying to attach usb device "SB Omni Surround 5.1" (high speed) to bus "usb.0", port "2.3" (full speed) 2016-11-22T02:06:28.565480Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "SB Omni Surround 5.1" (high speed) to bus "usb.0", port "2.3" (full speed) 2016-11-22T02:06:35.954441Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "SB Omni Surround 5.1" (high speed) to bus "usb.0", port "2.3" (full speed) PCI Devices: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 034: ID 1532:0043 Razer USA, Ltd Bus 001 Device 033: ID 05ac:9222 Apple, Inc. Bus 001 Device 032: ID 05ac:9130 Apple, Inc. [color=green]Bus 001 Device 037: ID 041e:322c Creative Technology, Ltd [/color]Bus 001 Device 027: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub