neon_phoenix

Hey all, Im trying to pass through a GTX 1050ti to a Win 10 VM. I will post my XML below. I have grabbed a VBIOS from TechPowerup, and edited it to remove the header as SpaceInvaderOne had mentioned in his video. I have disabled HyperV, made sure my GPU and its HDMI audio are in the same IOMMU group, and still I just keep getting code 43, if the passthrough works at all. I am not always able to connect to the VM after switching back and forth between GPU and VNC to troubleshoot. When i switch to the GPU for the VM, i often cant connect at all with NoMachine, and if i can, I dont always see a GPU or sound card in Device Manager. Just the 'Nomachine' emulated display and audio, as i am using that for remote access. Pulling out my hair on this. Unraid VM XML

Hey all, rather than start my own thread about the exact same card, i am necrobumping this thread in the hopes it will help me as well as others have a running dialog about passing through the 1050ti. I will post my own XML below, but first a few points: 1. I have tried the above fix that @rachid596 posted, as I am getting Code 43 in Windows 10 VM. 2. I have grabbed a VBIOS from TechPowerup, and edited it to remove the header as SpaceInvaderOne had mentioned in his video. You may notice in the XML that at this point, after trying all other well known fixes, and using @rachid596 fix from above, i noticed that for some reason HyperV was enabled, even though i make a point of disabling it. I have now tried to disable it multiple times, and interestingly it will not disable. I am able to connect to the VM, but now rather than having Code 43 in Device Manager as i was before, i am not seeing a GPU or sound card. Just the 'Nomachine' emulated display and audio, as i am using that for remote access. I can definitely try recreating (for the 100th time lol) if needed. Unraid VM XML

Hi guys, lol this is funny, but im having the same issue almost 2 years to the DAY from before, when i posted in this thread. The old "waiting for deluge to start on port xxxxx". WebUi doesnt work. What I have done probably to cause this, is replace my cache drive, following SpaceInvader's video guide. All my other dockers work but this one. I have tried multiple branches, going back as far as 1.3 from almost 5 years ago. Multiple restarts of the container, still no WebUI. I thought it would be the most recent pulldown that caused it, but at this point im lost. As well, while writing this comment, the error in the log has disappeared and looks normal. Ill paste below. Still no WebUI. 2021-11-13 19:05:23.674424 [info] Starting Supervisor... 2021-11-13 19:05:23,965 CRIT Set uid to user 0 2021-11-13 19:05:23,965 INFO Included extra file "/etc/supervisor/conf.d/deluge.conf" during parsing 2021-11-13 19:05:23,972 INFO supervisord started with pid 7 2021-11-13 19:05:24,974 INFO spawned: 'deluge-script' with pid 40 2021-11-13 19:05:24,975 INFO spawned: 'deluge-web-script' with pid 41 2021-11-13 19:05:24,980 DEBG 'deluge-script' stdout output: [info] Deluge config file already exists, skipping copy [info] Starting Deluge daemon... 2021-11-13 19:05:24,980 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-11-13 19:05:24,980 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

Sorry for the delayed response. I believe i removed both? Unraid gives you the option at removal, no? I still have other active Docker containers running.

Sorry for the delayed response. I believe i removed both? Unraid gives you the option at removal, no? I still have other active Docker containers running.

Ok then great, now, if i have removed deluge already, and forgive my noobishness, can i just do a docker pull for this tag and off i go?

Thanks for the reply, binhex! Having said that: "This repository doesn't have any tags that have "2.0.3-1-08" in their names." What about maybe 2.0.3-2-01?? Closest to what you recommended.

Hi guys, i have just had a wierd issue with deluge. i suddenly cant access the webui, i have checked settings in the docker container and even removed and reinstalled the app/container completely. i saw this in the log: [info] Waiting for Deluge process to start listening on port 58846... and noticed that in my previous attempts earlier after noticing the issue, it had stuck on this as well. The thing is, now i cant get the webui or the log viewer to display! Could use some assistance