trig229

Do you need to take a note and use the same UUID as well so that windows remains activated? I vaguely remember having an issue a while back and that was the answer?

Ah yes, sorry i get you now. Yep, one cable for each device(onbard/GPU card), then just swap your monitor input to whichever one you want

Its one or the other, you cant use the nvidia card to use in gui and a VM at the same time

Hi all, just wanted to provide an update. After trying all the things on various sites my 6800 xt still did not want to display after a reboot. However! Installed the latest AMD driver 21.6.1 today and viola, it's now working sweet. Reboots. Shutdowns the lot, no problems at all So looks like in the end there was a driver issue, can't see what exactly in the release notes that fixed it, but finally all is good! A thanks to @lnxd in helping out and throwing some ideas about

Hi @lnxd, thanks for checking, it at least confirms in not doing anything obvious and it should "just work". FYI no CPU maxing out, just for the first few seconds during bios start and then it all levels out. I have previously done the vendor ID, but i will re-do again as well as the other options as that was when i first started troubleshooting so i may have missed something out, i will let you know how i get on. The disablement of the SR-IOV in the BIOS was a line of thought i had been down in before, but made no difference @giganode Unfortunately yes, using the tech power up (or completely removing the vbios) had no change on the issue. First VM start no issues, all subsequent reboots/starts gives me a code43 until host restart.

Hi @lnxd, sorry my bad! I hadn't initiated the issue when i took that diagnostic dump so it wouldn't shown anything! Procedure; Shutdown VM Update XML to point to rom from techpower up as mentioned by @giganode and started VM - Booted but no output (code 43) as usual VM shutdown Updated XML to Removed the ROM entirely and started VM - Booted but no output (code 43) as usual Took dmesg, see attached Took Diagnostics (see attached) Rebooted unraid - VM boots fine with display Also attached the XML too Not even tried passing through WIFI yet, that's for another time core2-diagnostics-20210409-1532.zip dmesg.txt win10vm.xml

Hi, @giganode good shout, maybe mine didn't pull correctly, i see that mine is listed in so will test that later today or tomorrow. Do i need to edit the vbios in a hex editior like you do for Nvidia GPUs as per SIO video? @lnxd please see attached diagnostics core2-diagnostics-20210409-1224.zip

@lnxd Thanks for your reply, tried this earlier but getting no results from amdgpu expression before or after the vm shutdown/start up. To confirm, im running this in the unraid terminal?

Hey, so ive been having an issue getting the 6800xt to work after a VM reboot I can get my VM to boot up fine with the 6800 xt after initial unraid boot, However if i reboot or shutdown the VM i cannot get output from the GPU when it starts up again, when i VNC into the VM i see the dreaded code 43 issue. If i reboot unraid i can start up the VM no issues at all (until i reboot it). Ive tried all sorts of configs to no avail. Updated to latest bios, Unraid 6.9.1, latest GPU drivers etc Asus strix x570-e 5800x Sapphire 6800xt Nvidia p400 (Docker Passthrough) added video=efifb:off Stubbed the Card and Audio portion (no usb) VM Q35 5.0 (tried various types) Rom dumped and added to template (via spaceinvaders plugin) Updated the Multifunction and addresses in the XML Attached is the log of the VM Really dont understand why it works perfectly well on first startup but breaks after a reboot or restart. Ive tried stopping and starting the array but no cigars until unraid is rebooted! I dont see any other users having this issue so not sure if its something im doing wrong or maybe the hardware/qemu support isnt quite there yet? logs2.txt

Here you go. I have set mine to custom network as originally the template listed the server port field as "port" type and so conflicted with the tdarr server port. I think the template is updated now though as i can see a new field for server port as a "variable" instead of "port" type.

Hi, resolved the issue. Looks like the container paths are not set correctly as the default options Hope this helps anyone with the same issue. @HaveAGitGat im not sure how to go about updating default options in docker/CA? It is also the same for the Tdarr_Node as well When adding the docker, the default values for the config, logs. and appdata are all set to the actual host path and not the container path, see below example. It should be set to whats in the description Updated the paths to the following and all working

Hey, Just installed the new V2 version, used v1 many months back Installed everything ok, the one issue i have is the config is lost whenever i add a new variable to the docker container and start it up. If i perform a stop -> start or restart the config is fine. Its only when i add a new variable like NVIDIA settings that the config gets wiped out. I haven't tested this on an unraid reboot. I beleive its becuase its not saving the config in the appdata folder for some reason. The appdata\tdarr folder has the config and log file folders but no files contained in them Any ideas what im doing wrong?

Someone made a post just above mine saying that they couldn't start the docker due to a static IP not being in the subnet. Looks like they have now deleted it without a thanks or anything lol! On a side note, thanks for this, up and running in a matter of minutes

Setting -> Docker -> Advanced -> IPv4 custom network on interface br0: Check this is correct