Caddy

Did you ever get your appdata to run on your cache again ?

Ow... OW... Yeah i think i remember installing windows 10. Not 11. Well, all i need is run a android game. 24/7. VM Windows on my unraid was the perfect option. Untill now where it does not work optimally. Now if i cant do that on a windows VM, whats my options? My daily powerhungry driver cant be on 24/7. Did a reinstall of windows 10. Works like a charm again. Thanks a lot!

A quick note to self, and maybe google bots: Clone the VM. Make new VM. Point it to the clone. Just in case. /mnt/cache/domains/Windows_clone/vdisk1.img

Hi. Am i reading this thread right, that SR-IOV is currently broken? I came home to my windows VM crashed. When booting up again, my Intel Alder Lake-S GT1 UHD 730 iGPU has errorcode 43. Been fiddeling a few days now with no luck fixing it. Any help apriciated. Edit: Cause of this? xe 0000:00:02.2: Your graphics device 4692 is not officially supported by xe driver in this kernel version. To force Xe probe, use xe.force_probe='4692' and i915.force_probe='!4692' module parameters or CONFIG_DRM_XE_FORCE_PROBE='4692' and CONFIG_DRM_I915_FORCE_PROBE='!4692' configuration options. Edit2: Under Drivers: i915 (2025.07.22-sriov.6.12.39) Linux i915 driver with SR-IOV support, port from github.com/intel/mainline-tracking.git v6.12 branch Disabled gpu/drm/i915 Blacklist i915 Is this causing it ? Asking AI, and doing what AI said, the xe message is now gone. Opening the files edited, and the edits are gone after a reboot. Windows still on code 43. AI: 3. Permanent Use (via Modprobe) If you prefer configuring module options directly: Create a configuration file: sudo nano /etc/modprobe.d/xe.conf. Add: options xe force_probe=4692. Create another file: sudo nano /etc/modprobe.d/i915.conf. Add: options i915 force_probe=!4692. Update your initramfs: sudo update-initramfs -u. <---- unknown command. Going with the critical QEMU overrides from this https://forums.unraid.net/bug-reports/stable-releases/712-vm-intel-gpu-passthrough-to-monitor-stopped-working-r3855/ thread, results in: internal error: QEMU unexpectedly closed the monitor (vm='Windows'): 2026-01-19T18:01:21.915479Z qemu-system-x86_64: -device {"driver":"vfio-pci","host":"0000:00:02.2","id":"hostdev0","bus":"pci.6","addr":"0x10","romfile":"/mnt/cache/isos/VGA ROM/i915ovmf.rom","x-igd-opregion":true,"x-igd-gms":2}: vfio 0000:00:02.2: does not support requested IGD OpRegion feature: No such device FML. Probably cause machinetype is not Q35 ... testing.. Nope. Not it. Next.... A reinstall of Windows 10 seems to be the thing. Currently installing all Intel drivers with no problem. Windows 11 is the problem here, not the plugin. Thanks franko101 in this thread for sheding some light. https://forums.unraid.net/topic/194888-w11-vm-igpu-intel-uhd-630-passthrough-issue/

I too have a similar problem. Still have. I think my VM crashed, and then the GPU was no longer passed through. Error 43. Did use SR-IOV plugin. Now passing through the whole integrated GPU. (UHD 730) Still error 43. Google mentions Proxmox and troubble whereabouts. IDK where to go next.

Specify the tag where ?

This app worked. Just had to move the recovery to the end of the disk first, then merge the free space to disk c.

Is this template still updated? Docker list says "Version not available", but i know there are updates to AirDC++ ..

Is this still beeing updated/maintained? Docker list say that version is not available, and have been this way for a while now. Sorry, please move this post to docker containers..

Any way to get more of theese messages when updating stuff? I see way to many updates not giving them.