JustinChase

Thanks for that link. Looks like I can just wait for an unRAID update to fix it, which I'm fine with.

Recently I noticed this docker is showing "unavailable" for version on the docker page. I haven't done anything with this for a long time. i went into it to edit and "edited" a field, without actually changing anything, which let me "apply" the setting again, and it started fine, but still shows unavailable for the version. The log file does show the version of both the program and the docker, but the docker screen in the unraid GUI will not show a version. checking for updates does not change this.

I'm fine with just waiting as it pretty much always does eventually connect. But, out of curiosity, how would i change the endpoint? I can see from the log file that it's connecting to nl-amsterdam.privacy.network but I can't see any settings in the docker setup that relate to this location. Again, no issue for me to just wait and maybe try again, since I don't restart the server very often, I'm mostly just curious. thanks

I noticed that parity check was still running, so I paused that (so happy this functionality was added a while back) and restarted the docker. It still took a bit to get up and running. It seems to need to obtain the json at least twice in the process, but it did successfully complete this time. When I opened the GUI I saw the prompt dialog box for the briefest of time, then it disappeared, and I was into deluge without any input from me. So, SUCCESS!! thank you again for taking the time to do this!

Wow, you do work fast! Thank you for this. I have made the changes and saved. Just waiting for it to fully start to test... ...no luck. unable to get json file... [info] Adding 209.222.18.222 to /etc/resolv.conf 2023-02-03 09:13:24,327 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2023-02-03 09:13:24,335 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2023-02-03 09:13:24,340 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2023-02-03 09:13:24,345 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2023-02-03 09:13:24,349 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2023-02-03 09:13:24,352 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2023-02-03 09:13:24,356 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2023-02-03 09:14:10,535 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 12 retries left [info] Retrying in 10 secs... 2023-02-03 09:14:51,604 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 11 retries left [info] Retrying in 10 secs... 2023-02-03 09:15:32,671 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 10 retries left [info] Retrying in 10 secs... 2023-02-03 09:16:16,739 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 9 retries left [info] Retrying in 10 secs... 2023-02-03 09:16:57,807 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 8 retries left [info] Retrying in 10 secs... 2023-02-03 09:17:38,879 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 7 retries left [info] Retrying in 10 secs... 2023-02-03 09:18:22,948 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 6 retries left [info] Retrying in 10 secs... 2023-02-03 09:19:04,016 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 5 retries left [info] Retrying in 10 secs... 2023-02-03 09:19:42,083 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 4 retries left [info] Retrying in 10 secs... 2023-02-03 09:20:20,150 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 3 retries left [info] Retrying in 10 secs... 2023-02-03 09:20:58,218 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 2 retries left [info] Retrying in 10 secs... 2023-02-03 09:21:36,286 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 1 retries left [info] Retrying in 10 secs... 2023-02-03 09:21:46,289 DEBG 'start-script' stdout output: [crit] Unable to successfully download PIA json to generate token for wireguard, exiting script... 2023-02-03 09:21:46,289 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23208325329152 for <Subprocess at 23208325323968 with name start-script in state RUNNING> (stderr)> 2023-02-03 09:21:46,289 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23208325329200 for <Subprocess at 23208325323968 with name start-script in state RUNNING> (stdout)> 2023-02-03 09:21:46,289 WARN exited: start-script (exit status 1; not expected) 2023-02-03 09:21:46,289 DEBG received SIGCHLD indicating a child quit It had been taking several minutes to work previously, so I'm not sure if this is a new issue, or just an extension of what was already a long process. I wonder if I have something else set incorrectly that it was (and still is) taking so long to get this json. I'll be here for a little while still this AM, if you have more for me to test, otherwise I'll be back this afternoon, and can test then. Thank you again!!

I just waited a while and tried again, and both deluge and sabnzbd are running. I changed the password to none, then rebooted deluge. it didn't start right away, so I'm waiting again... ...wait over. Your solution worked!! interface came right up, no password prompt!! You are awesome. Wish I hadn't waited almost a decade to inquire again about it

