VM Engine (KVM) Latest Topics

Unraid 7.1: 9070XT Won't Passthrough

Wed, 19 Mar 2025 00:52:47 +0000

Hey everyone,

I’m trying to pass through my 9070 XT to a Windows 11 VM on UnRAID 7, but I’m running into a ton of issues.

The VM fails to start, and I get the following errors in the logs:

Quote

qemu-system-x86_64: vfio: Unable to power on device, stuck in D3
qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:03:00.0

I’ve tried a few things so far:

vBIOS: Downloaded a clean vBIOS from TechPowerUp and set it in UnRAID, but the issue persists.

IOMMU Groups: The GPU is in its own group, so I don’t think it’s an isolation issue.

PCIe ACS Override: Enabled in "Both" mode, but still no luck.

BIOS Settings: Above 4G Decoding is enabled, and I made sure another GPU is the primary display.

Different PCIe Slots: Moved the GPU around, but the problem persists.

I’m wondering if this is an issue with how UnRAID is handling power states?

As others have stated that they have those exact issue as well...

Any suggestions would be greatly appreciated!

I'm hoping it's an easy fix that either I can implement or LimeTech/Unraid or a plugin expert can implement ASAP 🙏

Thanks in advance!

Arrow Lake iGPU Passthrough

Tue, 21 Jul 2026 10:10:36 +0000

Hi can someone help me passthrough the iGPU on my 285K to an ubuntu VM? I seem to be passing it through to the VM and I see the driver loading but then when I check the console in the VM I see i915 0000:00:02.0 [drm] *ERROR} GT1: GSC proxy handler failed to init and I can't actually use the GPU in my VM

Applicable Info

Host
- Unraid 7.3.2
  - Plugins: I have Intel SR-IOV installed but inactive as the GPU is being passed through
