PUNGGOKERS

A lot of anti-cheat engine can be bypass now, we have plenty of resources in this sub-topic. Edit: leaving this here

Thanks for these comments, it kind of helped me because vantec dual controller already disappointed me.

Could be, it's easier to tell if you have diagnostics that we can review. But usually it's just a VM quirk.

Have you tried running the VM without the sound card?

Try not to passthrough the Audio if that works. Edit: Or try not to add the sound card in the VM settings.

<smbios mode='host'/>This one made me play Warhammer 40k Space Marine 2.

Some cards are quirky, or maybe it's the motherboard. My RTX 4060 and 5050 doesn't want my GPU to be binded with its sound card.

It will be great if you can post your diagnostics or syslog. It will help us see what is going on. Can you also share you XML?

MB: MSI Z890-A WIFI It works but bad USB Controller, all USB are in one controller IOMMU, Resize BAR, and other needed functions for VM is good! You may end up with D3cold state with your GPU if you passthrough it to your VM. It has 4 M.2 slots and 4 DDR5 Ram slots GPU: RTX 5050 and RTX 4060 Supported, just had some quirk, if you end up with D3cold state, there are instructions in this forum from me.

Add your diagnostics.

Refer to this:

Try removing the sound card, only passthrough the GPU.

I would like to see your XML.

Add this between the <clock> </clock> Let me know if it helps. <timer name='tsc' present='yes' mode='native'/>

Glad you worked it out yourself. This happens when you don't set your BIOS at the initial stage of your VM setup. Few things to as a reminder when setting up your VM, here are what you need to look for in BIOS, depending on what type of motherboard you have: Above 4G Decoding - Enabled Resizable BAR - Enabled IOMMU - Enabled Intel VT-D/ AMD-Vi - Enabled SVM(AMD) - Enabled ACS (ACS Override or PCIe ACS) - Enabled VT-x - Enabled Some of these will not appear in your BIOS, and some will, chances are they are already enabled, just hiding.

I can't visualize what is happening. Can type this in the terminal BEFORE and AFTER you run the VM. Tell me what you see. dmesg | grep -i vfio

For Unknown PCI Header Type 127 - D3cold state Adding this in the append line and running VM with only Primary GPU without sound card should fix it. vfio-pci.disable_idle_d3=1 # Prevent GPU power state issues - This prevents the D3cold state.

This should be pinned on the top of this forum.