some days i just hate computers! I tried adjusting the session timeout to be about 10 years, from a terminal, using MC to navigate to and open the web.conf file. Saved and started deluge. It was "unable to connect" I figured I entered too large a number. I changed it back. Deluge refuses to start. I restored the web.conf.bak file and restarted, still fails to restart log file says this... 2023-02-02 13:34:48,919 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' I didn't change anything to do with that. I don't remember setting it to wireguard, so i tried openvpn, still wouldn't start I checked the sabnzbd docker, and it is also set to wireguard. I changed it back in deluge, same issue. ARRRGGG!!! I'll troubleshoot this issue later. I thought/hoped this would be a 10 second test. I do not have hours to spend on this right now. I'll try your solution above once I get it running normally again. Thanks again for all your help!

Thank you for that solution, but I really just don't want to even see the prompt. It honestly makes no sense to me why the deluge creator even has it in there. none of my other dockers require a separate login, so there must be some way to just remove this prompt altogether. I don't know enough programming to find the cause and remove it myself. I have to believe someone smarter than me has been annoyed by this and has 'fixed' this, but I cannot figure out how. Is there some other fork that disables this?

Sorry if this has been covered, but a search has not provided me relevant results, so I figured I'd just ask. Is it possible, and if so how, to remove the deluge password prompt? Deluge is the only docker that makes me enter a password to access the GUI and i am the only user of this server and plugin, so this password prompt is just an extra step and I'm so beyond tired of having to enter it every time I want to see what's happening. Surely there must be a way to get this to just trust me, like every other docker I use. Thanks for any guidance to resolving this!

I just realized my spare car key has a CR2032 battery, so I replace the motherboard one with it and changed the primary display to the iGPU, checked all my other settings and rebooted. Everything worked fine now. Not sure why the failing battery allowed it to start, but unraid didn't load and the VM did, but new battery seems to have resolved it. I ordered new batteries and will replace again with a brand new one, as I'm not sure how old my spare key battery was thanks again for your guidance!

I don't actually know if the unraid bootup is normally shown on the VM display. Once I got the VM working, I don't remember booting up the server again with that monitor on. I'll buy a new battery and replace it, then go thru the BIOS and confirm all the settings and force the primary display to the iGPU. Once I have that done, I'll boot again and if it's still not working, I'll report back. thanks for the guidance.

Yesterday i noticed my server was turned off, when I turned it on, i saw a message that there was no time set in the BIOS. I booted into the BIOS and set the time, then unraid was able to start, but never actually finished starting up. It was just stuck on the booting screen. The second line, which I can't remember what it says, but the first thing boots immediately, then the second command takes a long time to boot, but never finished. Tonight, I restored my BIOS to my saved settings (assuming everything got jacked up somehow), and tried again. The screen appeared to be stuck at the same place, but on the lower right it went from A1 to B2, then after several minutes, I saw my VM starting. Great I thought. I tried playing a video and it said it couldn't find the file. I tried to get into the GUI and it wouldn't load. i tried to putty into the server and it says it's unable to open connection. host does not exist. i don't know how the server could not be online but the VM is working. I don't know how to get a diagnostics from this condition. Appreciate any help moving forward from here.

Thank you again. Rebooted and everything seems to be working so far. I can't test hot plugging yet, until I rearrange some things, but the keyboard works, so I assume anything plugged into that port should also work. You deserve many great things to happen for you. Have a most excellent new year!

after binding the usb controller and rebooting, I couldn't just add the controller, as it threw an error about the old usb device address. I had to delete that bit at the end, save, then add the controller, and that saved okay. starting the VM after this seems to have worked. here is that new/updated XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 11</name> <uuid>38bc4966-2d3f-8238-e182-bd217aec53b9</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-6.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/38bc4966-2d3f-8238-e182-bd217aec53b9_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <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='4' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VMs/Media Server/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/backup/Programs/WindowsISOs/Win11_English_x64v1.iso' index='2'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <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/backup/Programs/WindowsISOs/virtio-win-0.1.208-1.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='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f9:7c:95'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 11/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <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> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/cache/VMs/vbios/GT1030.dump'/> <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='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <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='0x43' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

