ghost82

mmm I don't know, can you paste the full backtrace? Once you reboot a window should popup, click on show details and paste all here, it should be something like this: panic(cpu 0 caller 0xffffff8006262e0a): Kernel trap at 0xffffff7f8998c7ce, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000001badf000, CR4: 0x00000000003626e0 RAX: 0x0000000000000000, RBX: 0xffffff9124ef5000, RCX: 0xffffff8006aa30a0, RDX: 0x0000000000000000 RSP: 0xffffff9124e7bd10, RBP: 0xffffff9124e7bd20, RSI: 0xffffff802d320240, RDI: 0xffffff9124ef5000 R8: 0x0000000000000000, R9: 0x0000000000000004, R10: 0x0000000000000051, R11: 0xffffff8028537000 R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0xffffff9124ef5000, R15: 0xffffff802e5a2000 RFL: 0x0000000000010282, RIP: 0xffffff7f8998c7ce, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffff9124e7b770 : 0xffffff8006139a3b 0xffffff9124e7b7c0 : 0xffffff8006270fe5 0xffffff9124e7b800 : 0xffffff8006262a5e 0xffffff9124e7b850 : 0xffffff80060e0a40 0xffffff9124e7b870 : 0xffffff8006139127 0xffffff9124e7b970 : 0xffffff800613950b 0xffffff9124e7b9c0 : 0xffffff80068d17f9 0xffffff9124e7ba30 : 0xffffff8006262e0a 0xffffff9124e7bbb0 : 0xffffff8006262b08 0xffffff9124e7bc00 : 0xffffff80060e0a40 0xffffff9124e7bc20 : 0xffffff7f8998c7ce 0xffffff9124e7bd20 : 0xffffff7f8998c916 0xffffff9124e7bd40 : 0xffffff7f89980531 0xffffff9124e7bd60 : 0xffffff7f8998044f 0xffffff9124e7bd80 : 0xffffff7f8995e45d 0xffffff9124e7bdb0 : 0xffffff7f8995c92b 0xffffff9124e7bde0 : 0xffffff800681a336 0xffffff9124e7be40 : 0xffffff8006819ee1 0xffffff9124e7bef0 : 0xffffff800681922e 0xffffff9124e7bf50 : 0xffffff800681b9cd 0xffffff9124e7bfa0 : 0xffffff80060e013e Kernel Extensions in backtrace: com.apple.driver.AppleIntelSKLGraphics(14.0.2)[11074779-5CB6-3C9C-98F4-7F745CDCFDE0]@0xffffff7f89951000->0xffffff7f89a43fff dependency: com.apple.iokit.IOPCIFamily(2.9)[AA7C7A4F-9F5D-3533-9E78-177C3B6A72BF]@0xffffff7f86ea2000 dependency: com.apple.iokit.IOSurface(269.6)[39DC4195-B168-3895-ACD5-E731581855F8]@0xffffff7f877e7000 dependency: com.apple.iokit.IOGraphicsFamily(568)[247C211E-C250-351C-BCE2-4DB9D3003E10]@0xffffff7f8935f000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.2.7)[72B8A0B5-E12C-3764-9187-0AC0E93416F9]@0xffffff7f893b0000 BSD process name corresponding to current thread: kernel_task Boot args: dart=0 nv_disable=1 -v Mac OS version: 19B88 Kernel version: Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 Kernel UUID: 7503CD47-851F-321E-8747-50DB4299165F Kernel slide: 0x0000000005e00000 Kernel text base: 0xffffff8006000000 __HIB text base: 0xffffff8005f00000 System model name: iMac17,1 (Mac-B809C3757DA9BB8D) System shutdown begun: NO Panic diags file available: YES (0x0) System uptime in nanoseconds: 173374690057 last loaded kext at 79505135625: >!AGraphicsDevicePolicy 4.5.9 (addr 0xffffff7f89c03000, size 86016) last unloaded kext at 62534305083: >!A!ILpssGspi 3.0.60 (addr 0xffffff7f8847b000, size 45056) loaded kexts: com.insanelymac.RealtekRTL8111 2.3.0d7 com.rehabman.driver.USBInjectAll 0.7.1 org.netkas.driver.FakeSMC 1800 >!AGraphicsDevicePolicy 4.5.9 @AGDCPluginDisplayMetrics 4.5.9 >!AHV 1 |IOUserEthernet 1.0.1 |IO!BSerialManager 7.0.1f1 >!AUpstreamUserClient 3.6.8 >!AMCCSControl 1.13 >AGPM 111.2.5 >X86PlatformShim 1.0.0 >!APlatformEnabler 2.7.0d0 >pmtelemetry 1 >!AHDAHardwareConfigDriver 283.14 >!A!ISKLGraphics 14.0.2 @Dont_Steal_Mac_OS_X 7.0.0 >!AHDA 283.14 >!A!IPCHPMC 2.0.1 >ACPI_SMC_PlatformPlugin 1.0.0 >!A!ISKLGraphicsFramebuffer 14.0.2 >!AFIVRDriver 4.1.0 >!A!ISlowAdaptiveClocking 4.0.0 @filesystems.autofs 3.0 @filesystems.ntfs 3.14.3 @fileutil 20.036.15 @filesystems.apfs 1412.41.1 >!AVirtIO 1.0 @filesystems.hfs.kext 522.0.9 @!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1 @BootCache 40 @!AFSCompression.!AFSCompressionTypeZlib 1.0.0 >!AAHCIPort 341.0.2 @private.KextAudit 1.0 >!ARTC 2.0 >!AACPIButtons 6.1 >!AHPET 1.8 >!ASMBIOS 2.1 >!AAPIC 1.7 $!AImage4 1 @nke.applicationfirewall 303 $TMSafetyNet 8 @!ASystemPolicy 2.0.0 |EndpointSecurity 1 >!AGraphicsControl 4.5.9 |IOAVB!F 800.17 >!ASSE 1.0 |IO!B!F 7.0.1f1 |IO!BPacketLogger 7.0.1f1 >!ASMBus!C 1.0.18d1 |IOSMBus!F 1.1 >DspFuncLib 283.14 @kext.OSvKernDSPLib 529 |IONDRVSupport 568 >IOPlatformPluginLegacy 1.0.0 @!AGPUWrangler 4.5.9 >!AHDA!C 283.14 |IOHDA!F 283.14 |IOAudio!F 300.2 >!A!ILpssGspi 3.0.60 >usb.IOUSBHostHIDDevice 1.2 >!ASMBusPCI 1.0.14d1 @!AGraphicsDeviceControl 4.5.9 |IOAccelerator!F2 438.2.7 |IOGraphics!F 568 >X86PlatformPlugin 1.0.0 >IOPlatformPlugin!F 6.0.0d8 |IOSlowAdaptiveClocking!F 1.0.0 @plugin.IOgPTPPlugin 810.1 |IOEthernetAVB!C 1.1.0 |IOSkywalk!F 1 @kext.triggers 1.0 |IOAHCIBlock!S 316.40.3 @vecLib.kext 1.2.0 >usb.networking 5.0.0 >usb.!UHostCompositeDevice 1.2 >usb.!UHub 1.2 |IOSerial!F 11 |IOSurface 269.6 @filesystems.hfs.encodings.kext 1 |IOAHCI!F 290.0.1 >usb.!UXHCIPCI 1.2 >usb.!UXHCI 1.2 >usb.!UHostPacketFilter 1.0 |IOUSB!F 900.4.2 >!AEFINVRAM 2.1 >!AEFIRuntime 2.1 |IOHID!F 2.0.0 $quarantine 4 $sandbox 300.0 @kext.!AMatch 1.0.0d1 >DiskImages 493.0.0 >!AFDEKeyStore 28.30 >!AEffaceable!S 1.0 >!AKeyStore 2 >!UTDM 489.41.1 |IOSCSIBlockCommandsDevice 422.0.2 >!ACredentialManager 1.0 >KernelRelayHost 1 >!ASEPManager 1.0.1 >IOSlaveProcessor 1 |IOUSBMass!SDriver 157.40.7 |IOSCSIArchitectureModel!F 422.0.2 |IO!S!F 2.1 |IOUSBHost!F 1.2 >!UHostMergeProperties 1.2 >usb.!UCommon 1.0 >!ABusPower!C 1.0 |CoreAnalytics!F 1 >!AMobileFileIntegrity 1.0.5 @kext.CoreTrust 1 |IOTimeSync!F 810.1 |IONetworking!F 3.4 |IOReport!F 47 >!AACPIPlatform 6.1 >!ASMC 3.1.9 >watchdog 1 |IOPCI!F 2.9 |IOACPI!F 1.4 @kec.pthread 1 @kec.corecrypto 1.0 @kec.Libm 1

