mans_

root@Marcus:~# cat /tmp/gpudata0000\:00\:02.0 {"period":{"duration":1014.881557,"unit":"ms"},"frequency":{"requested":0,"actual":0,"unit":"MHz"},"interrupts":{"count":0.985337,"unit":"irq\/s"},"rc6":{"value":100,"unit":"%"},"power":{"GPU":0,"Package":11.831377,"unit":"W"},"engines":{"Render\/3D":{"busy":0,"sema":0,"wait":0,"unit":"%"},"Blitter":{"busy":0,"sema":0,"wait":0,"unit":"%"},"Video":{"busy":0,"sema":0,"wait":0,"unit":"%"},"VideoEnhance":{"busy":0,"sema":0,"wait":0,"unit":"%"}},"clients":[]}root@Marcus:~#

+1

Why Unraid Should Support Passkeys for GUI LoginUnraid has grown far beyond a hobby NAS—it’s now used for home labs, small businesses, and mission-critical self-hosting. The login experience should reflect that maturity. Adding passkey (WebAuthn/FIDO2) support to the Unraid web GUI—similar to Tailscale’s username@passkey flow—would be a major step forward. Here are reasons this feature deserves priority: 1. Massive Security Upgrade (Phishing-Resistant by Design)Passkeys eliminate shared secrets entirely: No passwords to steal, reuse, brute-force, or phish Resistant to credential replay and MITM attacks Immune to weak or reused admin passwords For a system that often runs root-level services, this is a meaningful security improvement—not just convenience. 2. Removes the Weakest Link: PasswordsEven strong passwords are: Hard to manage Often reused Frequently stored insecurely in browsers or notes Passkeys leverage: Hardware security keys TPM / Secure Enclave Biometric unlock (Face ID, Touch ID, Windows Hello) This aligns Unraid with modern authentication best practices. 3. Faster, Cleaner Login ExperienceA passkey login is: One click / biometric prompt No typing (great for mobile and tablets) No password managers required For admins who log into Unraid frequently, this saves time every day. 4. Perfect Fit for Local & Remote Admin AccessUnraid GUIs are often accessed: Over LAN Via VPN (Tailscale, WireGuard) Through reverse proxies Passkeys work seamlessly across all of these scenarios and bind authentication to the real origin, preventing fake login pages. 5. Matches the Modern Stack Unraid Users Already UseUnraid users already rely on: Tailscale Cloudflare GitHub Google / Apple ecosystems All of these platforms already support passkeys. Unraid adopting the same standard would feel natural and expected. 6. No Cloud Dependency RequiredThis can be implemented using: Standard WebAuthn APIs Local credential storage Optional fallback to password login No requirement for Unraid accounts, external identity providers, or always-online validation. 7. Backward Compatible & OptionalPasskeys don’t need to replace passwords: Enable per user Allow mixed authentication (password + passkey) Ideal for gradual adoption Admins who want passwords can keep them. Power users can upgrade. 8. Positions Unraid as a Forward-Looking PlatformAdding passkeys would: Signal strong security leadership Differentiate Unraid from other NAS solutions Reduce support issues related to compromised credentials This is the kind of feature users brag about. Suggested UX Conceptunraid_admin@passkey → Browser / OS prompts for biometric or security key → Instant login Simple. Secure. Modern. Bottom line: Passkey support isn’t just a nice-to-have—it’s the future of authentication. Implementing it in the Unraid GUI would significantly improve security, usability, and user trust while keeping Unraid competitive with modern infrastructure tools like Tailscale. This is a feature worth building.

@SimonF Please let me know if you need more info !

The power draw bar was perfectly working on 7.1.4. Now it is all white again on 7.2.3. I had the same bios for both the versions. Clearly this is not my bios, can you please look into it and fix it when you get time? Thank you for your work !

I updated from 7.1.4 to 7.2.3 and the plugin "check for update" gives the error Checking connectivity ... No response, aborting! I do have controld.com DoH (ads+malware) filter which worked perfectly for unraid versions 6.xx.x to 7.1.4 where the plugin update will give no error like above. Now only if I turn off this DoH resolver, my updates work in 7.2.3. "Check for updates" doesn't work on the docker tab too. I am trying to understand what changes were made in 7.2.3 and fix them? marcus-diagnostics-20251223-1414.zip

