MarkRMonaco

+1 for bad RAM. Just attempted to install some additional RAM modules in my system and ran into this issue. - Pulled the RAM, but had to redo my flash drive. Thankfully, I had a copy of the config folder.

Oddly enough, the problem resolved itself through several reboots (of the VM)... I did remove the following code during one of the reboots, but it did not make any difference initially. Therefore, I am inclined to believe that it was purely coincidental. <kvm> <hidden state='on'/> </kvm>

Another update, I went into my motherboard's BIOS, and switched the boot mode from UEFI (only) to UEFI+Legacy. - This allowed the VM to boot up w/ video being output to the monitor. However, error code 43 is still present. What I've done so far is: Re-enable Hyper-V in the VM config. Change the Unraid boot mode to from UEFI to what I am assuming is Legacy (under the "Flash" section). I also removed the video card (and it's HD audio) device ID from the "vfio-pci.ids" section of my Flash config. No improvements. - Video output, but stuck at a 800x600 resolution.

Just an update, I was able to successfully run the driver install after clearing out all of the Hyper-V lines in the VM XML config. However, I am now getting error code 43 in Device Manager. - Still no video output to my monitor though.

I have a Windows 10 Pro v1903 VM running on my Unraid v6.7.2 server. - Passthrough was previously working headless w/ a DisplayPort dongle (remotely accessible via RDP or TeamViewer). However, when I attempted to run it like a traditional workstation (w/ a known working monitor, keyboard and mouse), I lost the ability to pass the GPU-through (resulting in BSOD boot-loops). The system itself is running on a single EVGA GTX 1660 TI board. - No other GPU's are present, and integrated graphics is not an option w/ my CPU. I have previously went through the process of exporting my vBIOS using GPU-Z and modifying it w/ a hex editor. - Passing either the modified version or the original file no longer helps. Running DDU (and disabling auto-driver download) resolves the bootloop issue, but is only accessible via remote methods (mentioned above). - My monitor will remain black/blank. - Cannot successfully reinstall drivers. As for the VM error log, I am seeing the following: 2019-07-27T19:34:57.873893Z qemu-system-x86_64: vfio_region_write(0000:27:00.0:region1+0x1210c8, 0x0,8) failed: Device or resource busy VM XML Config.txt diagnostics-20190727-2004.zip

+1

Good call. - I'm following too many topics, and lost track of which one I was posting this on...

Does anyone have a good guide/process on changing the pihole hostname in docker? The container's console lacks an editor and I'm unable to get one via apt-get. - I also tried copying the files (/etc/hosts and /etc/hostname) back to my pc via Krusader, editing them, and copying back to the container... which resulted in the WebGUI no longer loading (by IP) after the container was restarted. - Applying "chmod 777" to the files didn't help either (as I assumed they were copied back as read-only). Lately, attempting to pass the hostname variable via the container setup gets ignored, and only results in a new random hostname being generated (all of my other settings/data are preserved). - I should note that this seems to be the default behavior when running the container setup (i.e. new random hostname each time, regardless of the variable being passed or not).

Does anyone have a good guide/process on changing the pihole hostname in docker? The container's console lacks an editor and I'm unable to get one via apt-get. - I also tried copying the files (/etc/hosts and /etc/hostname) back to my pc via Krusader, editing them, and copying back to the container... which resulted in the WebGUI no longer loading (by IP) after the container was restarted. - Applying "chmod 777" to the files didn't help either (as I assumed they were copied back as read-only). Lately, attempting to pass the hostname variable via the container setup gets ignored, and only results in a new random hostname being generated (all of my other settings/data are preserved). - I should note that this seems to be the default behavior when running the container setup (i.e. new random hostname each time, regardless of the variable being passed or not).

Thanks @Firejack. I haven't had a chance to take my array offline to switch to IPv4+IPv6 mode. - I'm hoping that "ip a" will return a v6 address once it has been enabled.

I'm not having any problems with my unRAID server using the Pi-Hole as its primary DNS. - The only caveat was that you had to add "raw.githubusercontent.com" to your whitelist.

So, it appears that ifconfig is missing from the docker's console... Any alternatives or workarounds? # ifconfig sh: 2: ifconfig: not found #

I actually, just answered my own question... After reviewing the Pi-Hole dashboard and logs, I found that the images were coming from "raw.githubusercontent.com". - I first attempted to whitelist just the base domain ("githubusercontent.com"), but found that it did not work. Instead, you have to explicitly define/add the sub-domain ("raw.githubusercontent.com"). - Once that was done, I was able to refresh my unRAID apps tab, and immediately see the missing pictures/icons. Hope this helps anyone else who runs into this problem...

Not sure if anyone ran into this issue, but right after installing and configuring Pi-Hole (Docker), icons on the unRAID apps tab are getting blocked. - Does anyone know the correct domain or sub-domain that needs to be added to the whitelist?

Thanks @jonathanm

When you add a 2nd data disk to the system, I assume that the contents of the first drive are not lost (referencing the comment about unraid not being a traditional array). Is that correct? Thanks in advance.