When you booted again there should be some more data on that window, you should be able to see what crashed.

it's different if you use a virtual or vfio gpu, amount of ram is different; they both work with virtual but I think you were at limit..

No, that's not how initial memory works; you couldn't run both vms with gpus because the amount of reserved ram was 32+32 (at boot systems use max memory, then you need a balloon driver in the guest and manually assign memory to the host or something else to do it automatically if you want dynamic memory), system log should had reported out of system memory. By decreasing to 16 you are able to run both vms (16+16 or 16+32). Take into account that unraid needs some ram too.

so is it solved? perfect I didn't notice the comma, which as you understood must not be there

Save diagnostics after plugging hdmi cable, booting unraid and running the vm; from your description you will have a black screen. Stop the vm and save diagnostics. Attach the zip here.

It should be possible to leave the hdmi plugged in and: 1. bind to vfio the gpu (both audio, video and usb controller parts, if any) 2. if booting unraid with efi, prevent efifb to attach to the gpu (video=efifb:off in syslinux config)

I never used bitlocker so I really don't know how it works, what I know is that it encrypts the drive. It could be possible that changing the hardware in the vm makes the drive inaccessible. If you can access the vm with vnc and unlock the drive try to deactivate bitlocker, do your hardware changes, make sure it works without bitlocker, then reactivate it. See here for example: https://social.technet.microsoft.com/Forums/windows/en-US/09caca79-76bf-4e70-81c3-ad8cb4da40e1/bitlocker-and-hardware-modification-best-practice-?forum=w7itprosecurity From your signature I see you have a 12700 cpu: as far as I know igpu passthrough for this cpu is still unsupported because of intel drivers, but I'm not 100% sure. If this is true, to have acceleration you need a dGPU installed and passed through, with a server (vnc, or parsec, or etc) configured INSIDE the vm, so the only graphic configured for the vm is the dGPU. Then you can connect from a second device with the vnc/parsec client and you will stream accelerated contents. You should not need any dummy plug or monitor connected to the vm, I have a second box with an nvidia gpu running in a windows 11 vm without any monitor nor dummy plug connected.

