allroy1975

I'm currently struggling like the dickens to get my win 11 passthrough working with Nvidia in a 3 monitor configuration. Care to tell me about the custom utility? just cuz i've exhausted damn near everything else.

Incidentally here's a copy of my XML from the Windows 10 version of this computer that DOES work. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>1. MusicBox</name> <uuid>28c77f08-edd1-a1d2-444b-5d0232222f8b</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10" webui=""/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='5'/> <vcpupin vcpu='1' cpuset='13'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='14'/> <vcpupin vcpu='4' cpuset='7'/> <vcpupin vcpu='5' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/28c77f08-edd1-a1d2-444b-5d0232222f8b_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='3' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='yes'/> <timer name='hypervclock' present='yes'/> </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' discard='ignore'/> <source file='/mnt/user/VM-SSD/1. MusicBox/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='ignore'/> <source file='/mnt/disks/SATA_SSD/Vdisk2.img'/> <target dev='hdd' bus='virtio'/> <serial>vdisk2</serial> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </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='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f7:f2:d9'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/VMs/vbios/evga-GTX-1050ti-ur6.11.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x1ba6'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain>

I always have some thing that seems a little off. This is a BIG off. I have 3 monitors set up on my 1050ti and I can't get monitor spanning to work correctly anymore for the life of me. I've been staying up way too late every night for the last 4 nights. I'm exhausted, but I'm convinced there's something I'm doing wrong. I've made a LOT of VMs in unraid just for different little things here and there. I've been passing this video card through for the past 6 years and haven't really experienced anything this brutally frustrating. I've got everything updated at this point (which is nice). I have the newest Bios on my asus 370-pro motherboard. I'm on Unraid 7.1. I'm trying to install Windows 11 24h2 (but i've also tried old 22h2 with the same results) which is the newest from MS. I had some old Win10 VMs that started having problems LIKE this, but not quite to this extent. I've got an existing Win11 machine that ...let's just say I f'd something up and it's gone. but it was working correctly. So i figured "welp, everything is on my Unraid server, I didn't NEED that install of Windows. I'll just rebuild Win11, no harm no foul. but it JUST WON'T WORK. I've USUALLY built my VMs by starting in VNC getting the OS up and running install chrome remote destkop and setting up RDP so i have ways in while i install video drivers. When i try that the Video on the monitors just go like....a milky grey\white color and RDP and Chrome RD don't work. The keyboard will work until the windows 11 "it's time to log in" chime happens. then it goes unresponsive. I mean...the num and cap lock just stop. only a force stop will fix it. I've dumped my vbios using Space Invader's script. I moved the 1050Ti out of the unraid server to a windows box and dumped it there using GPU-Z and SIV. The SIV one actually works without editing. and by "works" i mean.....I can boot and I see the Unraid boot screen in Windows. Like if i was booting a bare metal Dell, I'd see the Dell windows boot screen. I can actually build windows 11 right from there, but I can't get the drivers to load correctly. In the past I've only seen that old TianoCore screen. so....the Unraid one is nice. Sometimes when i get Windows up I can install Nvidia drivers and I'll have 3 monitors...but the fonts look pretty terrible in web browsers. nothing is smooth like it should be. It doesn't feel correct. and if I reboot or shut down the VM, i'm back to 1 monitor. Just the Display port. When I boot the server, bios shows on the DVI monitor. but I want it to span Display Port, DVI and HDMI. Windows knows they're there. But i can't configure them. for the last couple years I have been rocking pretty well without a vbios file at all. but that doesn't work anymore. that locks up windows with the milky screens. My config looks like this: kernel /bzimage append isolcpus=5-7,13-15 video=efifb:off initrd=/bzroot I always pin my VM to 5\13, 6\14, 7\15. I suspect something is up with the vbios. like it's abnormal. but I can't say exactly why. I've tried Q35 7.1, 7.0, 6.0, 6.1 and i440 fx 6 7 and 9...i think. I've tried with multifunction on, off. having the audio together and separate from each other. I'm also passing through a soundcard from my mobo. this all sounds crazy and on the one hand i think "you're nuts". but it used to work! it Works in Linux! I can boot a linux (specifically Zorin, which i believe is based on Ubuntu...without using a vbios) vm and span the 3 monitors I've attached my diagnostics and here is my XML from the VM i'm currently typing this on. A sad single screened VM. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='4'> <name>Trash11</name> <uuid>34ad2903-a6fc-838d-caac-e8625827ce07</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm" webui="" storage="default"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='5'/> <vcpupin vcpu='1' cpuset='13'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='14'/> <vcpupin vcpu='4' cpuset='7'/> <vcpupin vcpu='5' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/34ad2903-a6fc-838d-caac-e8625827ce07_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='3' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> </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' discard='unmap'/> <source file='/mnt/user/VM-SSD/Trash11/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='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Installs/Appz/Microsoft/Windows 11/Win11_micro_24h2 Enterprise.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/user/VM-SSD/VirtIO/virtio-win-0.1.266.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='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='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:e1:05:3c'/> <source bridge='br0'/> <target dev='vnet3'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' 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='/run/libvirt/qemu/channel/4-Trash11/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='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/VMs/Atier/GeForce GTX 1050 Ti [GP107-A]-86.07.39.00.52.rom'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x1ba6'/> <address bus='1' device='2'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='1'/> </hostdev> <watchdog model='itco' action='reset'> <alias name='watchdog0'/> </watchdog> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> If I'm missing something super obvious I'll be so happy. Please help me community. I feel like my eyes are going to bleed. tower-diagnostics-20250306-2322.zip.crdownload

no way! I'm just a home studio nerd, but ....very similar. I'm trying to get my recording server back up and running. I have a Win10 one from a few years ago where the 3 monitors work, but I'd like to stay current with 11...if at all possible. but I'm rocking a little Presonus Studio 24 as my interface. Kinda hilarious to me that we're using stuff for similar reasons. Anyway, yeah, that doesn't help ME but I appreciate the response!

I believe I'm having this exact same problem. Windows 11 is showing all the monitors, but I can't display to all of the monitors. I've nearly lost my mind trying to troubleshoot this over the last 3 days (which turn into very very late nights) I'm also running a 1050ti card and I'm hoping you can give me a tip on a driver or or an exact setting in the xml that might help. If you even remember this problem, or get notifications from Unraid forums about this.

I'm just another lost soul who found your post and it worked perfectly, i wanted to say thank you! Add me to the list of fools who spent HOURS trying to fix this themselves - unsuccessfully. depends how you're getting to it i think. @ghost82 broke it down pretty well right there, i think.

just wanted to say thanks, i don't know how long i would have futz around before I tried a reboot. lol.

my server is called tower. I have a dns entry for it, and had a nginx Proxy host set up for it. I was seeing the same thing. I got rid of the tower proxy host, created a proxy host for "unraid" and a coresponding dns entry.....I did this around midnight last night and haven't seen a single Exited on signal 6 all day. I've also had many tabs open to my unraid dns and a whole bunch, maybe ALL of the docker containers i created proxys for. i'm not sure WHY that'd fix it....but it seems to have worked for me. I also posted about it here: but wanted to suggest it in both threads i found when trying to troubleshoot the issue. I'd love to hear if that helps for other people....

hey @jademonkee did you have to DO anything? I feel like i'm having a real similar issue. I had some system problems around the beginning of the month and now that i'm stable again, I keep seeing "Synchronizing block information" but it climbs to 100% then just starts over. It looks like i changed the memory in the RIGHT place 😉 a few days ago to 3072 from 2048 which had been working fine. or did you just let it sit and after a LONG time it finally got itself all synced up and is working correctly?

I'm constantly talking about this software to friends and coworkers. Been around since the 4.5 days..... The whole experience just keeps improving! Keep it up!

I started over yesterday too. After using (lazily relying on) the crashplan Desktop Docker, it lost it's mind yesterday and I didn't do enough research, so I dropped back and punted. following Leifgg's tutorial and notes: I reinstalled the crashplan plugin, copied (via putty) the .ui_info and .identity to /boot (\\tower\flash) and from there I could copy and paste them to C:\programdata\crashplan ...then simply edited .ui_info and added my IP address to the file where it belonged. I connected to the engine and signed in....it promptly kicked me out. checking the logs I watched until each upgrade was complete. It seemed to go in about 4 steps. Something like 4.3.0 to 4.3.1 to 4.3.2 to 4.4.0 and then finally 4.4.1. I would restart the docker after each update, then once my apps\crashplan\engine_output.log finally said: [10.03.15 17:26:09.047 INFO main com.backup42.service.CPService] CPVERSION = 4.4.1 - I copied those 2 files again and edited .ui_info and changed to my and boom. I'm in business again. many thanks to Leifgg's notes! It really wasn't that hard once I saw that simple post and actually quit relying on that desktop It does suck that after every restart of the docker crashplan is changing those files. I was going to write a little batch file to copy those 2 files from \\tower\dockers\apps\crashplan\id\ to c:\programdata\crashplan and then do a find 127.0.0.1 and replace it with my IP and then launch Crashplan, but...I can't copy from that crashplan\id folder as myself. grr....that's why i copied them to /boot first. probably not the cleanest place..but..it worked in a pinch. The only version of Crashplan for windows I used during this whole thing was x64 4.4.1, so don't worry about installing an old version of the desktop app to connect to the fresh Crashplan docker, even though the docker starts out at 4.3.0, you can connect. Just...give it some time and restart the docker until it's at 4.4.1 and I think things will work.

looks like 4.4.0 was skipped. 4.4.1 is indeed available now: https://download.code42.com/installs/win/install/CrashPlan/jre/CrashPlan-x64_4.4.1_Win.exe

This needs to be added to the OP and/or the WIKI please seriously. I feel lucky to have found this. Maybe running a desktop adds a little more overhead, but I was pulling my hair out trying to figure this out. It's about 1000x less stressful to just RDP to a Linux desktop, and this document was REALLY well done. So simple. THANK YOU!!!!

it's the crashplan service. when it runs it assumes you want to connect to it on your windows box. Go into Services (services.msc) and change the crashplan service to Manual or Disabled. Then your .ui_info file will survive a reboot. I'm on a brand new Crashplan docker setup and changing my Crashplan 4.4 .ui_info file to read: 4243,unRAID,10.168.1.41 got me connected once. I logged into my existing account. Crashplan shows that Tower (with a new GUID) logged in. then it threw a "crashplan has been disconnected from the backup engine" and I can't get it to re-connect. I just get that same message over and over again. I eventually want it to take over for my old "tower" exact same hardware, just upgraded to 6 from 5 of Unraid. But first I gotta get logged in to the engine! any ideas?