The problem: Unknown PCI Header type 127. Cause, according to SpaceInvaderOne, the reason this happens is when GPU is abruptly shutdown, the only way to fix this is to restart the server or use his script (which works btw). However, the problem remains when we run the VM and gives the same message again. Possible Solutions in Append line: vfio-pci.disable_idle_d3=1 # Prevent GPU power state issues - This prevents the D3cold state. ---- vfio-pci.ids=xxxx:xxxx,xxxx:xxxx # Bind your GPU + audio to VFIO video=efifb:off # Disable EFI framebuffer pcie_aspm=off # Disable PCIe power management pci=noats # Disable Address Translation Services intel_iommu=on iommu=pt # Enable IOMMU passthroughAfter adding the vfio-pci.disable_idle_d3=1 to the append line, this what it should look like if you run this in the terminal: dmesg | grep -i vfio root@Punggokers:~# dmesg | grep -i vfio [ 0.000000] Command line: BOOT_IMAGE=/bzimage isolcpus=0-17 vfio-pci.ids=10de:2882,10de:22be vfio-pci.disable_idle_d3=1 video=efifb:off pcie_aspm=off intel_iommu=on iommu=pt initrd=/bzroot [ 0.088917] Kernel command line: BOOT_IMAGE=/bzimage isolcpus=0-17 vfio-pci.ids=10de:2882,10de:22be vfio-pci.disable_idle_d3=1 video=efifb:off pcie_aspm=off intel_iommu=on iommu=pt initrd=/bzroot [ 1.779123] VFIO - User Level meta-driver version: 0.3 [ 1.779152] vfio-pci 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none [ 1.779190] vfio-pci 0000:82:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none [ 1.779223] vfio_pci: add [10de:2882[ffffffff:ffffffff]] class 0x000000/00000000 [ 1.779330] vfio_pci: add [10de:22be[ffffffff:ffffffff]] class 0x000000/00000000 [ 34.475709] vfio-pci 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none [ 34.475711] vfio-pci 0000:82:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none root@Punggokers:~#This tells us that the GPU and Audio is properly binded and is now ready to be in a VM. The next problem you'll encounter is if you put your GPU + Audio as your primary GPU and Audio, and run the VM you'll probably get a BLACK SCREEN. type this in the terminal dmesg | grep -i vfio after running the VM and you should probably get the following below : root@Punggokers:~# dmesg | grep -i vfio [ 0.000000] Command line: BOOT_IMAGE=/bzimage isolcpus=0-17 vfio-pci.ids=10de:2882,10de:22be vfio-pci.disable_idle_d3=1 video=efifb:off pcie_aspm=off intel_iommu=on iommu=pt initrd=/bzroot [ 0.089377] Kernel command line: BOOT_IMAGE=/bzimage isolcpus=0-17 vfio-pci.ids=10de:2882,10de:22be vfio-pci.disable_idle_d3=1 video=efifb:off pcie_aspm=off intel_iommu=on iommu=pt initrd=/bzroot [ 1.769221] VFIO - User Level meta-driver version: 0.3 [ 1.769254] vfio-pci 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none [ 1.769293] vfio-pci 0000:82:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none [ 1.769323] vfio_pci: add [10de:2882[ffffffff:ffffffff]] class 0x000000/00000000 [ 1.769451] vfio_pci: add [10de:22be[ffffffff:ffffffff]] class 0x000000/00000000 [ 34.399695] vfio-pci 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none [ 34.399697] vfio-pci 0000:82:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none [ 404.394745] vfio-pci 0000:01:00.1: enabling device (0000 -> 0002) [ 405.546733] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 405.546845] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 406.266298] vfio-pci 0000:01:00.0: timed out waiting for pending transaction; performing function level reset anyway [ 407.426295] vfio-pci 0000:01:00.0: not ready 1023ms after FLR; waiting [ 408.514290] vfio-pci 0000:01:00.0: not ready 2047ms after FLR; waiting [ 410.626281] vfio-pci 0000:01:00.0: not ready 4095ms after FLR; waiting [ 414.850269] vfio-pci 0000:01:00.0: not ready 8191ms after FLR; waiting [ 423.554237] vfio-pci 0000:01:00.0: not ready 16383ms after FLR; waiting [ 440.450175] vfio-pci 0000:01:00.0: not ready 32767ms after FLR; waiting [ 476.290040] vfio-pci 0000:01:00.0: not ready 65535ms after FLR; giving up [ 476.572567] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.572721] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.584156] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.584312] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.593936] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.594092] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.599060] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.599552] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.605684] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.605820] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.605841] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.605867] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.605965] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.605986] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.606064] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.606084] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.615625] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.615761] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.620394] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.620493] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.620514] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.620612] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.640481] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.640665] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs [ 476.708380] vfio-pci 0000:01:00.0: vfio_bar_restore: reset recovery - restoring BARs [ 476.708556] vfio-pci 0000:01:00.1: vfio_bar_restore: reset recovery - restoring BARs root@Punggokers:~# This will give us an FLR issue: The VFIO logs show that the GPU is having serious reset issues - it's failing to complete a Function Level Reset (FLR) and timing out after 65+ seconds. The solution, when you create a VM, only put the Primary Graphics Card, NO SOUND CARD, and it should run without a black screen and should boot properly. This may be a quirk of the consumer cards, but at least it should work. Warning: You need to have an iGPU on top of your primary GPU. I tried running unraid with one GPU, it will still give you a black screen. Make sure Unraid uses your iGPU or something else. Unraid must absolutely not use your VM GPU.

I was reading your log, you are at the same ditch as me, try adding that in your append line, it may start working.

Did you ever try to use this in the append line: vfio-pci.disable_idle_d3=1 This will prevent the GPU to go to d3cold before even attempting to turn on the VM. My issue was I can't even open the VM because it automatically goes to d3cold which gives the unknow pci header type 127. I was able to run the VM but I am currently in black screen now. Let me know if you tried that one.

For VM specifically, gaming. I bought RTX 5050 last week and could not get it to work despite of the instructions in the docs and forums. So I ended up returning it and got myself a RTX 4060. I was wondering this could've been avoided if I knew that RTX 5050 has not been tested/proven working by anyone in here. I saw RTX 4060 out here working for a few people so I figured I should get this instead as it has the same price range.

I was looking in reddit and forums and I can't seem to find a list of proven working GPU's for Unraid. I am not sure if this affects what type of MB you should have as well, can we create a list like this? Is what I am asking more complex than it should be?

Hey, I was in the same ditch as you, but mine was RTX 5050. There are issues with it. I am depressed and returned it and bought an RTX 4060. I guess we will have to wait until 5000 series is fully supported for unraid.