wow, thanks again for your help. Here is the working XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 11</name> <uuid>38bc4966-2d3f-8238-e182-bd217aec53b9</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-6.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/38bc4966-2d3f-8238-e182-bd217aec53b9_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <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='4' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VMs/Media Server/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/backup/Programs/WindowsISOs/Win11_English_x64v1.iso' index='2'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <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/backup/Programs/WindowsISOs/virtio-win-0.1.208-1.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='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f9:7c:95'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 11/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <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> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/cache/VMs/vbios/GT1030.dump'/> <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='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='5' device='2'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Actually, I would still love to pass thru the entire USB controller. Do you wanna hold off on reviewing this until i can see if I can make that change quickly and (hopefully) repost that working XML?

I ended up changing my config.sys to default to running without GUI and added you bit in there, like so then I bound the video and sound cards as you suggested then tried to make the XML changes, but got some error about the address not being right (can't remember exactly), so I just cancelled the update and rebooted to see where I got. I saw the unraid bootup on the screen up to where it was running bzroot, then the screen froze, leaving that message visible. I then started the VM and it loaded and I could see everything, but i still had the error 43 message and couldn't change the resolution. i re-installed the nvidia drivers, and that completed, and seemed to work. i rebooted the VM and it loaded fine, and the resolution is good. No errors in Device Manager and several video files played great with sound and no issues. Everything is now working. THANK YOU SO MUCH for your help. Maybe the unraid devs can use this feedback to make this all work a little better for folks out of the box, without having to troubleshoot so much. Have a most excellent weekend!

First off, thank you for helping! To be sure I don't make things worse, I want to clarify a couple things. You suggest My syslinux config says this I believe your suggestion is to change this to read as follows by just adding that bit into the line, but leave everything else. Is that correct, or should I remove all the pcie override stuff also? Next, you suggest replacing a block of the XML with your edit, but I'm not certain I'm picking the block to replace, as when I tried, I got an error upon saving. So I need to look more carefully, or am i really just adding the multifunction='on'/> bit to the section, with everything else the same? If I attach group 16 & 17 as you suggest, will that not prevent me from using this card for unraid to see it boot up, as I can currently? Is it necessary to do this bit? I ask because I've never done that, and it used to work fine. In fact, I've never done any of these steps before, and this all worked fine until a few days ago, when I tried to just pass thru the whole controller instead of the device. I thought I reverted all those changes when I ran into errors, but was never able to get back to what worked prior to trying to 'make it better'. Thanks again, and I'll wait to hear back before I make things worse again, and then will report back after making the changes, hopefully with good news!

unraid version: 6.10.0-rc2 I had this working for a while, but decided to try to passthru the entire usb controller instead of just the keyboard connected to it, and now I can't get any video on the monitor. I've tried so much, I don't even know what to write, so I'll just attach my logs, and what i think the issue might be. From the log when starting the VM, I see this error "2022-01-07T04:47:55.865887Z qemu-system-x86_64: -device vfio-pci,host=0000:01:00.0,id=hostdev0,bus=pci.5,addr=0x0,romfile=/mnt/cache/VMs/vbios/GT1030.dump: Failed to mmap 0000:01:00.0 BAR 3. Performance may be slow" I believe the rom is fine, since it worked for awhile with just the usb device passed thru. But, maybe it's corrupted now, or it just decided to stop working. I'm not sure how to diagnose, other than asking here for help. I can see the VM starting, but I eventually lose video on teh monitor, either in the middle of the tiago loading screen, or often, windows will boot into windows, but then the screen goes black. i am able to log into the VM with remote desktop to verify it's running, but device manager shows an error with the nvidia adapter "Windows has stopped this device because it has reported problems. (Code 43)" Here is my XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Media Server</name> <uuid>8ea1304c-fb66-0a91-e96a-cbf8ca134324</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-6.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/8ea1304c-fb66-0a91-e96a-cbf8ca134324_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <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='4' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VMs/Media Server/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/backup/Programs/WindowsISOs/Win11_English_x64v1.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <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/backup/Programs/WindowsISOs/virtio-win-0.1.208-1.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='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <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'/> <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'/> <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'/> <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'/> <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'/> <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'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:bd:8a:2a'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='none'/> </devices> </domain> media-diagnostics-20220106-2343.zip

Thanks. I didn't see that in my search. Glad to know a fix is in the works. have a great weekend!

Thanks, that helped. I was trying to have this new VM point to my existing windows 10 install, but it doesn't seem to want to just run that, it wants me to install, but it won't let me install over what exists, and no version of 'repair' I could access seemed to work. So, it seems I'll be installing windows from scratch, but at least it let me see something on the monitor, so definite progress. I'll write back if I run into any more roadblocks. Thanks again for your help

I used to have this working, but it's been 'broken' for about a year now. I've decided to try starting over, but can't get anything working. I have created a brand new VM, using the windows 11 template. I have edited my video rom bios per the spaceinvaders video. I added that bios/dump to the VM, but I get a message on the monitor that lists lots of aliases and ends with a line about pressing esc within 1 second, but I can't so it just sits at a Shell> prompt. (see attached) I've tried so many other things along the way, I can't even explain it all. Can someone/anyone, PLEASE help me get this working? I've tried reaching out in Discord also, but have not gotten any help there. I'm happy to continue working on this there, for a real-time conversation if that's helpful. Thanks in advance for any help you can provide!!!!!!!! media-diagnostics-20211217-0939.zip

TL;DR - Windows VM won't start, diagnostics attached. Long ago, I had the USB controller passed thru to the VM, but it constantly quit working, and I'd have no mouse/keyboard control, so I'd have to restart the VM, which usually didn't work for long. Eventually, I quit fighting it, and just passed the dongle to the VM. At one point, to upgrade the version of windows, I didn't have enough space, so I passed thru an external SSD, which all worked fine. However, if I disconnect the SSD, the VM won't start. I updated to the latest version of unraid, and was able to get the VM to start with the SSD passed thru, but now, even with that, I simply cannot get the VM to start at all. I can't find anything in my logs to explain it, so I'm asking for help. In an ideal world, I'll be able to just pass thru the USB controller again, to allow me to plug in the SSD when I want, but not be required to, and the USB dongle will just continue to work, and all will we right with the world. However, just getting the VM to start will be a big step forward. thanks for any help you can provide. media-diagnostics-20210816-1210.zip

I tried adding an nzb to SABnzb tonight, and it won't download. I went to settings, and tested my server settings (which seem to have worked when it last downloaded on Friday), and they fail. I get [Errno 99] Address not available Check for internet or DNS problems I've restarted SAB, tried news-us.newsnetserver.com, news.newsnetserver.com, ssl, not ssl, and nothing seems to connect. I've searched for episodes in Sonarr and it searched fine, so the internet connection seems to be okay. I suspect a newsnetserver issue, but wanted to ask here if anyone has seen this or has any ideas on how to further troubleshoot

I never setup such a connection (that I remember), and do not have any disks physically located in that machine which are not assigned already. I only started receiving warnings about this location yesterday, after updating Unassigned Drives. When I went to the plugin, I could see nothing there, as I no longer have any extra disks in that machine. Given I have no extra disks, and currently have no need for unassigned devices, I removed the plugin, then rebooted, so I can't go check again. Hopefully this removes this error, and if I ever need to use another device, I'm hopeful the UD plugin will guide me through this remote thing at that time. thanks again for your help