Community Developer
  • Posts

  • Joined

  • Last visited

Everything posted by Capt.Insano

  1. @Martsmac Did you ever get this sorted? I am looking for a USB 3.2 PCI-E card to passthrough to a Windows 10 VM in order to try and use my server for VR. @pinion Did you ever get your card working in unRAID?
  2. Sorry to resurrect old thread but this worked for me. Thanks
  3. Seems you may be right! 😭 Booted the same unraid hardware with a Windows 10 drive and also got Code 43 errors after driver installation. What a balls! GPUs are just so expensive at the moment. Thanks for your advice
  4. Firstly: Happy New Year unRAID community I would HUGELY appreciate any help that could be offered here: I have been reading all the AMD passthrough threads that I could find but I have gotten incredibly confused by conflicting information and information that is possibly no longer valid as per versions 6.9+. I am swapping the GPU on a Win10 VM from a Nvidia 1050Ti to an AMD RX580 (Gigabyte Aorus RX580 8GB). I am having a lot of difficulty in getting the RX580 reliably passed through: I can get it to boot in the VM with a 800x600 resolution and green/blue artifacts on the screen and I am sometimes get the AMD drivers (latest from AMD website) to correctly install but it inevitably crashes and then reboots to show an "Error Code 43" in the device manager for the card. I have tried completely removing all driver components with DDU in safe mode between attempts but still struggling greatly. I recently had it working but then after a reboot of the server it reverted to Code 43 again! Artifacts disappear in safemode so I am fairly confident they are related to drivers/passthrough. Card is known working as was removed from eGPU enclosure. My Setup: M/B: Gigabyte Technology Co., Ltd. C246-WU4-CF Version x.x - s/n: Default string BIOS: American Megatrends Inc. Version F6g. Dated: 09/16/2020 CPU: Intel® Core™ i9-9900 CPU @ 3.10GHz HVM: Enabled IOMMU: Enabled Cache: 512 KiB, 2 MB, 16 MB Memory: 64 GiB DDR4 (max. installable capacity 64 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 eth1: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 5.14.15-Unraid x86_64 I have CSM disabled in BIOS as per some posts I read here. I have the AMD Vendor Reset Plugin from @ich777 installed: My System VM Manager Settings are as follows: I have the following VFIO bindings: VM Log: -boot strict=on \ -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 \ -device pcie-root-port,port=0xd,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x5 \ -device pcie-root-port,port=0xe,chassis=7,id=pci.7,bus=pcie.0,addr=0x1.0x6 \ -device pcie-root-port,port=0xf,chassis=8,id=pci.8,bus=pcie.0,addr=0x1.0x7 \ -device pcie-pci-bridge,id=pci.9,bus=pci.1,addr=0x0 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/disks/CT2000MX500SSD1_2111E589AB92/domains/Windows 10 (BI)/vdisk_new.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-2-storage","backing":null}' \ -device virtio-blk-pci,bus=pci.4,addr=0x0,drive=libvirt-2-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/ata-WDC_WD20PURZ-85AKKY0_WD-WX42D609RS31","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device virtio-blk-pci,bus=pci.5,addr=0x0,drive=libvirt-1-format,id=virtio-disk3,write-cache=on \ -netdev tap,fd=39,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=30:11:d2:80:23:6a,bus=pci.3,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=40,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=3 \ -audiodev id=audio1,driver=none \ -device vfio-pci,host=0000:01:00.0,id=hostdev0,bus=pci.6,multifunction=on,addr=0x0,romfile=/mnt/user/Files/VMs/vbios/RX580.Fast.rom \ -device vfio-pci,host=0000:01:00.1,id=hostdev1,bus=pci.6,addr=0x0.0x1 \ -device usb-host,hostdevice=/dev/bus/usb/001/006,id=hostdev2,bus=usb.0,port=1 \ -device usb-host,hostdevice=/dev/bus/usb/001/003,id=hostdev3,bus=usb.0,port=2 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/2 (label charserial0) 2022-01-01T23:52:10.162457Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism. 2022-01-01T23:52:10.167466Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism. 2022-01-01T23:59:38.988500Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism. 2022-01-01T23:59:38.994580Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism. VM XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10 BI XML_Edits</name> <uuid>33eb8092-98b7-7fb8-c0c4-219f958f4b13</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='5'/> <vcpupin vcpu='1' cpuset='13'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='14'/> <vcpupin vcpu='4' cpuset='7'/> <vcpupin vcpu='5' cpuset='15'/> </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.fd</loader> <nvram>/etc/libvirt/qemu/nvram/33eb8092-98b7-7fb8-c0c4-219f958f4b13_VARS-pure-efi.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='3' threads='2'/> <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='qcow2' cache='writeback'/> <source file='/mnt/disks/CT2000MX500SSD1_2111E589AB92/domains/Windows 10 (BI)/vdisk_new.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-WDC_WD20PURZ-85AKKY0_WD-WX42D609RS31'/> <target dev='hdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <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-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xf'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='9' 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> <interface type='bridge'> <mac address='30:11:d2:80:23:6a'/> <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='3'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <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> <rom file='/mnt/user/Files/VMs/vbios/RX580.Fast.rom'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0' multifunction='on'/> </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='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x413c'/> <product id='0x2003'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x413c'/> <product id='0x3012'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain> NOTE: I have tried it both with and without vbios files as I have read conflicting reports of their importance for AMD cards. I have ran a vbios file that I dumped myself via @SpaceInvaderOne script and have ran ones downloaded from There has been no difference in success either way. I have nothing special in my syslinux.cfg: kernel /bzimage append isolcpus=5-7,13-15 pcie_acs_override=downstream initrd=/bzroot Diagnostics attached also: Thanks so much for any advice!
  5. Update to this issue incase anyone else faces a similar issue: Took me longer than it should have to figure this out. The recording issue was based on EIT (programme runtime) setting in recorder: This should be set to DISABLED in my case, there is some issue in getting this EPG data. Disabling "Use EPG running state" fixes it in my case. Thanks to all devs
  6. Thanks so much. I did not know what the "Aperture" setting was for but it also gave me more mode options: Seems to be stable so far, will report if issues.
  7. I have 5 cameras in my set up but 4 of them are fairly low res so seem to be consuming very little effort from the iGPU. I dont know of any BlueIris setting to limit usage, however usage is never over 15-20% Current Task Manager status of VM: GPU 1 = Intel iGPU GPU0 = Nvidia Card Current Bios Settings: Was prev on MAX but changed to 256M instead of MAX to see if stability improves. Left this on 1024M I also just changed the "Aperture Size" for the first time, I am not sure if it is relevant. I was default on 256M but I increased it to 1024M (I tried 2048M but it caused issues booting unRAID)
  8. I am still having reliability issues with my Win 10 VM and Intel-GVT, I am now receiving a different error to previous errors: (Previous error was "Tower kernel: gvt: guest page write error, gpa XXXXXXXX"). As pre previous post: My details: Found VGA Adapter: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] (rev 02) using mode V5_4 with Win10 VM I have GuC/HuC Firmware loading: set to default Win 10 VM is also assigned a Nvidia GPU (1050 Ti) There is no other VM assigned a vGPU I have set RDP max resolution to 1920x1080 via Group Policy Editor on the VM I have increased the BIOS values to the max for the following options: dvmt pre-allocated dvmt total gfx mem My VM will work happily away with BlueIris doing some Intel based transcoding with approx 15-20% GPU usage reported via Task Manager but it crashes at random and then makes the VM system inaccessible on unRAID. Diags attached. Syslog reports the below at time of VM crash: Nov 6 15:00:1Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: shadow page 0000000000000000 guest entry 0xffffffffffffffff type 9 Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: spt 00000000a1a28f04 guest entry 0xffffffffffffffff type 9 Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: shadow page 00000000a1a28f04 guest entry 0xffffffffffffffff type 9. Nov 6 15:00:18 Tower kernel: gvt: guest page write error, gpa 2c6daa000 Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: shadow page 0000000000000000 guest entry 0xffffffffffffffff type 9 Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: spt 00000000a1a28f04 guest entry 0xffffffffffffffff type 9 Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: shadow page 00000000a1a28f04 guest entry 0xffffffffffffffff type 9. Nov 6 15:00:18 Tower kernel: gvt: guest page write error, gpa 2c6daa008 Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: shadow page 0000000000000000 guest entry 0xffffffffffffffff type 9 Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: spt 00000000a1a28f04 guest entry 0xffffffffffffffff type 9 Nov 6 15:00:18 Tower kernel: gvt: vgpu 1: fail: shadow page 00000000a1a28f04 guest entry 0xffffffffffffffff type 9. Nov 6 15:00:18 Tower kernel: gvt: guest page write error, gpa 2c6daa010 Diags attached As always thanks so much for your work and any help that can be given.
  9. Issue, marked as solved. Defo a VM issues not an unRAID issue. Thanks to all and thanks to devs
  10. Sorry for the delay in replying, I could not take the time restart the server and change BIOS settings during the week. I have updated the bios values to their max values and the VM is seemingly stable so far! Thanks for your help, I will report back if I encounter the issue again.
  11. Thanks so much for the reply Few bits of info: 0. Also happening at mode: i915-GVTg_V5_4 for me 1. My RDP connections are from a 1920x1080 laptop so RDP connections were at that max resolution. 2. RDP was also never active when the crashes happened, I noticed the crashes when my BlueIris cameras were gone. 3. Crashes still happen when BlueIris is not using the assigned Intel v-GPU for hardware acceleration or any tasks, I moved all hardware acceleration back to my Nvidia Card as a test of stability and still a crash happened from just having the v-GPU assigned to the VM ? 4. My Mainboard (Gigabyte C246-WU4) allows the 2 following options in BIOS: dvmt pre-allocated 64M dvmt total gfx mem 256M They are both at default values above, would changing this improve my situation? @alturismo What GuC/HuC options are you running with your UHD630? Really appreciate the help with this and @ich777's work on this plugin.
  12. I have read through the thread and seen others with the issue but am not sure of the proper advice for this error: Windows 10VM stalls and results in having to reboot my unRAID server. syslog shows loads of : "Tower kernel: gvt: guest page write error, gpa XXXXXXXX" errors My details: Found VGA Adapter: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] (rev 02) tested passing thru as both mode V5_4 & V5_8 Tried with GuC/HuC both as default and option:0 (disabled), same issue: Windows 10 VM (latest drivers and windows updates, all power saving disabled (screen off : never, sleep: never)) Diags attached: Any advice much appreciated
  13. Thanks for this advice, I will defo do this. @JorgeB & @Squid I think I have found the issue that is causing the excessive shutdown times at the moment (and possibly the unclean shutdowns): libvirt is not hibernating my linux VMs. My Windows 10 VM will hibernate no problem either during array stop, unraid shutdown or by manually triggering a hibernation here: But if I try the same with either my PiHole VM (ubuntu based) or HomeAssistant OS VM(Hassio) nothing happens: This screenshot was after clicking the "Hibernate" button, nothing happens and the VM does not hibernate (same with HassOS VM) I think they are just sitting there (ignoring the hibernation command) causing the libvirt timeout to be reached and then being force-closed. Should linux VMs be able to hibernate from libvirt?
  14. Just stopped the array from the Main Tab, it completed successfully but took 4mins 14secs! Attached is the diag from this. not sure what is causing such a delay?
  15. No, input shows a correct kp/s for the stream (usually about 3k). If I manually trigger/schedule the recording the input and output kb/ps are the same and the recorded file is being created. I have not seen anything in the TVheadend logs, it is as if TVHeadend thinks it is recording correctly but then after the recording realises that the file is missing. But I must check the logs again.
  16. I updated VM shutdown time-out to 180 secs and still a parity check after reboot. I have 3 VMs as you can probably see from prev logs: HomeAssistant VM (Hassio) PiHole (Debian Based) Windows 10 (With latest virtio-win-0.1.208 drivers installed) New diags (from USB key) attached.
  17. I am running this docker with the deafult (latest) tag. Current version: HTS Tvheadend version 4.3-1979~g8fc2dfa7e I am not sure if that is currently recommended or not? When recording via autorecs the recordings fail with a file missing error, the scheduled recording "starts" there is no file outputted: During a "recording": Status > Subscriptions lists the output as 0kb/s and there is no file created in the unRAID filesystem It is not a permission issue (either filesystem or user permissions) as: If I stop the autorecording and start it manually via either WebUI or Kodi the recording works correctly. The Priority and DVR Configurations for the autorecs are the same as manually triggered recordings but only manully triggered or schedued recordings work. I have tried searching this bug in regular tvheadend forums but got nowhere. Anyone here having the same issue?.
  18. I did, infact they were already installed but I also updated them and all drivers to latest stable: virtio-win-0.1.208
  19. I followed your recommendation of changing my VMs to hibernate instead of shutdown, any other recommendations seeing as libvirt is the culprit?
  20. Anyway of figuring what was using Cache? If I monitor top/htop during a shutdown would that tell me?
  21. @JorgeB Sorry, I didn't realise there were other logs: Attached are the 2 zips dated today from /boot/logs Are these the diags that you were after? Thanks for the help BTW
  22. Hi @JorgeB, Diags were attached to the post above yours, these were the diags from the latest unclean shutdown (this morning) that caused the parity check again. I will try and stop the array manually again and time it when I get home but as per one of my prev posts above; the last time it took 1 min 9 secs to stop and the disk timeout in my settings is now 180 secs
  23. Spoke too soon, Just tried another clean reboot there and again a parity check started after power up: Diags attached again. Any further advice?
  24. This seems to have fixed it. Increasing the timeout to a high vaue (180 secs in my case) has ensured enough time for safe shutdown even in the event of a Windows update during VM shutdown. Thanks @Frank1940. Update: See below, problem returned after array runnning for any length of time.
  25. I timed how long it took to stop the array from the Main tab: 1 minute & 9 Seconds. Could it be that 90 secs is not long enough in my setup for all my VMs (x3) and Docker Containers (x30+) to shutdown fully if something like a windows update kicks in? I am going to up the timeout to 180 secs and see if a parity check starts on reboot.