- CPU: Intel 285K
- Motherboard: MSI z890P-WIFI (IOMMU and SR-IOV are both enabled, Primary GPU set to the iGPU with 64MB of ram assigned
VM
- Ubuntu 24.04.4 LTS
- Kernel 7.0.0-28generic
- Driver: I currently have the i915 SR-IOV driver v2026..05.06 (I've been experimenting with SR-IOV as well but thqt doesn't seem to work yet for Arrow Lake unless I'm misunderstanding)
- Config



  Ubuntu-test
  8668e034-2ccf-fc63-f1a1-ff14198ea38b
  
    
  
  67108864
  67108864
  
    
    
    
  
  24
  
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
  
  
    /machine
  
  
    hvm
    /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd
    /etc/libvirt/qemu/nvram/8668e034-2ccf-fc63-f1a1-ff14198ea38b_VARS-pure-efi.fd
  
  
    
    
  
  
    
    
    
  
  
    
    
    
    
  
  destroy
  restart
  restart
  
    /usr/local/sbin/qemu
    
      
      
      
      
      vdisk1
      
      
      
    
    
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
    
    
      
      
    
    
      
      
    
    
      
      
      
    
    
      
      
      
    
    
      
      
      
    
    
      
      
        
        
      
      
      
      
      
    
    
      
      
        
        
      
      
      
      
      
    
    
      
      
        
        
      
      
      
      
      
    
    
      
      
      
      
      
      
    
    
      
      
      
      
      
      
    
    
      
      
        
      
      
    
    
      
      
      
    
    
      
      
      
      
    
    
      
      
    
    
      
    
    
      
    
    
      
    
    
    
      
      
      
    
    
      
      
        
      
      
      
      
    
    
      
      
        
      
      
      
      
    
    
      
      
        
      
      
      
    
    
      
    
    
  
  
    +0:+100
    +0:+100

Hoping someone can help me diagnose what is wrong



Machine keeps resetting to pc-q35-8.0
Fri, 29 May 2026 15:02:01 +0000
I have a Mojave VM that I run with pc-q35-5.1
With 7.3 it seems whenever I stop/start the array the machine setting in the XML (below) resets to pc-q35-8.0
Strange that UNRAID would make changes to VM XML surreptitiously.
Is there any way to stop it? 
  
    hvm
    /mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd
    /etc/libvirt/qemu/nvram/318231bd-841c-44xa-a9f5-389c374b34cd_VARS-pure-efi.fd
  


Use the eth0 or vlan0 network for the VMs in the event of an eth0 outage.
Sun, 12 Jul 2026 10:49:58 +0000
Hello everyone.
It’s all in the subject line: I want to use either the eth0 or vlan0 network for my VMs, specifically to handle situations where there is a problem with eth0.
I’m not sure how to configure Unraid for this scenario.
I was thinking of using "bridge" mode for both interfaces, but I can't figure out how to set that up.
To summarize:
By default, I use eth0 for everything in Unraid.
If eth0 loses its internet connection, I want to automatically switch to wlan0, which is connected to the internet.
I want this switch to be seamless for the VMs (Windows).
wlan0 is used only as a backup for internet access.
I’d appreciate some guidance on this, as I’m a bit lost...
Thanks !


VM Snapshots
Tue, 02 Jul 2024 18:23:02 +0000

	VM Snapshots discussion thread.




Lenovo ThinkStation P360 Ultra - VM GPU Passthrough deadlock on shutdown/stop (vfio_container_dma_map = -22 / BARs not supported)
Thu, 04 Jun 2026 17:23:38 +0000
Hi everyone,
I am experiencing a frustrating system deadlock (WebUI freeze, Error 504) whenever I attempt to gracefully shut down or stop a Windows 11 VM with a dedicated GPU passed through. The only way to keep Unraid stable is by using "Force Stop", but then the GPU stays bound to VFIO until manually re-attached.
Here are my exact system specifications and hardware topology gathered via lshw and Unraid System Devices:
Host Computer: Lenovo ThinkStation P360 Ultra (Desktop Computer / Motherboard SKU: LENOVO_MT_30G0)
BIOS Version: S0FKT34A (Date: 04/29/2025) with BIOS display set to "Auto"
CPU: 12th Gen Intel Core i7-12700 (Alder Lake-S)
RAM: 64 GB DDR5 (2x34GB SK Hynix SODIMM 5600 MHz)
Primary/Passed-through GPU: NVIDIA Corporation TU117GL [T400 4GB / T400E] (rev a1) – Note: The physical monitor cable is plugged into this card.
Integrated GPU: Intel Corporation Alder Lake-S GT1 [UHD Graphics 770]
Additional PCIe Hardware: Intel Corporation I350 Gigabit Network Connection (4-port server card installed in the second slot via riser, currently idle/no cables connected).
Storage: 2x 1TB Samsung PM9A1 NVMe SSDs + external TerraMaster D5-300C 5-bay USB enclosure via Thunderbolt/USB 3.2.
The Problem & Logs
When the VM boots, everything works perfectly. However, during a normal Windows shutdown or an ACPI "Stop" from the Unraid panel, the host logs immediately spam the following lines before the entire WebUI locks up:
char device redirected to /dev/pts/1 (label charserial0)
qemu-system-x86_64: warning: vfio_container_dma_map(...) = -22 (Invalid argument)
0000:70:00.0: PCI peer-to-peer transactions on BARs are not supported.
What I have already tried (and failed):
BIOS Tweaks: Disabled ASPM (Active State Power Management) completely to avoid PCIe power-state issues.
Unraid VM Settings (Startup): Enabled VFIO Allow Unsafe Interrupts and turned On all framebuffer blocks (EFI Framebuffer, Simple Framebuffer, Block All Framebuffers).
VM XML Patch: Modified the CPU section to include the  parameter, which is known to solve DMA mapping issues on 12th/13th Gen Intel CPUs. After rebuilding the NVRAM template, the VM started cleanly, but the host still locked up upon standard shutdown.
PCIe Conflict Suspect: I suspect a hardware limitation or interrupt conflict on the Lenovo motherboard/riser card between the NVIDIA T400 and the multi-port Intel I350 network card, as they share the CPU's primary PCIe lanes.
Since "Force Stop" works without crashing the host, I am currently using a custom User Script to manually re-attach the GPU back to the unRAID core/dockers after forcing the VM down. However, I would love to find a native fix for proper ACPI power-downs.
Has anyone encountered this specific behavior on Lenovo mini PCs or stasions with Intel 12th Gen CPUs sharing lanes with an un-utilized server NIC? Any advice on how to bypass this kernel/VFIO DMA mapping restriction would be highly appreciated!
Thank you in advance!



Arc Passthrough causing VM crashes loops (looks memory related)
Mon, 06 Jul 2026 15:20:45 +0000
I've had this issue for a while now, it started after an Unraid update  7.3.x. Currently on 7.3.2. The GPU passthrough to my Windows Server VM will work perfectly fine for weeks or months and then start crashing.
Once it starts the bsod's, only an Unraid host level reset will stop it. But even that only works for a limited time. From the logs, its definitely something with memory mapping. But this started after a recent update so im not sure if it was a kernel update or something?
Diags + virtual machine XML attached. Motherboard is ASUSTeK COMPUTER INC. TUF GAMING Z690-PLUS WIFI D4 with resize bar + 4g decoding enabled.
I also do see this error on VM boot which tells me something is off.
2026-07-05T14:46:28.232661Z qemu-system-x86_64: warning: vfio_container_dma_map(0x14e36f87aa00, 0xe0200000000, 0x100000000, 0x14e240000000) = -22 (Invalid argument)
0000:0a:00.0: PCI peer-to-peer transactions on BARs are not supported.
nas-diagnostics-20260706-0941.zip
server.xml


Linux VM with GPU passthrough broke after upgrading to 7.3
Fri, 15 May 2026 16:55:03 +0000
I don't really know how this is possible, but after upgrading to 7.3 my main linux VM won't show a gpu output.  I get the splash screen during startup, and I can even enter the VMs bios settings, but as soon as it tries to boot the screen goes black and never changes.  I'm passing through an Intel Arc B570.  I've tried changing the frame buffer parameters and VFIO unsafe interrupts without success.  Unfortunately I already converted to internal boot so I can't easily downgrade versions too.  Anybody else experience something similar with their VMs?
I haven't been able to attach the gpu vbios rom successfully, but I never needed it before so I don't see why I would need to now.


Easy Anti Cheat : launch error. cannot run under Virtual Machine
Fri, 26 Aug 2022 17:43:38 +0000

	been playing EAC games for years on my windows VM and have not had a problem until recently. I have come across someone saying add



	



	to the  section of my xml but it doesnt seem to change anything. not sure if im doing anything wrong or what. 



	 



	here is a copy of my xml. any help would be greatly appreciated.


xml version='1.0' encoding='UTF-8'?>
 type='kvm' id='3'>
  Windows 10
  46148b4e-b243-1e51-805c-cc16725ea2e2
  Gaming VM
  
     xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  
   unit='KiB'>25165824
   unit='KiB'>25165824
  
    
  
   placement='static'>20
  
     vcpu='0' cpuset='2'/>
     vcpu='1' cpuset='14'/>
     vcpu='2' cpuset='3'/>
     vcpu='3' cpuset='15'/>
     vcpu='4' cpuset='4'/>
     vcpu='5' cpuset='16'/>
     vcpu='6' cpuset='5'/>
     vcpu='7' cpuset='17'/>
     vcpu='8' cpuset='6'/>
     vcpu='9' cpuset='18'/>
     vcpu='10' cpuset='7'/>
     vcpu='11' cpuset='19'/>
     vcpu='12' cpuset='8'/>
     vcpu='13' cpuset='20'/>
     vcpu='14' cpuset='9'/>
     vcpu='15' cpuset='21'/>
     vcpu='16' cpuset='10'/>
     vcpu='17' cpuset='22'/>
     vcpu='18' cpuset='11'/>
     vcpu='19' cpuset='23'/>
  
  
    /machine
  
  
     arch='x86_64' machine='pc-q35-5.1'>hvm
     readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd
    /etc/libvirt/qemu/nvram/46148b4e-b243-1e51-805c-cc16725ea2e2_VARS-pure-efi.fd
     mode='host'/>
  
  
    
    
    
       state='on'/>
       state='on'/>
       state='on' retries='8191'/>
       state='on' value='none'/>
    
  
   mode='host-passthrough' check='none' migratable='on'>
     sockets='1' dies='1' cores='10' threads='2'/>
     mode='passthrough'/>
     policy='require' name='topoext'/>
  
   offset='localtime'>
     name='hypervclock' present='yes'/>
     name='hpet' present='no'/>
  
  destroy
  restart
  restart
  
    /usr/local/sbin/qemu
     type='file' device='disk'>
       name='qemu' type='raw' cache='writeback'/>
       file='/mnt/disk1/isos/spaces_win_clover.img' index='2'/>
      
       dev='hdc' bus='virtio'/>
       order='1'/>
       name='virtio-disk2'/>
       type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    
     type='file' device='cdrom'>
       name='qemu' type='raw'/>
       file='/mnt/user/isos/virtio-win-0.1.190-1.iso' index='1'/>
      
       dev='hdb' bus='sata'/>
      
       name='sata0-0-1'/>
       type='drive' controller='0' bus='0' target='0' unit='1'/>
    
     type='pci' index='0' model='pcie-root'>
       name='pcie.0'/>
    
     type='pci' index='1' model='pcie-root-port'>
       name='pcie-root-port'/>
       chassis='1' port='0x8'/>
       name='pci.1'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    
     type='pci' index='2' model='pcie-root-port'>
       name='pcie-root-port'/>
       chassis='2' port='0x9'/>
       name='pci.2'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    
     type='pci' index='3' model='pcie-root-port'>
       name='pcie-root-port'/>
       chassis='3' port='0xa'/>
       name='pci.3'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    
     type='pci' index='4' model='pcie-root-port'>
       name='pcie-root-port'/>
       chassis='4' port='0xb'/>
       name='pci.4'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
    
     type='pci' index='5' model='pcie-root-port'>
       name='pcie-root-port'/>
       chassis='5' port='0xc'/>
       name='pci.5'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
    
     type='pci' index='6' model='pcie-root-port'>
       name='pcie-root-port'/>
       chassis='6' port='0xd'/>
       name='pci.6'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
    
     type='pci' index='7' model='pcie-root-port'>
       name='pcie-root-port'/>
       chassis='7' port='0xe'/>
       name='pci.7'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
    
     type='pci' index='8' model='pcie-root-port'>
       name='pcie-root-port'/>
       chassis='8' port='0xf'/>
       name='pci.8'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/>
    
     type='virtio-serial' index='0'>
       name='virtio-serial0'/>
       type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    
     type='sata' index='0'>
       name='ide'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    
     type='usb' index='0' model='ich9-ehci1'>
       name='usb'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    
     type='usb' index='0' model='ich9-uhci1'>
       name='usb'/>
       startport='0'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    
     type='usb' index='0' model='ich9-uhci2'>
       name='usb'/>
       startport='2'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    
     type='usb' index='0' model='ich9-uhci3'>
       name='usb'/>
       startport='4'/>
       type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    
     type='bridge'>
       address='52:54:00:6e:2f:a7'/>
       bridge='br0'/>
       dev='vnet0'/>
       type='virtio'/>
       name='net0'/>
       type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    
     type='pty'>
       path='/dev/pts/0'/>
       type='isa-serial' port='0'>
         name='isa-serial'/>
      
       name='serial0'/>
    
     type='pty' tty='/dev/pts/0'>
       path='/dev/pts/0'/>
       type='serial' port='0'/>
       name='serial0'/>
    
     type='unix'>
       mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-3-Windows 10/org.qemu.guest_agent.0'/>
       type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
       name='channel0'/>
       type='virtio-serial' controller='0' bus='0' port='1'/>
    
     type='mouse' bus='ps2'>
       name='input0'/>
    
     type='keyboard' bus='ps2'>
       name='input1'/>
    
     mode='subsystem' type='pci' managed='yes'>
       name='vfio'/>
      
         domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
      
       name='hostdev0'/>
       type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    
     mode='subsystem' type='pci' managed='yes'>
       name='vfio'/>
      
         domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
      
       name='hostdev1'/>
       type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    
     mode='subsystem' type='pci' managed='yes'>
       name='vfio'/>
      
         domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      
       name='hostdev2'/>
       type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    
     mode='subsystem' type='pci' managed='yes'>
       name='vfio'/>
      
         domain='0x0000' bus='0x0a' slot='0x00' function='0x3'/>
      
       name='hostdev3'/>
       type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    
     model='none'/>
  
   type='dynamic' model='dac' relabel='yes'>
    +0:+100
    +0:+100
  



	 




Unraid 7.3.1 - Slow VM Startup & Unraid Hangs/Crashes When Shutting Down VM (Anyone Else?)
Mon, 29 Jun 2026 18:05:40 +0000
Hi all,
I'm wondering if anyone else has experienced this after upgrading to Unraid 7.3.1.othe
VM startup is significantly slower than before. (The UI freezes for about 30 sec to a minute)
When shutting down a VM, Unraid hangs or crashes completely. The WebGUI becomes unresponsive/ fails to SSH, and I have to force reboot the server.
wing


Code 43 in Win11 with 6950XT
Sun, 05 Jul 2026 06:36:47 +0000
Sometimes it works, sometimes it doesn't. When it doesn't, it will boot windows for 10 minutes, and then run with code 43 in device manager. But a couple of days later it will boot just fine.
I have a 6950XT in slot 1 and Arc A310 in the bottom most slot, running at 4x, bios is set up to boot from the ARC card, unraid recognises it as default, as it should. I'm also using ReBAR hack from this post: https://forums.unraid.net/topic/133192-vm-gpu-passthrough-resizable-bar-support-in-61-kernel/page/4/#findComment-1531812
CPU is Ryzen 5900X on X570 Aorus Ultra.
Please help.

brix-diagnostics-20260705-0816.zip


virtiofsd silently crashes
Thu, 14 May 2026 14:51:18 +0000
I am running an arch VM:
VM XML


Whole server turning off suddently after booting my most important VM (downgraded the setup)
Sat, 27 Jun 2026 18:15:17 +0000
Hi !

Really a critical issue here. Until now my Unraid server was a strong powerful PC (i7-14700kf + RTX 4060) used for me to use a VM as my main PC. I did setup an important PC, everything worked well no issue. It was using the GPU Passthrough, 24Gb of RAM only for the VM etc.

But for personnal reasons, I need to downgrade my setup. I removed the GPU + CPU + MB + RAM for something more light (i7-10700 / No GPU / 8Gb of RAM). Changing the PC was fine, the server works well no issue. So i've tried to boot my VM (after removing the old passthrough stuff etc) and... No result (no post). So easy fix was to just create a new profile using the correct vdisk.
It worked fine. Until the VM passed the Windows loading screen. After that, the WHOLE server just shut down. No alert, no warning. Turns off. I don't really know the issue it should just move fine. For information, I don't need the power of before. I just need to access my internet browser and the file to prepare a migration planned next week. So nothing special will be launched.
I blamed the RAM but I had like 2Gb for the Unraid and 4Gb for the VM. Nothing else.
Really need an urgent help here.
Edit : Thrown 32Gb of RAM. Still not working. I could hold it a little longer but still turned off.
Edit 2 : Used a NON Unraid VM Windows. Let it run for 1 hour straight. No issue. Launched the VM. Passed the password => Unraid died. 
It's really important for me to have a solution here.

Thanks !
serveur-syslog-20260627-1751.zip


Windows VM - non-trivial to safely remove locally attached USB drives without restarting
Sat, 27 Jun 2026 15:54:46 +0000
In my Windows 11 VM running under Unraid 7.2.2, it is difficult or impossible to safely remove USB drives that are mounted in the VM. 
One of the host system's USB3 controllers (ASMedia) is passed through to the VM.  It is a physical USB3 controller on a PCIe card. Devices that are directly and locally used by the Windows VM are connected there. 
In the Windows VM, the device Manager tree looks like this: 

The problem is the "Safely Remove Device" dialog in the tray looks like this: 

If I remove the ASMedia USB3.1 controller, it also removes devices unrelated to the USB hard drives and used by applications, and would affect system operation. 
The USB Mass Storage Device that holds the drives is a Sabrent 4-bay drive docking controller 
Attempting to disable this device in Device Manager results in a prompt to reboot. 
Has anyone found a clean way to shut down drives for replacement without shutting down the VM? 




My Windows 11 VM doesn't detect properly docker hub via usb 4 pass through
Sat, 27 Jun 2026 10:11:34 +0000
The docker hub is a Ugreen thunderbolt 4 that works properly when i connect it to a laptop. But I when I move the same cable to the usb 4 passhtrough, the windows vm only shows thunderbolt 4 docker and doesn't recognize any connected devices to it (microsd, flash drive, bluetooth usb). There is another usb keyboard attached on the passthrough and it works properly... There is something with the docker stations in general. The older unraid pc i had did not prsent issues.
Motherboard: ASRock X870E Taichi , Version Default string
American Megatrends International, LLC., Version 3.40
BIOS dated: Wed 27 Aug 2025 12:00 AM
Unraid : 7.3.1
Docker station: https://www.amazon.com/UGREEN-Revodok-Docking-Station-Display/dp/B0FM45VH8N/ref=sr_1_4?crid=RXTTHA3U9ZK0&dib=eyJ2IjoiMSJ9.-ROzQ6mS84m-4zLSIIQy1BbbBNnUrBFWxqTydRMdZKenM3huWvy7BXq7EaD_XKMaPgrZjNjvrI_hoEjTXoEDKoN7npffsgoKLYKblKbn7znBM0Ew5LRpVVWeWKvuhuem1u4fHa_1wjE2OhZW1YHyBPj9JQALSy0YzmXYJcQ5zsP2lsPcKrxrSJg0eB7adyJRojgVNU4L9ZUeH4yA5JXDkna2Fic0Roj80XE7vqypHj0.tLVOvpLlL9dQ5Oc-cN0WZX3Ojm6tsr4T-GpJS2c0n7c&dib_tag=se&keywords=ugreen+thunderbolt+4+dock&qid=1782554828&sprefix=ugreen+thunder%2Caps%2C248&sr=8-4
diagnostics and syslog attached.


tower-diagnostics-20260627-1308.zip 
syslog.txt


Poor performance on Win11 VM
Wed, 24 Jun 2026 08:24:01 +0000
Not sure what is going on but I have noticed since upgrading to V7.3.1 my Win11 VM is running weirdly, its slow and laggy.
Is it still the case when you add GPU passthru you need to configure using XML mode or can you do it all through the gui now? This VM has been setup for about 4 years at a guess, using spaceinvader video. Not sure if the XML is the issue or its OS level fault.


	Windows 11
	996dd70b-875d-f9ba-0d9c-b1cd88f2825a
	
		
		
		16777216
		16777216
		
			
		
		10
		
			
			
			
			
			
			
			
			
			
			
			
		
		
			/machine
		
		
			hvm
			/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd
			/etc/libvirt/qemu/nvram/996dd70b-875d-f9ba-0d9c-b1cd88f2825a_VARS-pure-efi-tpm.fd
		
		
			
			
			
				
				
				
				
				
				
				
			
		
		
			
			
		
		
			
			
		
		destroy
		restart
		restart
		
			/usr/local/sbin/qemu
			
				
				
				
				
				vdisk1
				
				
				
			
			
				
				
				
				
				
				
				
			
			
				
				
			
			
				
			
			
				
				
				
				
			
			
				
				
				
				
			
			
				
				
				
				
			
			
				
				
				
				
			
			
				
				
				
				
			
			
				
				
				
				
			
			
				
				
				
				
			
			
				
				
				
				
			
			
				
				
			
			
				
				
			
			
				
				
			
			
				
				
				
				
				
				
			
			
				
				
					
				
				
			
			
				
				
				
			
			
				
				
				
				
			
			
				
			
			
				
			
			
				
				
			
			
			
				
				
					
				
				
				
				
			
			
				
				
					
				
				
				
			
			
				
			
			
		
		
			+0:+100
			+0:+100
		
	
In the log
2026-06-20 09:13:25.384+0000: Domain id=7 is tainted: high-privileges
char device redirected to /dev/pts/0 (label charserial0)
2026-06-20T09:13:27.952700Z qemu-system-x86_64: warning: vfio_container_dma_map(0x14977b3d0d80, 0x382000000000, 0x10000000, 0x149760000000) = -22 (Invalid argument)
0000:01:00.0: PCI peer-to-peer transactions on BARs are not supported.
GPT and Grok said disable Resizable BAR in BIOS but that was already disabled and BIOS settings are unchanged also. Want just rule out config issue before I nuke the windows install and start again.



VM cannot start
Sat, 20 Jun 2026 16:29:32 +0000
Not sure what updated. I upgraded to 7.3.1 and now can no longer start my VM. Getting the error message below. Any thoughts?
Internal error: process exited while connecting to monitor: 2026-06-20T16:[removed] qemu-system-x86_64: -device {"driver":"vfio-pci","host":"0000:04:00.0","id":"hostdev0","bus":"pci.0","addr":"0x5"}: vfio 0000:04:00.0: group 0 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver.



Help with creating VM with unraid share mount in read-only mode
Mon, 22 Jun 2026 06:22:22 +0000
I have a VM on the unraid server that I have in a separate subnet. That subnet can't reach the subnet with the unraid server front end. I am trying to use the "unraid share mode" feature to share some of the directories to the VM. But I want them to be shared to the VM in read only mode. Is that possible? I don't see an option for that on in the vm config page. Is there a setting somewhere in the shares themselves or possibly in the settings that I'm not seeing?


Missing vhost NIC option in VM configuration GUI
Sun, 21 Jun 2026 19:24:29 +0000
vhost network interface suddenly gone missing in edit VM GUI. This bug reproducing even on VMs with vhost0 still active (and working!) in XML view:
Unraid version: 7.3.1
/boot/config/network.cfg
# Generated settings:
IFNAME[0]="eth0"
DHCP_KEEPRESOLV="no"
DHCP6_KEEPRESOLV="no"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="yes"
USE_DHCP6[0]="yes"
IFNAME[1]="eth1"
DESCRIPTION[1]="Mellanox 10G"
PROTOCOL[1]="ipv4"
USE_DHCP[1]="yes"
SYSNICS="2"
/boot/config/domain.cfg
SERVICE="enable"
IMAGE_FILE="/mnt/user/system/libvirt/libvirt.img"
IMAGE_SIZE="1"
DEBUG="no"
DOMAINDIR="/mnt/user/domains/"
MEDIADIR="/mnt/user/isos/"
VIRTIOISO="/mnt/user/isos/virtio-win-0.1.240-1.iso"
BRNAME="eth0"
VMSTORAGEMODE="auto"
TIMEOUT="60"
HOSTSHUTDOWN="shutdown"
CONSOLE="web"
DISABLE="no"
RDPOPT="no"
USAGE="N"
USAGETIMER="3"
Something is definitely messed up - network.cfg reports Mellanox as interface with index 1, but in GUI its definitely eth0:
eth1 is inactive (1 Gbe NIC)
So, any ideas how do I bring back vhost0 to my VM GUI? editing XML works too, but not ideal.


unraid 7.2.3  - showing this error all of a sudden when running windows VM (another VM on the same SSD is working fine)
Thu, 11 Jun 2026 21:16:01 +0000
I will attach diagnostics in case it's needed. I tried rebooting the entire server but the same issue. Not sure what to do (I have snapshots but before I do anything, waiting for instructions) - The vm in VNC mode starts but the spinning white circle just stops. In VM's it shows paused but i did hard shut down and rebooted entire server and it keeps happening.
tower-diagnostics-20260611-1715.zip





[Unraid 7.3.1] KVM Ubuntu Installation Stuck at Profile Configuration Screen, Keyboard Input Not Working
Thu, 18 Jun 2026 01:25:24 +0000
Hi everyone,  
I'm running Unraid 7.3.1 and creating a new KVM VM with Ubuntu 24.04 LTS Server. 
The installer boots normally to the "Profile configuration" screen, but I can't type anything into any input fields here—keyboard input is completely unresponsive.  
I've tested both SPICE and VNC console protocols, and the keyboard works fine in the Unraid webUI and other VMs, so the issue only happens during this Ubuntu installation step.  
Screenshot attached for reference. 
 Thanks for any help!






blank screen on intel uhd 770 igpu passthru. unraid 7.3.1
Tue, 16 Jun 2026 05:20:21 +0000
i was able to setup windows 11 and install intel gpu driver using vnc. but everytime i tried to use the onboard graphics all i get is blank screen, but seems to boot up but no display and sound.
i follow alot of guide but no luck. if i used dedicated graphics (nvidia p2000) everything work normal but of course jellyfin transcoding will not work not even start the jellyfin.  can anyone help me on configuring vm using onboard graphics and sounds thanks!


Built-in VNC Viewer Freezes on Connection
Tue, 16 Jun 2026 01:24:52 +0000
I’ve run into a new issue with the built-in VNC viewer. Immediately after connecting to a virtual machine, the viewer freezes. I can't tell if the entire session is locked up or if it's just failing to receive input, but it makes installing Linux over VNC nearly impossible. I see an error in the browser console: `noVNC requires a secure context (TLS). Expect crashes!`.

I have found a temporary solution, If I switch the VM network to virbr0, the freezing issue completely disappears.

I'm seeing this problem across multiple networks. All of them are managed by UniFi and utilize VLANs (a pretty standard setup, I assume).

My workflow right now to install Ubuntu Server remotely is to:
Create a VM with virbr0, install linux.
Enable SSH.
Update the VM's network configuration.
Switch the interface over to br0.
VNC is frozen but SSH is working.
Is anyone else experiencing this same VNC freeze on bridged networks, or does anyone have a permanent fix?



Ubuntu VM Guided storage configuration
Sat, 13 Jun 2026 18:57:14 +0000
Hello all. I have been using Unraid for a number of years and have created a boat load of VM's In fact many of them are in use daily. Today was the first time that I attempted to create a new Ubuntu VM in UR v.7.3.1. I may be experiencing a brain fart or am totally missing something. All drives are healthy and have an abundace of storage. I cannot get past the Ubuntu prompt you see below. Your time and assistance will be greatly appreciated. Peter




Nvidia T400 and audio and Win11
Thu, 11 Jun 2026 12:27:09 +0000
I have a problem with the Nvidia T400 and audio. When I shut down my Windows 11 virtual machine, Unraid freezes because it doesn't release the Nvidia audio.


Upgraded from 7.2.3 to 7.3.1, now Win11 VM passthrough disk isn't seen
Wed, 03 Jun 2026 21:22:03 +0000
I updated unRAID last week and didn't think to try my VMs till today.
I had a template "Windows 10 Gaming 3" (that is actually running Windows 11 now) which, when I attempted to boot today, only gave me a black screen.
After several forced shutdowns via the VM Manager, to troubleshoot, I removed the NVIDIA passthru card and used VNC. 
I get the Windows System Recovery terminal, and Command Line for DISKPART shows no disks or volumes are present.
I'm using a WD NVMe as passthru (no issue before the upgrade)
I created a new template (specifying Win11 this time) and set the same settings. Still the same result.
Do I need to downgrade back to 7.2.3 or is there maybe something I don't know about that can fix this?

ChatGPT kept calling out this as the probable issue:
2026-06-03T15:53:36.813915Z qemu-system-x86_64: vfio_listener_valid_section received unaligned region 0000:06:00.0 BAR 4 mmaps[0] iova=0x847fbf00 offset_within_region=0x0 qemu_real_host_page_size=0x1000 
2026-06-03T15:54:19.062102Z qemu-system-x86_64: vfio_listener_valid_section received unaligned region 0000:06:00.0 BAR 4 mmaps[0] iova=0x847fbf00 offset_within_region=0x0 qemu_real_host_page_size=0x1000 
2026-06-03T15:54:20.119240Z qemu-system-x86_64: vfio_listener_valid_section received unaligned region 0000:06:00.0 BAR 4 mmaps[0] iova=0x847fbf00 offset_within_region=0x0 qemu_real_host_page_size=0x1000

PCIe ACS Override setting is enabled, btw.

hagrid-diagnostics-20260603_1111.zip


SR-IOV error
Thu, 11 Jun 2026 04:44:17 +0000
When applying number of VF on iGPU, I get this error;

Error: Failed to change VF configuration: Failed writing to /sys/bus/pci/devices/0000:00:02.0/sriov_numvfs: file_put_contents(): Write of 1 bytes failed with errno=2 No such file or directory

Claude says that iGPU and XE drivers crashes and suggests adding to syslinux:

"append initrd=/bzroot intel_iommu=on iommu=pt i915.enable_guc=3 modprobe.blacklist=xe"

I have not yet tried that. What is the correct way to fix this?
Cheers,

// f
kjell-diagnostics-20260611-0638.zip


v7.3.1 Kernel panic in Ubuntu VM - no issue with previous v7.2.3
Mon, 08 Jun 2026 16:52:40 +0000
I upgraded 2 of my 3 servers to 7.3.1 and noticed one issue that can hopefully be easily corrected. When running my ubuntu VM, I keep getting kernel panic causing complete stop of my remote desktop session. I checked online and it said to use the latest Machine Q35-10.2 but between 10-15 minutes after running the vm, it stops. Any hints with this? Before 7.3.1 I had 7.2.3 and no issue. Any ideas? If you need my diag, let me know but this one sounds like an easy fix?
I also had another Ubuntu VM and tried it and same thing occurred with the kernel panic so it's got to be with something when it got upgraded.
phantekone-diagnostics-20260608-1205.zip


VM Autostart disabled due to vfio-bind error
Tue, 09 Jun 2026 12:41:50 +0000
I've been playing, replacing some components and reconfiguring others... But I've clearly messed something up.
I have two VMs that autostart at startup:
One that uses the Network card (Upgraded) to run the router, and another to run home assistant.
Once I log in I can just start the two VMs and they seem to be working fine.
I also have a gaming VM that uses a Dedicated SSD, a USB card, and Video card. But it gets launched as needed (Sure wish I could let the server use that Video card when the Gaming machine isn't in use.)
I guess I could completely wipe out the vfio-bind and rebuild, but if there error is coming from the config of a virtual machine that might not fix it.
Thanks
jupiter-diagnostics-20260609-0825.zip


COMPLETE TECHNICAL REPORT - VFIO GPU PASSTHROUGH FAILURE
Wed, 21 Jan 2026 12:39:18 +0000
HARDWARE CONFIGURATION
Motherboard: MSI MPG X870E Carbon WiFi (MS-7E49)
BIOS Version: E7E49AMSI.1A7D
BIOS Build Date: January 07, 2026
Chipset: AMD X870E
CPU: AMD Ryzen 9 9950X3D
16 Cores / 32 Threads
Base Clock: 4.3 GHz
Integrated Graphics: AMD Radeon (iGPU)
RAM: 128GB DDR5-5200
Brand: G.Skill Flare X5
Configuration: 4x 32GB modules
GPU (Passthrough Target):
Model: NVIDIA GeForce RTX 4060 Ti 16GB (MSI)
PCI Address: 0000:01:00.0 (GPU) + 0000:01:00.1 (Audio)
IOMMU Group: 14
Device IDs: 10de:2805 (GPU), 10de:22bd (Audio)
Primary Display: Integrated Graphics (AMD Radeon iGPU)
Operating System:
Unraid Server OS version 7.2.3
Linux Kernel: 6.12.54-Unraid
Bootloader: Limine (NOT Syslinux - critical detail!)
Storage:
VM vDisk 1: /mnt/windowsfestplatte/vdisk1.img (Windows System)
VM vDisk 2: /mnt/gaming/gaming_storage.img (Gaming Storage)
VirtIO Drivers: /mnt/vm/virtio-win-0.1.285-1.iso
OBJECTIVE
Pass through NVIDIA RTX 4060 Ti to a Windows 11 VM using VFIO-PCI for native GPU performance in gaming and GPU-accelerated workloads.
INITIAL PROBLEM: BOOTLOADER DISCOVERY
Issue #1: Kernel parameters not loading
Initial attempts to configure VFIO via /boot/syslinux/syslinux.cfg had NO EFFECT because:
bash
# cat /proc/cmdline[empty output]```**Root Cause:** System boots via **Limine bootloader**, NOT Syslinux
- Limine config location: `/boot/limine.conf`- Evidence: `ls -la /boot/` showed `limine.conf` with recent modification date- This is a critical issue because most Unraid VFIO guides assume Syslinux
**Solution Applied:**
Modified `/boot/limine.conf` instead of syslinux.cfg:
```
/Unraid OS
    protocol: linux
    kernel_path: boot():/bzimage
    module_path: boot():/bzroot
    cmdline: pcie_acs_override=downstream,multifunction amd_iommu=on iommu.passthrough=1 vfio-pci.ids=10de:2805,10de:22bd video=efifb:off
    comment: Unraid OS
Verification:
bash
# cat /proc/cmdlinepcie_acs_override=downstream,multifunction amd_iommu=on iommu.passthrough=1 vfio-pci.ids=10de:2805,10de:22bd video=efifb:off
# dmesg | grep "Command line"[0.000000] Command line: pcie_acs_override=downstream,multifunction amd_iommu=on iommu.passthrough=1 vfio-pci.ids=10de:2805,10de:22bd video=efifb:off
```
✅
 Kernel parameters successfully loaded after Limine configuration --- ### **BIOS CONFIGURATION****Critical Settings for VFIO:** **1. Graphics Configuration:** ```Advanced → Integrated Graphics Configuration   - Initiate Graphic Adapter: IGD (iGPU) ✅  - Graphics Card Detection: Ignore ```*Purpose: Force iGPU as primary display, leaving NVIDIA available for passthrough* **2. PCI Subsystem Settings:** ```Advanced → PCI Subsystem Settings   - Above 4G Decoding: ENABLED ✅  - Re-Size BAR Support: DISABLED ✅ (CRITICAL!)  - SR-IOV Support: DISABLED ✅```*Purpose: Re-Size BAR enabled causes "1:1 IOMMU mapping" firmware errors* **3. AMD IOMMU Settings:** ``` Advanced → AMD CBS → NBIO Common Options   - IOMMU: Enabled ✅  - ACS Enable: Auto/Enabled
Verification:
bash
# dmesg | grep -i "amd-vi"AMD-Vi: IOMMU performance counters supported
pci 0000:01:00.0: Adding to iommu group 14pci 0000:01:00.1: Adding to iommu group 14# dmesg | grep -i "iommu"iommu: Default domain type: Passthrough (set via kernel command line)
✅ IOMMU enabled and operational
VFIO-PCI BINDING
Issue #2: Duplicate binding causing conflicts
Problem: GPU was being bound to vfio-pci TWICE:
Via kernel parameter: vfio-pci.ids=10de:2805,10de:22bd
Via Unraid config: /boot/config/vfio-pci.cfg containing BIND=0000:01:00.0|10de:2805 0000:01:00.1|10de:22bd
Solution:
bash
# Backup and clear vfio-pci.cfgcp /boot/config/vfio-pci.cfg /boot/config/vfio-pci.cfg.backup
echo "" > /boot/config/vfio-pci.cfg
reboot
Verification:
bash
# lspci -nnk -d 10de:280501:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD106 [GeForce RTX 4060 Ti 16GB] [10de:2805] (rev a1)    Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:5174]    Kernel driver in use: vfio-pci 
✅
    Kernel modules: nouveau # ls -la /dev/vfio/crw------- 1 root root 245, 0 Jan 20 20:18 14 ✅crw-rw-rw- 1 root root 10, 196 Jan 20 20:18 vfio
✅ GPU successfully bound to vfio-pci
IOMMU GROUP CONFIGURATION
Issue #3: IOMMU Group in wrong mode
Discovery:
bash
# cat /sys/kernel/iommu_groups/14/typeidentity 
❌
IOMMU Group 14 was in "identity" mode instead of "DMA" mode required for VFIO.
Solution:
bash
# echo DMA > /sys/kernel/iommu_groups/14/type# cat /sys/kernel/iommu_groups/14/typeDMA 
✅
Additional mitigation:
bash
# echo 1 > /sys/module/vfio_iommu_type1/parameters/allow_unsafe_interrupts
VM CONFIGURATION
Multiple VM configurations tested:
Attempt 1: i440fx machine type (initial)
Machine: pc-i440fx-9.2
Result: GPU not available in WebUI dropdown
Attempt 2: Q35 machine type
Machine: pc-q35-9.2
BIOS: OVMF-TPM (UEFI)
vCPUs: 16 (8 cores, 2 threads)
RAM: 16GB
Primary vDisk: VirtIO bus
Result: GPU still not in dropdown, added manually via XML
Attempt 3: Manual XML configuration
Multiple PCI bus configurations attempted:
Configuration A:
xml
        
Result: Failed with "Invalid argument"
Configuration B:
xml
        
Result: Failed with "Invalid argument"
Configuration C (Final attempt):
xml
            ```
Result: Still failed with "Invalid argument"
---
### **PERSISTENT ERROR**
**Every VM start attempt fails with:**
```
error: Failed to start domain 'Windows 11'
error: internal error: QEMU unexpectedly closed the monitor (vm='Windows 11'): 
2026-01-21T12:35:40.272528Z qemu-system-x86_64: -device {"driver":"vfio-pci",
"host":"0000:01:00.0","id":"hostdev0","bus":"pci.6","multifunction":true,
"addr":"0x0"}: vfio 0000:01:00.0: failed to setup container for group 14: 
Failed to set group container: Invalid argument
Kernel log shows:
bash
# dmesg | tail -5vfio-pci 0000:01:00.0: Firmware has requested this device have a 1:1 IOMMU mapping, 
rejecting configuring the device without a 1:1 mapping. Contact your platform vendor.
DIAGNOSTIC DATA
IOMMU Status:
bash
# dmesg | grep -i "iommu mode"[0.587478] iommu: Default domain type: Passthrough (set via kernel command line)# ls /sys/kernel/iommu_groups/ | wc -l54# for d in /sys/kernel/iommu_groups/14/devices/*; do lspci -nns "${d##*/}"; done01:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD106 [GeForce RTX 4060 Ti 16GB] [10de:2805] (rev a1)01:00.1 Audio device [0403]: NVIDIA Corporation AD106M High Definition Audio Controller [10de:22bd] (rev a1)
VFIO Module Status:
bash
# lsmod | grep vfiovfio_pci               16384  0vfio_pci_core          86016  1 vfio_pci
vfio_iommu_type1       49152  0vfio                   65536  3 vfio_pci_core,vfio_iommu_type1,vfio_pci
Container Status:
bash
# ls -la /dev/vfio/crw------- 1 root root 245, 0 Jan 20 20:18 14crw------- 1 root root 245, 1 Jan 20 20:18 15crw-rw-rw- 1 root root 10, 196 Jan 20 20:18 vfio
# lsof /dev/vfio/14[no output - device not in use]
PCI Device Tree:
bash
# lspci -tv-[0000:00]-+-00.0  Advanced Micro Devices, Inc. [AMD] Device
           +-00.2  Advanced Micro Devices, Inc. [AMD] Device
           +-01.0  Advanced Micro Devices, Inc. [AMD] Device
           +-01.1-[01]--+-00.0  NVIDIA Corporation AD106 [GeForce RTX 4060 Ti 16GB]           |            \-00.1  NVIDIA Corporation AD106M High Definition Audio Controller
TROUBLESHOOTING STEPS ATTEMPTED
✅ 1. Verified hardware compatibility
Confirmed IOMMU support in CPU
Verified motherboard supports VT-d/AMD-Vi
✅ 2. BIOS configuration
Enabled IOMMU
Disabled Re-Size BAR (critical!)
Set iGPU as primary display
Enabled Above 4G Decoding
✅ 3. Bootloader configuration
Discovered Limine (not Syslinux)
Configured correct kernel parameters
Verified parameters loaded
✅ 4. Kernel parameters optimized
amd_iommu=on
iommu.passthrough=1 (later changed to iommu=pt)
pcie_acs_override=downstream,multifunction
vfio-pci.ids=10de:2805,10de:22bd
video=efifb:off
✅ 5. VFIO binding
Removed duplicate bindings
Verified vfio-pci driver attachment
Confirmed VFIO devices created
✅ 6. IOMMU group management
Set group type to DMA
Enabled unsafe interrupts
Verified group isolation
✅ 7. VM configuration
Tested multiple machine types (i440fx, Q35)
Tried various PCI bus configurations
Added multifunction attribute
Attempted different slot/bus combinations
✅ 8. GPU unbind/rebind
bash
echo "0000:01:00.0" > /sys/bus/pci/drivers/vfio-pci/unbind
echo "0000:01:00.1" > /sys/bus/pci/drivers/vfio-pci/unbind
sleep 2echo "0000:01:00.0" > /sys/bus/pci/drivers/vfio-pci/bind
echo "0000:01:00.1" > /sys/bus/pci/drivers/vfio-pci/bind
```
❌
 **None of these resolved the issue** --- ### **ROOT CAUSE ANALYSIS****Firmware-Level Restriction:** The error message is clear: ``` vfio-pci 0000:01:00.0: Firmware has requested this device have a 1:1 IOMMU  mapping, rejecting configuring the device without a 1:1 mapping. Contact your  platform vendor.
This indicates the UEFI firmware is enforcing a DMA protection mechanism that conflicts with VFIO's virtualization requirements.
Possible Contributing Factors:
New Hardware Generation
X870E chipset released Q4 2024
Ryzen 9 9950X3D released 2024
VFIO support may not be mature
Re-Size BAR Conflict
Despite disabling in BIOS, firmware may still enforce related restrictions
Common issue with newer NVIDIA GPUs
Firmware Bug
BIOS version E7E49AMSI.1A7D may have incomplete IOMMU implementation
May require BIOS update from MSI
Kernel/QEMU Version
Unraid 7.2.3 uses kernel 6.12.54
X870E support may require newer kernel
Missing BIOS Option
Hidden or unavailable option controlling IOMMU strictness
AMD CBS settings may have additional undocumented options
QUESTIONS FOR MSI/AMD SUPPORT
Is VFIO GPU passthrough officially supported on the MPG X870E Carbon WiFi?
Does BIOS version E7E49AMSI.1A7D have known issues with IOMMU/virtualization?
Is there a newer BIOS version that addresses VFIO compatibility?
Are there hidden BIOS settings (AMD CBS) that control the "1:1 IOMMU mapping" firmware requirement?
Does the "Re-Size BAR Support" setting have secondary effects even when disabled?
What is the recommended BIOS configuration for GPU passthrough on this board?
Is this a known limitation of the X870E chipset?
SYSTEM STATE AT TIME OF FAILURE
All verifications passing:
bash
# Kernel parameters
✅
 pcie_acs_override: active ✅ amd_iommu: enabled ✅ iommu.passthrough: active ✅ vfio-pci.ids: bound # BIOS settings✅ IOMMU: enabled ✅ Re-Size BAR: disabled ✅ Above 4G: enabled ✅ iGPU primary: active # GPU binding✅ Driver: vfio-pci ✅ IOMMU group: 14 (isolated)✅ Group type: DMA ✅ VFIO device: /dev/vfio/14 exists
Yet VM start fails with firmware restriction.
COMMUNITY NOTES
Discord user "Mainfrezzer" (experienced with Unraid VFIO) suggested:
"Has anyone told you that pcie pass through does not work with i440fx? Create a new template, set it to q35 at the start and go from there"
However, Q35 configuration also failed with identical error.
Discord user "mowmdown" confirmed Limine configuration was correct:
"you will need to insert this line between the module_path: and comment: lines"
HARDWARE COMPARISON
For context, this same RTX 4060 Ti successfully works with:
VFIO on older platforms (X570/B550)
Native Windows installation on this motherboard
This suggests the issue is specifically with:
X870E + VFIO combination
Firmware restrictions on new chipset
Incomplete BIOS implementation
CONCLUSION
Despite extensive troubleshooting and correct configuration at every level (kernel, BIOS, VFIO), GPU passthrough fails due to a firmware-level restriction requesting "1:1 IOMMU mapping" that cannot be satisfied.
This appears to be either:
A BIOS bug requiring an update from MSI
A chipset limitation of X870E
Missing kernel/QEMU support for new hardware generation
Request to MSI Support: Please investigate firmware-level IOMMU handling on the MPG X870E Carbon WiFi and provide guidance or BIOS update to enable VFIO GPU passthrough.
TECHNICAL LOGS AVAILABLE
Complete dmesg output
libvirt/QEMU logs
VM XML configurations (all iterations)
BIOS screenshots
Full hardware specifications
System available for remote diagnosis if needed.
Report compiled: January 21, 2026
Testing duration: ~8 hours intensive troubleshooting
Configuration attempts: 15+ different approaches
Result: Unsuccessful - firmware restriction


VM Console (VNC) hangs after a while
Sun, 30 Nov 2025 12:19:03 +0000
Hi!
I have a Debian VM on my Unraid box, which is running fine so far. However, the VNC Console just stops working a few hours or days (it varies) after boot up of the VM. It just stops responding while the VM itself is running fine. Services are running, accessing the machine via SSH is possible, etc. Just VNC stops working, cursor is not blinking, and it does not accept any keyboard strokes:
Does anyone know how to fix this? Thx a lot!
Have a nice weekend
Thorsten



Legacy PCI Sound Card Passthrough Failure on Unraid 7.3.1 (Regression from 7.2.4)
Mon, 08 Jun 2026 04:51:46 +0000
User Introduction & Context
Hello,
I was forced to revert back to Unraid 7.2.4 after upgrading to 7.3.1 because the update completely broke my old Windows 10 VM that runs CasaTunes using a proprietary Creative Labs sound card. I use hardware passthrough, and it worked perfectly up until upgrading. I spent a significant amount of time attempting to troubleshoot this using various deep system modifications, but none of the structural changes worked. Reverting back to 7.2.4 instantly resolved my issues.
It would be great to upgrade to the latest stable Unraid release, but I feel completely stuck. I am required to run this specific Windows 10 VM because CasaTunes relies on this exact OS environment paired with their specially designed Creative Labs hardware to drive my multi-room home audio system via the CasaTunes mobile app and website.
Problem Description
After upgrading from Unraid 7.2.4 to Unraid 7.3.x, a long-standing Windows 10 VM ("Casatunes") lost access to its passed-through Creative Sound Blaster audio hardware. In Windows Device Manager, the audio zones showed translucent icons with Code 45 (Device Not Connected). Reverting the entire server back to Unraid 7.2.4 instantly and completely resolved the issue, indicating a regression or structural driver change in the newer Linux Kernel / QEMU stack regarding legacy bridge hardware power states or interrupt handling.
Hardware / IOMMU Context
The card in question is a legacy split-chip architecture utilizing an onboard PCIe-to-PCI translation bridge:
IOMMU Group 11: * [1102:7006] 01:00.0 PCI bridge: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG PCIe to PCI Bridge
[1102:0009] 02:00.0 Audio device: Creative Labs CA0110 [Sound Blaster X-Fi Xtreme Audio]
Comprehensive Troubleshooting Log (Everything Attempted)
1. Initial Storage/Motherboard Migration Issues
Symptom: Upgrading the VM template structure to modern defaults triggered an immediate Windows INACCESSIBLE_BOOT_DEVICE Blue Screen.
Fix: Temporarily changed the Primary vDisk Bus from VirtIO to SATA. This bypassed the Q35 PCIe layout storage controller conflict and successfully allowed Windows 10 to boot to the desktop.
2. Driver & Basic Interrupt Adjustments
VirtIO Tools: Repaired and validated the latest virtio-win-0.1.285-1.iso drivers inside the guest OS.
Legacy Interrupts: Because the Creative card relies on older line interrupts (INTx) instead of modern MSI, we enabled "VFIO allow unsafe interrupt remapping" in the global Unraid VM settings. The card still reported Code 45.
3. XML Hardware Routing & Slot Allocations
Attempted to isolate the audio endpoint (02:00.0) manually within the XML by forcing it to alternate virtual slots:
Attached directly to a clean virtual PCIe root port (bus='0x06').
Attached directly to a virtual PCIe-to-PCI Bridge (bus='0x05' slot='0x01').
Attached directly to the main virtual motherboard root complex (bus='0x00' slot='0x15').
Result: No change in Windows; device remained locked in a Code 45 state across all configurations.
4. Motherboard Chipset and Power State (D3) Adjustments
Syslinux Power Tweaks: Suspecting the new kernel was force-sleeping the idle hardware endpoint, we appended vfio_pci.disable_idle_d3=1 to the Unraid flash boot lines.
Machine Type Downgrades: Shifted the VM machine type sequentially backwards from pc-q35-10.2 down to pc-q35-7.2, pc-q35-6.2, and eventually completely reconstructed a flat PCI legacy layout using pc-i440fx-7.2 (including removing the itco watchdog device).
Option ROM: Disabled the hardware option ROM bar in the XML () to ensure the VM’s UEFI (pure-efi.fd) wasn't choking on the card's old 16-bit pre-boot code.
Result: The VM booted flawlessly on every chipset version, but Windows remained completely blind to the device.
5. Attempts to Isolate the Onboard Hardware Bridge (01:00.0)
Libvirt Block: Attempted passing the parent bridge chip via a standard  block, which failed validation with: “XML error: Non-endpoint PCI devices cannot be assigned to guests.”
QEMU Command Line Bypass: Attempted to use  to manually bind the physical bridge (01:00.0) at the root emulator level. This crashed the VM initialization completely with an Unraid core hook error: “Failed to bind device 01:00.0 to vfio-pci driver.”
Host Power Management Override: Attempted removing the bridge ID from the VFIO stubbing list entirely while adding pcie_port_pm=off to the Syslinux profile. This was meant to force the host's native pcieport driver to keep the hardware bridge pathway physically powered on so the VM could talk to the audio endpoint behind it.
Result: Followed by full cold AC electrical power cycles, this configuration still resulted in a persistent Code 45 error inside Windows.
Diagnostic Notes for Developers
Every software, firmware, power regulation, and architectural topology flag available in KVM/QEMU was deployed to keep the hardware awake and visible. The fact that the card works instantly on Unraid 7.2.4 but is completely unreachable under Unraid 7.3.x strongly implies that the newer Linux kernel completely changes how physical PCIe-to-PCI bridge controllers drop power states, or how legacy INTx line interrupts are isolated when a single endpoint within a multi-chip bridge group is passed to a guest.
unraid-mt-diagnostics-20260607-2240.zip unraid-mt-diagnostics-20260607-2250.zip


Software on Windows 10 VM "Sorry, this application cannot run under a virtual machine"
Fri, 05 Jun 2026 21:34:55 +0000
I know this isn't exactly an unraid specific question, but some of yall are straight up wizards. 

But I've set up a windows 10 VM via unraid, and when I'm attempting to run a specific software, i'm greeted with a 

"Sorry, this application cannot run under a virtual machine"

Now I understand its probably an anti-piracy measure, but I'm wondering if there is anything that I may be able to change in my vm set up to possibly get around this? 

( the software I use is a 3d rendering/modeling software called Agisoft Metashape, and would LOVE to be able to run this on my server rather than my main PC ) 

I know its a long shot, and I may just be better off biting the bullet and building a secondary machine, but running a VM cost me nothing compared to spending out the butt for current PC part prices. 
wind10XML.txt


libvirt.img is in-use, cannot mount
Fri, 06 Apr 2018 19:47:18 +0000


	Hi,



	 



	Bit of an issue, I was having a problem with one core on my CPU being maxed out so I was stopping dockers trying to trace it (eventually found it was the directory caching plugin).



	 



	During that I set 'Enable VM's' to off, but now I can't turn it back on, the error "root: /mnt/user/system/libvirt/libvirt.img is in-use, cannot mount" is showing up in the logs.



	 



	I'm sure a reboot would fix the issue but wondering if there's another way?



	 



	Thanks



	 



	 




How to stop VM machine type update to default 8.0 on each boot?
Tue, 02 Jun 2026 19:07:52 +0000
Hi all,
After upgrading my Unraid server to 7.3.1, the default VM machine type changed to Q35 8.0.
My macOS VM only works with Q35 6.0, but every time I reboot the server, the machine type is automatically changed back to Q35 8.0.
Is there a way to permanently lock the VM to Q35 6.0 and prevent Unraid from updating it on each boot?
Thanks,
wing


Unraid 7.3 Causing VM to Generate Libvert/BTRFS Errors
Wed, 27 May 2026 04:47:50 +0000
Hoping for support on this seemingly niche issue. I don't see anyone else discussing this specific problem.

I updated form 7.2.2 to 7.3 today, and immediately noticed an explosion of BTRFS 'corruption errors' being generated on my cache pool when my Windows 11 VM was running. After running Memtest (clean) and a scrub of my cache pool, I pulled everything off my cache and rebuilt it. During that time, I tried running my VM after moving the vDisk to my other SSD pool, and saw the same behavior:


I just checked my libvert logs for the VM, and I have multiple errors there as well:


I'm assuming something has changed with 7.3 that is causing my VM to generate these errors? Below is my XML, any help would be greatly appreciated!


  Win11_LTSC-new
  6621b335-dc0a-455a-fd7c-5e7666d0e68c
  
    
  
  38797312
  38797312
  
    
  
  16
  
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
  
  
    /machine
  
  
    hvm
    /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd
    /etc/libvirt/qemu/nvram/6621b335-dc0a-455a-fd7c-5e7666d0e68c_VARS-pure-efi-tpm.fd
    
  
  
    
    
    
      
      
      
      
      
      
      
      
      
      
      
      
      
    
    
      
    
    
  
  
    
    
    
  
  
    
    
    
  
  destroy
  restart
  restart
  
    /usr/local/sbin/qemu
    
      
      
      
      
      vdisk1
      
      
      
    
    
      
      
      
      
      
      
      
    
    
      
      
    
    
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
      
      
    
    
      
      
    
    
      
      
    
    
      
      
      
      
      
      
    
    
      
      
        
      
      
    
    
      
      
      
    
    
      
      
      
      
    
    
      
        
        
      
      
      
      
    
    
      
      
    
    
      
    
    
      
    
    
      
      
    
    
      
    
    
    
      
      
      
    
    
      
      
        
      
      
      
    
    
      
      
        
      
      
      
    
    
      
      
        
      
      
      
    
    
      
      
        
      
      
      
    
    
      
    
    
  
  
    +0:+100
    +0:+100
  



VM (Ubuntu 22.04) not mounting Shares and no ethernet if Shares configured
Tue, 02 Jun 2026 16:21:47 +0000
I recently uphraded a dev unraid server from 6.12 branch to 7.3.0, and then upgraded a VM with Ubuntu 20.04.4 to Ubuntu 22.04.4. 
Now I can't start the vm if I have Shares provided to the VM. 
I had this happen once before and then it was enough to update the netplan in the VM to define the correct ethernet interface. This no longer seems to work. 
The ethernet IF is defined as virtio-net and I have tried using e1000 and refreshing the mac address. This does not work. 
Once I remove the Shares defined I get ethernet access again in the VM. 
The vDisk uses VirtIO. I've tried adding just one Share using either 9P or Virtiofs but as soon as I do that the VM doesn't start with error "Start PXE ofver IPv4". Changing the ethernet IF to E1000 and back to virtio-net works. 
What could be the issue here?


manually removing VM definition
Tue, 02 Jun 2026 06:08:27 +0000
Hello there,
I have a VM definition I cannot get rid off. I once installed Macinabox. After fiddling around I removed the VM folder in the domains share.
Now I'm stuck with a VM entry on the management page, if I select remove VM, it will never end the process. I can't start or stop of course as nothing is there except the definition.
Can someone please explain where the definition is kept so I can delete it from the config file ?
It's just a pain,doesn't consume resources etc.
Thx for the help. Juergen


Kubuntu VM freezes after 7.3.1 upgrade ***UPDATED***
Sun, 31 May 2026 15:38:13 +0000
After upgrading to 7.3.1 from 7.2.4 without issue, now my Kubuntu VM freezes solid after a while and when clicking on Discover Software Center in VNC
Logs doesn't show any errors except:


This is the Audio device passed to the VM. It was set like this before the upgrade


In the VM edit:


Before upgrading, Kubuntu VM was working fine
Please, let me know if you need +info to resolve this issue
Thanks


Successfully running Roblox (Microsoft Store version) on my Windows 11 VM
Fri, 19 Jul 2024 05:17:38 +0000

	Ok after much trial and error I have finally got the UWP Roblox version to run on my Win11 VM, running on a Intel 11700k cpu. My 2080ti GPU, NVME SSD & MB NIC are bond to VFIO also.



	 



	Please understand I am by no means an expect and it’s been the hard work of others that have got me this far, It’s been nothing but guessing and trial and error on my end….lol

	

	Basically, when opening UWP Roblox, it starts but then closes after 20secs with no error etc. So, I applied XML edits that removed the “Virtual Machine” flag from  Task manger but still same issue.



	 



	So after scouring through the Unraid forums and google I found information regarding  XML commands found here



	https://github.com/zhaodice/qemu-anti-detection/issues/56  Basically, if the “model=0” was applied to the (added)  commands within the XML it allowed Roblox to work but with severe performance losses all round making the VM unusable.



	 



	Further scouring lead, me to




	which allowed me to change the “model” without the  commands section. So, a big SHOUT!!! out to @mackid1993 who’s hard efforts got me the result I required once again.



	 



	What I ended up doing was changing the  section of the xml based on the information provided from running the “virsh capabilities” cmd within the unraid console which revealed “Skylake-Client-noTSX-IBRS” but “-noTSX-IBRS” section resulted in severe VM performance loss also.



	 



	Changing it to  Skylake-Client has resulted in everything working better than it has ever before in my VM, seriously no joke, everything just works better now, I’m now seeing the AAA games really pushing the GPU now instead of the CPU maxing out. I have no idea why this is the case but it’s working.



	 



	So, I’m sharing what has worked for me in the hope it helps others @bmartino1



	 



	My original ,cpu> xml section was:


   mode='host-passthrough' check='none' migratable='on'>
     sockets='1' dies='1' cores='4' threads='2'/>
     mode='passthrough'/>
   


	 



	Which now is the following:


   mode='custom' match='exact' check='none'>
     fallback='allow'>Skylake-Client
     sockets='1' dies='1' cores='4' threads='2'/>
     policy='disable' name='hypervisor'/>
     policy='require' name='vmx'/>
   


	 



	The  from what I understand removed the Virtual Machine Flag seen in Task Manger and is required for Roblox to work



	 



	 This allows virtualization to be run within the VM, I require this to run “Bluestacks android emulator”



	 



	Hope this helps others!




Custom VM settings are overwritten
Fri, 29 May 2026 17:50:04 +0000
Hello,
I have no idea how I should describe the problem because it consists of a few things.
Recently, I started doing some optimizations on VMs and I noticed while I can set things like mq, rss, vCPU topology, etc.
While Unraid allows to set up some things (like physical cores that a VM should use), I saw that if I select 4 cores, it will force the config to present it to the guest as 2 cores with 2 threads, no matter whether physically it's an HT pair or not.
All in all, I could accept the fact that I need to change some things in the config directly, but the issue is, whatever I do, if I enter/edit the VM in the GUI, even when I don't make any changes, it will overwrite the config.
Is there a way to get around that? Except for never going into VM's edit menu that is.
Or maybe there's a way to edit the xml via GUI so it'll save all the custom entries, it's just that I don't see it?


Windows 10 VM: "Sorry, this application cannot run under a Virtual Machine"
Wed, 27 May 2026 16:31:47 +0000
I'm playing around the idea of offloading my 3d rendering work from my main PC to my unraid server, running a windows 10 vm. 

When I attempt to launch the software, I get a 

"Sorry, this application cannot run under a Virtual Machine" error box. 

the software is called "Agisoft Metashape" and I haven't found much at all online about running it in a VM. It may simply not be possible, but figured I'd see if there were any ideas for things I could attempt. 


Hardware: 12700k, cpu's pinned, and my 3060ti fully passed-tru to the VM.

Attached is my current XML set up. 

working VM.txt


Poor VM performance
Wed, 27 May 2026 11:25:59 +0000
I run a number of Virtual Machines on my server, mostly Windows Server 2022 and 2025.
General remote desktop performance of these VMs is poor. The stat menu has a significant amount of lag, for example.
The main VM I use in this way is SR1VDI01, which has 24 passthrough vCPUs (the server has 2x28c Skylake-SP Xeon CPUs). The Cores are not pinned. 64GB RAM, the server has 1536GB. It is using Q35-9.2 and OVMF TPM.
VHD is stored in .img format on NVMe storage, using ZFS over LUKS, via VirtIO. I have accessed this pool directly, without FUSE.
I am not sure what I can do to improve this?
tacgnol-core-diagnostics-20260527-1219.zip


7.3.0 QEMU High CPU usage
Tue, 19 May 2026 15:57:41 +0000
claron-cloud-diagnostics-20260519-1647.zip
Since updating to 7.3.0, when my VM is running either core 0 or 16 is pinned at 100%

I have traced the issue to QEMU but cannot resolve. I have tried various settings in the VM config. This issue is not linked to the VM OS as the core is pinned at 100% before the OS VM boots.



VM: Windows Server 2016 running Blue Iris/CCTV workload
Initial symptom:
One host CPU thread permanently pinned at ~100%
qemu-system-x86 consuming up to ~220% host CPU
Guest Windows CPU usage only ~9%
Host overall remained mostly idle (~88% idle)
VM configuration changes attempted
Reduced VM from:
16 vCPUs (8c/16t)
to 8 vCPUs (4c/8t)
Applied explicit CPU pinning:
VM vCPUs pinned to cores 1-4,17-20
Emulator/iothread pinned to 0,16
Added:
Disabled Hyper-V enlightenments:
removed entire  block
Disabled Windows dynamic tick:
bcdedit /set disabledynamictick yes
Set Windows power plan to High Performance
Storage changes attempted
Original VM used SATA emulation:
Installed VirtIO drivers inside Windows
Migrated all disks to VirtIO-SCSI
Added:
Retained:
cache='none'
io='native'
Tested with:
qcow2 system disk
raw physical disk passthrough devices
Network changes attempted
Original NIC config:
type='direct'
macvtap
eth2 mode='bridge'
Changed to:
virtio-net
Graphics/device emulation changes attempted
Removed:
VNC graphics
QXL video
USB tablet
watchdog
VirtIO ISO/CD-ROM
unused SATA/IDE devices


VMs won't autostart after motherboard replacement
Thu, 21 May 2026 19:51:21 +0000
as the title suggests, I replaced the mb and cpu recently.  When my unraid is booting up I get an error stating my vm's can't auto start. The interesting thing is that I can start them manually once I login to the unraid ui.



I've tried looking through the VM configuration and don't see anything obvious on why it's causing issues. Attaching diags.cybertron-diagnostics-20260521-1418.zip


Upgrade to Unraid 7.0.0, VMS unable to start: Execution error unsupported configuration: locking options are not supported by this virtiofsd
Tue, 28 Jan 2025 17:49:09 +0000

	I just upgraded to Unraid 7.0.0. On 6.12, I had a VMS running just fine with no issues. Now, when I try to start this virtual machine, I get the following error. I have no idea how to fix this, I can't find any posts anywhere about other people having this issue to reference from. Can you all help me?

	

	



	Execution error



	unsupported configuration: locking options are not supported by this virtiofsd

	

	When I go to the VM logs, it just says:

	2025-01-28 17:37:11.678+0000: shutting down, reason=failed




Help with GPU passthrough of AMD GPU in Windows 11 VM?
Sun, 14 Dec 2025 03:41:41 +0000
I've recently started having trouble with my Windows 11 VM with passing through an AMD 9070XT. It was running fine for a few months and I was gaming with zero issues. Now, I can only get the VM to boot if I use VNC graphics. I can have the GPU attached and have it boot, but if I go with just the GPU I get a black screen on my monitors. Here are the things I have tried. Currently running 7.2.2.
1. Booted into the VM and run DDU and then reinstalled the graphics drivers.
2. Recreated the but using the same passthrough NVME drive and I get the same issues. 
3. Tried both binding and un-binding the GPU in system devices
4. Switched machine types, currently on Q35-9.2
Not sure where to go next so any help would be awesome. Thanks in advance!


Updated to 7.3.0 pfsense vm has no network ports
Fri, 15 May 2026 04:39:44 +0000
I have updated unraid several times and never had any problems with this VM. Tonight I update from to 7.3.0 and my PF sense VM shows no network ports. Everything else seems to be working except for this virtual machine.
When PF sense boots it shows that the configuration is changed and no network ports were found and it just simply halts. I have all of the necessary configuration set because it worked on 7.2.3 without a problem
Do you have any ideas on how I might troubleshoot this issue



7.3.0 Windows VM GPU Video suddenly Black while Sound passes through (Solved)
Fri, 15 May 2026 02:10:22 +0000
7.2.6 and earlier Windows 11 VMs worked fine
Updated to 7.3.0 and the screen shows black however sound can be heard – even the VM boot screen which typically displays an ‘Unraid bios’ splash screen was black
 
After my first VM boot, I remoted into the desktop (using RustDesk) and updated the Nvidia driver for the 5060 Ti (1:00.0 & 1:00.1) – this allowed display passthrough to work just fine at this point in time. 
 
After rebooting the VM it is back to displaying a black screen while sound works fine.
Under System/Display/Advanced Display I can see my LG TV connected to the 5060 Ti.
Rebooting the entire Unraid server, and each time the VM is launched for the first time, it will display a non-black screen only AFTER  DDU and re-installing the NVIDIA driver. 
 
lspci – knn (kernel driver in use vfio-pci, looks fine)
 
Tools/system devices has 5070 Ti isolated to IOMMU group 17 and bound w/ green circles
 
Updating the machine from i440fx-9.1 to 10.2 had no effect
 
WHAT FINALLY SOLVED THE ISSUE:  Changed GPU Multifunction from N to Y
Hopefully this helps someone


GTX1080 Ti passthrough works only sporadically
Fri, 08 May 2026 20:29:52 +0000
Hi,
I´ve got a Windows 10 VM running on my Unraid 7.0.1 server.
A GTX1080 Ti is passed into the VM. In general, this works, but not all the time.
Pretty often, the GPU is not correctly included into the system, leading to a Code 12 error (not enough resources available) in Windows device manager and the Nvidia driver not being loaded.
GPU-Z is detecting the GPU correctly.
The funny thing is, that sometimes the GPU is correctly included and fully usuable after boot-up.
Any ideas where to look at?
EDIT: Another interesting thing I noticed: the vm only gets a network connection when I define VNC as the primary and the GTX1080 as the secondary graphics adapter. As soon as I define the GTX1080 as the primary and I boot up the vm, it doesn´t gets a network connection. It doesn´t respond to a ping and my DHCP server is not getting any DHCP request, so I guess the network driver doesn´t even get loaded.
Thanks,
Hocky