diagnostics after trying to run both vms.

in unraid terminal: cat /proc/iomem if in the output you read efifb attached to the address of the gpu it means efifb is in use.

For lags using ioapic kvm driver may help, just add this line before </features> <ioapic driver="kvm"/>

yes, first gpu at 01:00.0/1 is flagged as boot vga, so you must have a vbios for that.

you are out of memory! (I didn't notice it in the first diagnostics) Jan 3 15:58:08 visionserver kernel: Out of memory: Killed process 10811 (qemu-system-x86) total-vm:65246480kB, anon-rss:63859640kB, file-rss:8kB, shmem-rss:24688kB, UID:0 pgtables:125152kB oom_score_adj:0 then you have several kernel panics. Try 32 Gb ram in the vm.

Can you try one step at a time?Try to passthrough the secondary 3060, just paste this: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>mona</name> <uuid>3f25e14d-e01b-b04c-05e4-8ea31610d531</uuid> <description>virtual machine mona</description> <metadata> <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>65011712</memory> <currentMemory unit='KiB'>65011712</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='11'/> <vcpupin vcpu='8' cpuset='4'/> <vcpupin vcpu='9' cpuset='12'/> <vcpupin vcpu='10' cpuset='5'/> <vcpupin vcpu='11' cpuset='13'/> <vcpupin vcpu='12' cpuset='6'/> <vcpupin vcpu='13' cpuset='14'/> <vcpupin vcpu='14' cpuset='7'/> <vcpupin vcpu='15' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3f25e14d-e01b-b04c-05e4-8ea31610d531_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> </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/user/domains/mona/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/ubuntu-20.04.5-live-server-amd64.iso'/> <target dev='hda' bus='usb'/> <readonly/> <boot order='2'/> <address type='usb' bus='0' port='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <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='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </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='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='9' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/mona-home'/> <target dir='mona-home'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:7e:61:21'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x04' 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='2'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> </domain>

This is strange for me. Maybe it depends on the physical layout, on how the gpus are phisically connected to cores, when you attach gpus maybe one core is common and one vm wont run. Just try to run the vm with 2 cores, if both run simultaneously you found the issue: windows vm: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>7f96a124-c821-8ea1-f72d-032027ca068d</uuid> <description>Windows 10 Professional - May 2020 (2004)</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='6'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='1234567890ab'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='1' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-WDC_WD3000HLHX-60JJPV0_WD-WX61E41V2631'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </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:00:17:3a'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/Zotac.RTX3090.24576.210305.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Please attach diagnostics after trying to start the vm with gpu passthrough.

I think parsec will not be able to encode the video signal because it detects the qxl virtual gpu. Just passthrough only the real gpu as primary, install a vnc server inside the vm if you want vnc too, attach the dummy plug to the real gpu.

This is usually because the gpu is not properly isolated, efifb may be the culprit, search this forum for fixes. When the gpu is isolated it means that it's not available for the host, so it's fine that the nvidia driver in unraid will not load. The proper dirver to be loaded will be that inside the vm. It should be better to dump your own, if possible, otherwise make sure that what you are downloading is the vbios for your exact model, then check and remove the nvidia header.

Yes, it should be possible, have a look at this, especially latest replies: https://forums.unraid.net/topic/89294-switching-between-vms-conveniently/

Exactly, try this, copy/paste and save xml: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 11</name> <uuid>bf15b8e2-225d-d84f-2b67-00d3e3e61b20</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>9437184</memory> <currentMemory unit='KiB'>9437184</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> <vcpupin vcpu='4' cpuset='8'/> <vcpupin vcpu='5' cpuset='9'/> <vcpupin vcpu='6' cpuset='10'/> <vcpupin vcpu='7' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/bf15b8e2-225d-d84f-2b67-00d3e3e61b20_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:b2:bb:98'/> <source bridge='virbr0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-gb'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <boot order='1'/> <alias name='ua-sm2262'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <qemu:override> <qemu:device alias='ua-sm2262'> <qemu:frontend> <qemu:property name='x-msix-relocation' type='string' value='bar2'/> </qemu:frontend> </qemu:device> </qemu:override> </domain> If it doesn't work attach diagnostics. If part of the code is stripped it could be an unraid issue. You didn't have any graphics defined in the xml, I added basic qxl + vnc, so connect to the vm with builtin novnc. Once and if you fix the nvme issue you can try to passthrough the igpu.

ok, good catch, then I'm quite sure the -set option wont work. I'm on mobile now if a possible solution wont be posted I'll write it tomorrow.

Which version of unraid? You need to follow Simon advice but depending on the libvirt version the qemu:arg setting may not work, libvirt removed -set and added other workarounds for this. This issue is related to your nvme firmware, as already stated. You can find other discussions in this forum related to this issue, with possible fixes depending on the libvirt version. If you don't find them just write your unraid version.

Without knowing what the anticheat checks it's not possible to say anything..it can be easy as injecting smbios properties and hiding the hypervisor or very hard requiring the modification of the qemu source code.. You could try to inject manually smbios properties, such as in this post and see if it works: https://forums.unraid.net/topic/125745-xml-smbios-sysinfo-not-being-applied-to-vm/#comment-1146255

Try to hide the hypervisor cpu flag: shutdown the vm make sure you passthrough the cpu and you are not emulating it, so you have something li ke this: <cpu mode='host-passthrough' ...... Then add to this cpu block hte line to disable the hypervisor flag: <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='2' dies='1' cores='8' threads='2'/> <feature policy='disable' name='hypervisor'/> </cpu> Obviously change the topology to reflect yours. Now disable the hypervisor cpuid leaves: just above the closing tag </features> paste this block: <kvm> <hidden state='on'/> </kvm> --------------- args: -cpu 'host,-hypevisor,kvm=off' are arguments to be passed to qemu, setting libvirt xml as I described does the same thing (cpu host passthrough, hypervisor flag disabled, kvm off/hidden)

ok, I think it could be tricky to access the ovmf bios settings if you connect to the vm with vnc, you should be fast to open the vnc client, connect and press esc continuously before the boot process starts. You could try to remove from the vm the windows disk, just have only the "cert" vdisk: by this way the vm should boot to the uefi shell; type "exit" and press enter and the vm should reboot without closing the vnc client window, so you can press esc when it reboots. Once you finished injecting the certificates you can add back the windows disk.