Hi ! I looked throughout the internet and wasn't able to find anyone having a same idea as me to use 2xhdd on the PSU side. Can you please tell me what you used to mount one top of the other?

@binhex doesnt connect to VNC on unraid 7.1.2. what is the fix?

@SimonF I have a 14900K and the black bar for power draw is not seen, it is just white. All options enabled on the plugin settings and on the latest plugin version. Unraid version is 6.12.15. Active apps icon is also missing. Its actually jellyfin. Prior to the update, it was working properly.

Then where only will we use the ipv4 of the jellyfin container? My docker containers dont have ipv6 which is the issue here. I use bridge network and it doesn't work. It still goes to the unraid webui this was your initial advice

@JorgeB Hi, I saw you commented on another post related to ipv6. Can you please help my containers get ipv6 via dhcpv6 or any other viable method for me? I am not sure, but this post here says to use macvlan for dhcp. Please support, thank you!

I can connect to my unraid login page via jellyfin.domain_name.com, but not jellyfin itself. My caddy config is as follows: jellyfin.domain.xyz, www.jellyfin.domain.xyz { reverse_proxy http://172.17.0.12:8096 } 172.17.0.12:8096 is internal jellyfin ip which is running on docker bridge network

Can you please tell me how? I can follow instructions well. I have a domain and setup nginx. Please, thank you!

Hi unraid team! I have tried and searched for several days and I am unable to figure out how to do the mentioned in the title. I have even reached out on the discord and was told the user base is very small and asked me to move to the forums. REASON: Tailscale does not stream jellyfin because I am under CGNAT. I am forced to use tailscale DERP severs. I have tried several times, and it doesn't work like it does for others in other parts of the world. According to https://tailscale.com/kb/1232/derp-servers, "Tailscale runs DERP relay servers distributed around the world to link your Tailscale nodes peer-to-peer as a side channel during NAT traversal, and as a fallback in case NAT traversal fails and a direct connection cannot be established." So ipv6 is my only option and reverse proxy on it. SETUP DETAILS: I can confirm I am able to connect to the unraid gui via http ipv6 remotely after setting ipv4+ipv6 in unraid gui and some settings in my OpenWrt router. I followed this guide and changed to macvlan -- unraid guide link When I inspect docker custom network bond0 it has no ipv6 enabled by default. I have no idea why this will be the case? I believe because of this bond0 setting when assigned to a container, is not getting ipv6 via dhcp. And for bridge it is enabled but it is not macvlan driver. root@Marcus:~# docker inspect network bridge [ { "Name": "bridge", "Id": "67da0ca0768313c1d78b6fcc9a2e0155dd2637ff448633d36d94f3895865ac42", "Created": "2025-04-06T15:31:37.995198845+05:30", "Scope": "local", "Driver": "bridge", "EnableIPv6": true, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.17.0.0/16", "Gateway": "172.17.0.1" }, { "Subnet": "fd17::/64", "Gateway": "fd17::1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { #redacted rest of the result root@Marcus:~# docker inspect network bond0 [ { "Name": "bond0", "Id": "12d68ab11cc0c49db92450d6c1643ee0619eb7e65598992782278c6dc65a2f79", "Created": "2025-04-06T15:31:38.99571313+05:30", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.86.0/24", "Gateway": "192.168.86.1", "AuxiliaryAddresses": { "server": "192.168.86.52" } } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": { "parent": "vhost0" }, "Labels": {} } ] Error: No such object: network root@Marcus:~# EXPECTED RESULT: I have dhcpv6 setup on my openwrt and want each docker container to receive ipv6 via dhcpv6. From there, I can allow firewall rule to access it. As I confirmed previously, I am able to connect to unraid gui via ipv6. I wish to get the same result for each docker container, and I believe macvlan will help me achieve this. Kindly, please provide me with the steps involved in doing this. Thank you!

So intel will support 12th gen alder lake but not 13th & 14th gen raptor lake? Or will 13th & 14th be supported because they essentially have the same iGPU?

Whichever feature that is necessary for nested VM. I know vmx is one of them

Hi @SimonF, did you get time to look into this?

Thank you so much for getting back. The below is the XML after VM is started. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='24'> <name>Windows 11_code</name> <uuid>966aae06-dea8-d7c4-7dc6-91d9b803b0fa</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>46661632</memory> <currentMemory unit='KiB'>46661632</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>28</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'/> <vcpupin vcpu='8' cpuset='12'/> <vcpupin vcpu='9' cpuset='13'/> <vcpupin vcpu='10' cpuset='14'/> <vcpupin vcpu='11' cpuset='15'/> <vcpupin vcpu='12' cpuset='16'/> <vcpupin vcpu='13' cpuset='17'/> <vcpupin vcpu='14' cpuset='18'/> <vcpupin vcpu='15' cpuset='19'/> <vcpupin vcpu='16' cpuset='20'/> <vcpupin vcpu='17' cpuset='21'/> <vcpupin vcpu='18' cpuset='22'/> <vcpupin vcpu='19' cpuset='23'/> <vcpupin vcpu='20' cpuset='24'/> <vcpupin vcpu='21' cpuset='25'/> <vcpupin vcpu='22' cpuset='26'/> <vcpupin vcpu='23' cpuset='27'/> <vcpupin vcpu='24' cpuset='28'/> <vcpupin vcpu='25' cpuset='29'/> <vcpupin vcpu='26' cpuset='30'/> <vcpupin vcpu='27' cpuset='31'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/966aae06-dea8-d7c4-7dc6-91d9b803b0fa_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='custom' match='exact' check='full'> <model fallback='forbid'>qemu64</model> <topology sockets='1' dies='1' cores='28' threads='1'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='lahf_lm'/> <feature policy='disable' name='svm'/> </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/exos/trackersexos/vms/Windows11_code/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/exos/trackersexos/vms/isos/Win11_23H2_English_x64v2.iso' index='2'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/exos/trackersexos/vms/isos/virtio-win-0.1.248.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='pci' index='3' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='3'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='4' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='4'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='pci' index='5' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='5'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='6' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='6'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:60:7b:9f'/> <source bridge='br0'/> <target dev='vnet20'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-24-Windows 11_code/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' 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'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0d' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> And below is XML before VM started. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11_code</name> <uuid>966aae06-dea8-d7c4-7dc6-91d9b803b0fa</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>46661632</memory> <currentMemory unit='KiB'>46661632</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>28</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'/> <vcpupin vcpu='8' cpuset='12'/> <vcpupin vcpu='9' cpuset='13'/> <vcpupin vcpu='10' cpuset='14'/> <vcpupin vcpu='11' cpuset='15'/> <vcpupin vcpu='12' cpuset='16'/> <vcpupin vcpu='13' cpuset='17'/> <vcpupin vcpu='14' cpuset='18'/> <vcpupin vcpu='15' cpuset='19'/> <vcpupin vcpu='16' cpuset='20'/> <vcpupin vcpu='17' cpuset='21'/> <vcpupin vcpu='18' cpuset='22'/> <vcpupin vcpu='19' cpuset='23'/> <vcpupin vcpu='20' cpuset='24'/> <vcpupin vcpu='21' cpuset='25'/> <vcpupin vcpu='22' cpuset='26'/> <vcpupin vcpu='23' cpuset='27'/> <vcpupin vcpu='24' cpuset='28'/> <vcpupin vcpu='25' cpuset='29'/> <vcpupin vcpu='26' cpuset='30'/> <vcpupin vcpu='27' cpuset='31'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/966aae06-dea8-d7c4-7dc6-91d9b803b0fa_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='custom' match='exact' check='none'> <model fallback='forbid'>qemu64</model> <topology sockets='1' dies='1' cores='28' threads='1'/> </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/exos/trackersexos/vms/Windows11_code/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/exos/trackersexos/vms/isos/Win11_23H2_English_x64v2.iso'/> <target dev='hda' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/exos/trackersexos/vms/isos/virtio-win-0.1.248.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='pci' index='3' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='4' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='pci' index='5' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='6' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' 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:60:7b:9f'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' 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'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <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='0x1e' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0d' function='0x0'/> </memballoon> </devices> </domain> What I am trying to achive here is enable and disbale cpu features automatically. I did this by using below XML. First, my VM did not start because I enabled hyperv in the VM. I used the below code and cpu features were enabled and disbled automatically after running VM. I switched to GUI and tried to pass through igpu and after that it was never enabling and disbaling cpu features automatically. I am trying to replicate that and it is never happening again. What I mean by "enable and disbale cpu features automatically" is when model fallback is allow it automatically chooses features, below is the code that worked. <cpu> <cpu mode='host-model' check='partial'> <model fallback='allow'/> </cpu> The issue is, please view the attached image. Just because vmx and other options are not enabled in the XML its not working. At this point, I am just trying to enable vmx and other options to successfully do nested VM. WSA dev on discord said without passing igpu it may work, and there are chances for my rig.

There's another issue which I am facing too and very annoying and pissing off. <cpu mode='host-model' check='partial'> <model fallback='allow'>Broadwell-noTSX-IBRS</model> <topology sockets='1' dies='1' cores='28' threads='1'/> <feature policy='require' name='ss'/> <feature policy='require' name='vmx'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='clflushopt'/> <feature policy='require' name='clwb'/> <feature policy='require' name='sha-ni'/> <feature policy='require' name='umip'/> <feature policy='require' name='pku'/> <feature policy='require' name='waitpkg'/> <feature policy='require' name='gfni'/> <feature policy='require' name='vaes'/> <feature policy='require' name='vpclmulqdq'/> <feature policy='require' name='rdpid'/> <feature policy='require' name='movdiri'/> <feature policy='require' name='movdir64b'/> <feature policy='require' name='fsrm'/> <feature policy='require' name='md-clear'/> <feature policy='require' name='stibp'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='avx-vnni'/> <feature policy='require' name='xsaves'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='ibrs'/> <feature policy='require' name='amd-stibp'/> <feature policy='require' name='amd-ssbd'/> <feature policy='require' name='rdctl-no'/> <feature policy='require' name='ibrs-all'/> <feature policy='require' name='skip-l1dfl-vmentry'/> <feature policy='require' name='mds-no'/> <feature policy='require' name='pschange-mc-no'/> <feature policy='disable' name='hle'/> <feature policy='disable' name='rtm'/> <feature policy='disable' name='mpx'/> </cpu> The above is my XML before starting the VM Below is what it becomes after starting the VM, and it doesn't start the VM. I want all the above features but I believe that can happen only with model fallback "allow" but after staring the VM it turns to "forbid", no matter what. I have a 14900k. The only way I can turn on the VM is to choose qume64 from the GUI but vmx and other features are not enabled that way. Below is what it becomes after starting the VM, and it doesn't start the VM. <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Skylake-Client-IBRS</model> <vendor>Intel</vendor> <topology sockets='1' dies='1' cores='28' threads='1'/> <feature policy='require' name='ss'/> <feature policy='require' name='vmx'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='clflushopt'/> <feature policy='require' name='clwb'/> <feature policy='require' name='sha-ni'/> <feature policy='require' name='umip'/> <feature policy='require' name='pku'/> <feature policy='require' name='waitpkg'/> <feature policy='require' name='gfni'/> <feature policy='require' name='vaes'/> <feature policy='require' name='vpclmulqdq'/> <feature policy='require' name='rdpid'/> <feature policy='require' name='movdiri'/> <feature policy='require' name='movdir64b'/> <feature policy='require' name='fsrm'/> <feature policy='require' name='md-clear'/> <feature policy='require' name='stibp'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='avx-vnni'/> <feature policy='require' name='xsaves'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='ibrs'/> <feature policy='require' name='amd-stibp'/> <feature policy='require' name='amd-ssbd'/> <feature policy='require' name='rdctl-no'/> <feature policy='require' name='ibrs-all'/> <feature policy='require' name='skip-l1dfl-vmentry'/> <feature policy='require' name='mds-no'/> <feature policy='require' name='pschange-mc-no'/> <feature policy='disable' name='hle'/> <feature policy='disable' name='rtm'/> <feature policy='disable' name='mpx'/> </cpu> What I mean to say is when I first implemented the fallback=allow code. It automatically chose the features to enable and disable and all were listed. I am not able to make it work again. <cpu> <cpu mode='host-model' check='partial'> <model fallback='allow'/> </cpu> The above is the code I used the first time to enable fallback automatically and all features were enables automatically after starting VM via fallback "allow"

I am using SR-IOV from unraid CA applications and can successfully pass through igpu independently. But when I use nested VM features like "Virtual Machine Platform Enabled", "Windows Hypervisor Platform Enabled" in the same SR-IOV Windows VM then the VM does not boot and that error is in my previous post.

Hi! But were you able to pass through intel igpu and get WSL working? I need help with this. WSA needs igpu, nested vm and ssd like you said to work. The error is in the syslog attached and I don't understand it. Like I said, I can only do either one but not both, which is the issue I am facing. Sep 20 08:49:31 Marcus kernel: i915 0000:00:02.3: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.4 (0000000000000000) Sep 20 08:49:31 Marcus kernel: i915 0000:00:02.3: [drm] *ERROR* GT0: IOV: Found interface version 0.1.4.1 The above is the error I see in the syslog.

WSA - https://github.com/MustardChef/WSABuilds For WSA to work, nested VM is necessary along with intel igpu. The issue is I am successfully able to do only one at a time and not both together. That is, I am able to pass through igpu via sr-iov or access nested vm with hyper-v enabled in the vm but not both together. How do I accomplish to make both work together? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11_code</name> <uuid>966aae06-dea8-d7c4-7dc6-91d9b803b0fa</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>46661632</memory> <currentMemory unit='KiB'>46661632</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>28</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'/> <vcpupin vcpu='8' cpuset='12'/> <vcpupin vcpu='9' cpuset='13'/> <vcpupin vcpu='10' cpuset='14'/> <vcpupin vcpu='11' cpuset='15'/> <vcpupin vcpu='12' cpuset='16'/> <vcpupin vcpu='13' cpuset='17'/> <vcpupin vcpu='14' cpuset='18'/> <vcpupin vcpu='15' cpuset='19'/> <vcpupin vcpu='16' cpuset='20'/> <vcpupin vcpu='17' cpuset='21'/> <vcpupin vcpu='18' cpuset='22'/> <vcpupin vcpu='19' cpuset='23'/> <vcpupin vcpu='20' cpuset='24'/> <vcpupin vcpu='21' cpuset='25'/> <vcpupin vcpu='22' cpuset='26'/> <vcpupin vcpu='23' cpuset='27'/> <vcpupin vcpu='24' cpuset='28'/> <vcpupin vcpu='25' cpuset='29'/> <vcpupin vcpu='26' cpuset='30'/> <vcpupin vcpu='27' cpuset='31'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/966aae06-dea8-d7c4-7dc6-91d9b803b0fa_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='14' 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/exos/trackersexos/vms/Windows11_code/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/exos/trackersexos/vms/isos/Win11_23H2_English_x64v2.iso'/> <target dev='hda' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/exos/trackersexos/vms/isos/virtio-win-0.1.248.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <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> <controller type='pci' index='0' model='pci-root'/> <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='pci' index='3' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='4' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='pci' index='5' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='6' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:60:7b:9f'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' 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'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <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='0x1e' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x10' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> This is my current xml and the vm starts, but it is a black screen in VNC. Any kind of help is highly appreciated. Thank you! marcus-syslog-20240920-0515.zip marcus-diagnostics-20240920-1040.zip

Thank you for your work and reply. I just have a few more questions. Will a 4090 work? (I see no reason why it won't but you say something about hardware incompatibilities, so just confirming) If yes, is possible to pass through dual (2x4090) GPU to the SAME container with this plugin driver?

@ich777 Hi! I would like to know if you are using https://github.com/NVIDIA/nvidia-container-toolkit for this plugin? If yes, is this plugin up to date with the nvidia releases in the link shared? If yes, why is the nvidia container toolkit version not mentioned in the driver? I am planning to install pytorch and other python packages in a docker and wondering how reliable this plugin is or is it possible to install the driver directly on top unraid host? Thank you!

When I try to passthrough UHD770 intel igpu of i9-14900k the boot gets stuck here, I have verified this by not passing and not binding vfio for the igpu -- then in windows it shows it shows 770, the igpu but with a exclamation mark on it and when i try to install drivers, i get the error -- Any idea why this is happening and how to fix?