byb

Zeze21, I also understand the frustration. I have a hunch about this bug in that it is related to the VM template. In my Unraid box I have 3x Nvidia GT1030 GPUs. My problem: I cannot run 3x VMs using the Debian or Linux templates concurrently. I can only run two instances of Debian, then the third one has a blank screen. I've even tried passing through the vbios, but it had no impact. I have to pause and force quit that VM. However, if I set the third VM to Windows 10, it launches fine. In other words, I am able to run Debian+Debian+Windows10, but I cannot run Debian+Debian+Debian. To prove this, I set out to simply get to the UEFI BIOS screen. I set up a basic Windows 10 template with these options: i440fx-7.1 OVMF 10 MB Vdisk Default VirtIO (doesn't matter, we're just trying to get to QEMU/UEFI) GPU passed through USB Controller passed through I was then able to get to get video output from the UEFI bios with this template. However, when I try the same thing with a Debian template, I get a blank screen. Zeze21, I realize that your time is valuable, but why not try the same thing (or experiment yourself with various minimal VM templates) to see if you can get to UEFI using Windows 10 templates? If you can confirm my hunch, then it might help the developers fix this bug faster.

False alarm. Thank you for prompting me to do this. I reconfigured the machine to its problematic configuration and began collecting diagnostics, however I tried using btrfs on the cache drive. I ended up encountering the same issue of the pool drive disappearing. I think this confirms my suspicion that this is a hardware-related issue.

Hello, I'm getting a ZFS pool suspended error. I recently upgraded to 6.12.3 and followed the onscreen advice to convert my cache drive (an NVMe drive) from XFS to a ZFS pool. I had heard the praises of zfs and felt why not try it. However, now I'm not sure if this drive is bad, going bad, or if there is a problem with Unraid. This particular drive is about four years old. I repurposed it from a laptop I purchased in 2019. About eighteen months ago, I put it in my Unraid server to serve as the cache drive. Looking through my past notifications, the drive temperature rarely exceeded 48 C, and only went over 50 C on one occasion. I did not, and still do not, have a heat sink on this drive. In the past, this drive was installed to an m.2 slot where it was located between the first and second PCIe slots on my motherboard. I had a GTX960 installed above it. Perhaps the fans on that device moved enough airflow to keep it cool. After upgrading to 6.12.3, I changed my configuration around. I added more dedicated hardware for GPU and USB pass through to support more VMs. I relocated this drive from its m.2 slot to the first 16x PCIe slot with a 8x4x4 PCIe adapter board with two m.2 slots. In the 8x slot I put a GT1030 (above it). In the other slot (on the other side), I put a Renesas USB controller. This put the nvme drive in a vertical orientation. It now faced the CPU/memory slots on my motherboard. Also, I ran some additional cables to some USB 2.0 ports in the PCI slot. I actually thought this would reduce temperatures. After the ZFS and position change, Unraid began sending notifications that the drive was hitting 51-54 C regularly. It never went above 54C. These temperatures should be well within the specification limits Tested: Does Your M.2 NVMe SSD Need a Heatsink? Then, after getting these errors my VMs would become unresponsive, the VM page in the webGUI also became unresponsive (the loading bar never finished), and CPU usage skyrocketed. On the webGUI's Drives page, I believe the pool drive started showing up as missing and/or showed a size of 0 GB (should be 512 GB). I don't think I have a screenshot. I could still ssh in from a client - not the webGUI, but trying to shutdown the system didn't work. I had to manually hold down the power button for six seconds. I was able to collect one message from the drive page that the ZFS pool was suspended: pool: pool_one state: SUSPENDED status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool clear'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-HC config: NAME STATE READ WRITE CKSUM pool_one ONLINE 0 0 0 /dev/nvme0n1p1 ONLINE 2 24.9M 0 errors: 11 data errors, use '-v' for a list I could not recover or run this command after reboot. Wild Guesses on the Root Cause The reduced airflow and higher temperatures caused a the problem. Maybe the temperatures are causing the PCB to flex and weaken the connection or the NVME drive is more temperamental at higher temperatures. The 8x4x4 PCIe adapter could be poorly made and could be introducing signal integrity issues or other interference. My motherboard could have bifurcation issues. I haven't run the first PCIe slot (1) in 4x4x4x4 mode frequently in the past, but the other 16x slot (3) happily ran in 4x4x4x4 mode. The last thing is why I'm posting: Something is going wrong with Unraid's zfs pool implementation. I'm not sure how I should proceed. I don't want to re-add this drive if the same behavior will occur. I relocated the drive to the original m.2 slot and began manually backing up the /domains and /"appdata backup" folder created by the appdata backup plug-in in case this is a sign the drive is dying. Ironically, it reached 60 C when I was copying data off of it at 200 MB/s to a USB drive. I'm not sure what follow-up help I can offer. I'm not sure how many logs are left or where to find them. I was already running all 2.5" SSDs on the array off of a SAS HBA to a SAS expander in another chassis, and just treating this as a JBOD without parity drives... so the 'cache' or 'pool' usage is not that critical. Here's an output of the smartctl... I don't see any issues. smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.38-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: KINGSTON RBUSNS8154P3512GJ1 Serial Number: <Redacted> Firmware Version: E8FK12.3 PCI Vendor/Subsystem ID: 0x2646 IEEE OUI Identifier: 0x0026b7 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 0 NVMe Version: 1.2 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 0026b7 6830511ae5 Local Time is: Thu Aug 10 21:32:54 2023 PDT Firmware Updates (0x12): 1 Slot, no Reset required Optional Admin Commands (0x0007): Security Format Frmw_DL Optional NVM Commands (0x001e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Log Page Attributes (0x04): Ext_Get_Lg Maximum Data Transfer Size: 512 Pages Warning Comp. Temp. Threshold: 84 Celsius Critical Comp. Temp. Threshold: 88 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 7.90W 0.0790W - 0 0 0 0 600 600 1 + 7.90W 0.0790W - 0 0 0 0 600 600 2 + 7.90W 0.0790W - 0 0 0 0 600 600 3 - 0.1000W 0.0790W - 3 3 3 3 1000 1000 4 - 0.0050W 0.0790W - 4 4 4 4 400000 90000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 1 1 - 4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 48 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 7% Data Units Read: 31,228,641 [15.9 TB] Data Units Written: 59,681,139 [30.5 TB] Host Read Commands: 488,266,303 Host Write Commands: 842,469,025 Controller Busy Time: 3,185 Power Cycles: 889 Power On Hours: 19,886 Unsafe Shutdowns: 36 Media and Data Integrity Errors: 0 Error Information Log Entries: 2,409 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 2: 48 Celsius Error Information (NVMe Log 0x01, 16 of 16 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 2409 0 0x001c 0x0005 - 6 0 - 1 2408 0 0x0015 0x0005 - 12 0 - 2 2407 0 0x5010 0x0005 - 6 0 - 3 2406 0 0x0011 0x0005 - 12 0 - 4 2405 0 0x0010 0x0005 - 6 0 - 5 2404 0 0x0009 0x0005 - 12 0 - 6 2403 0 0x000a 0x0005 - 6 0 - 7 2402 0 0x0001 0x0005 - 12 0 - 8 2401 0 0x5010 0x0005 - 6 0 - 9 2400 0 0x0011 0x0005 - 12 0 - 10 2399 0 0x5014 0x0005 - 6 0 - 11 2398 0 0x0015 0x0005 - 12 0 - 12 2397 0 0x0000 0x0005 - 6 0 - 13 2396 0 0x0005 0x0005 - 12 0 - 14 2395 0 0x0001 0x0005 - 6 0 - 15 2394 0 0x0004 0x0005 - 12 0 -

Hi, it seems my users and repositories are gone. I tried logging in both as root and my users and got an "Invalid login or password" error. I had to use GitLab docker's console to run gitlab-rake "gitlab:password:reset[root]" to reset the root password. My other accounts did not exist. I did two things recently, I'm not sure which one caused the problem: I used the "Update all" button from the docker management screen. I used the mover to move data from my cache drive to my array. I checked both /mnt/user/appdata and /mnt/cache/appdata for the data and there are no traces of the repositories, usernames, or data. I did not have a local copy of the data because I was using the webIDE. *edit* changing from */mnt/cache/appdata/gitlab-ce/* to */mnt/user/appdata/gitlab-ce/* for /data, /config, and /log fixed it! *edit 2* Nope, I could see the projects, but ended up getting Internal 500 errors when I tried to access the repos. Seems I won't get this data back.

I just wanted to say thank you for posting this. The current version 2022.11.30a was not detecting one of my GPUs. Both are passed through to VMs, when both VMs were stopped, only one GPU appeared in GPU Statistics, there was a ' -: ' for the other. Reverting to this version, 2022.02.22, stopping my VMs, and running SpaceinvaderOne's scripts produced this output: ''' I can see these Nvidia gpus in your server GPU 0: NVIDIA ... GPU 1: NVIDIA ... ------- Persistence mode is already Enabled for GPU 00000000.02:00.0. Enabled persistence mode for GPU 00000000.65:00.0. All done. Power state is P8 P0 -------- Power draw is now power.draw [W] [N/A] 104.92 W ''' Immediately afterwards, I checked the dashboard, GPU1 showed 9-10 watts of usage. I also have a 1200 watt UPS which I have configured for Unraid. Usually, I see about 14-18% (168-192 watts) usage with all VMs stopped. After running the script, it shows about 10-14% (120-168 watts). I added another one of SpaceinvaderOne's script to run every 5 minutes "*/5 * * * *". While I cannot be 100% sure that both my GPUs were reaching an S8 sleep state before I ran SpaceinvaderOne's script, I'm glad to have the peace of mind from using this plug-in to confirm I'm doing what I can to reduce power usage. Thank you everyone.

I saw this question posted twice on this page and thought I'd assist. I too had to figure this out... I first tried registering an account, but it was not obvious that it didn't work. Unfortunately there aren't any hints/tutorial when installing/configuring the docker. I've seen some other apps do this which is very helpful. First, you should confirm where your Unraid system stores its docker configurations. To do this, navigate to Unraid's Docker WebGUI page and left click on the GitLab-CE application. Select the "edit" option from the pop-up menu. Scroll down to the "show more settings" and click it. This will show you where the "Config Storage Path" is. Next, open a terminal from the webGUI (or SSH in or whatever your preferred way is). cd /mnt/cache/appdata/gitlab-ce/config cat initial_root_password # WARNING: This value is valid only in the following conditions # 1. If provided manually (either via `GITLAB_ROOT_PASSWORD` environment variable or via `gitlab_rails['initial_root_password']` setting in `gitlab.rb`, it was provided before database was seeded for the first time (usually, the first reconfigure run). # 2. Password hasn't been changed manually, either via UI or via command line. # # If the password shown here doesn't work, you must reset the admin password following https://docs.gitlab.com/ee/security/reset_user_password.html#reset-your-root-password. Password: <YOUR PASSWORD WILL BE HERE> Select the password, copy it (if the WebGUI didn't already). Open the GitLab-CE WebGUI. Use the account "root" with the password provided to log in. Have fun from here!

Bad news, I'm still getting this error: internal error: process exited while connecting to monitor: qemu-system-x86_64: -object -sandbox: Parameter 'qom-type' does not accept value '-sandbox' I also tried adding, but it had no effect. clear_emulator_capabilities = 0 At least the good news is that the subsequent errors 1 and 2 no longer occur - my passed through USB passthrough on my other VMs is working. Here is the qemu output from the diagnostic: 2022-09-25 04:20:07.370+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.46-Unraid, hostname: Tower LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-6-evdev VNC' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-6-evdev VNC/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-6-evdev VNC/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-6-evdev VNC/.config' \ /usr/local/sbin/qemu \ -name 'guest=evdev VNC,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-6-evdev VNC/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/7bafda78-eb87-7a41-da13-e4c92791ccd1_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-6.2,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m 16384 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":17179869184}' \ -overcommit mem-lock=off \ -smp 14,sockets=1,dies=1,cores=7,threads=2 \ -uuid 7bafda78-eb87-7a41-da13-e4c92791ccd1 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=40,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=16,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=17,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=18,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=19,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=20,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -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/user/domains/evdev VNC/vdisk1.img","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.3,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \ -netdev tap,fd=41,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:1d:f9:b4,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=39,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=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -device qxl-vga,id=video0,max_outputs=1,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pcie.0,addr=0x1 \ -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/2 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2022-09-25T04:20:58.305462Z qemu-system-x86_64: terminating on signal 15 from pid 8155 (/usr/sbin/libvirtd) 2022-09-25 04:20:58.505+0000: shutting down, reason=destroyed 2022-09-25 04:21:18.552+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.46-Unraid, hostname: Tower LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-7-evdev VNC' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-7-evdev VNC/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-7-evdev VNC/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-7-evdev VNC/.config' \ /usr/local/sbin/qemu \ -name 'guest=evdev VNC,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-7-evdev VNC/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/7bafda78-eb87-7a41-da13-e4c92791ccd1_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-6.2,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m 16384 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":17179869184}' \ -overcommit mem-lock=off \ -smp 14,sockets=1,dies=1,cores=7,threads=2 \ -uuid 7bafda78-eb87-7a41-da13-e4c92791ccd1 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=40,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=16,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=17,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=18,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=19,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=20,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -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/user/domains/evdev VNC/vdisk1.img","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.3,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \ -netdev tap,fd=41,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:1d:f9:b4,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=39,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=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -device qxl-vga,id=video0,max_outputs=1,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pcie.0,addr=0x1 \ -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 \ -object input-linux,id=kbd,evdev=/dev/input/by-id/usb-LITE-ON_Technology_USB_NetVista_Full_Width_Keyboard.-event-kbd,grab_all=on,repeat=on \ -object \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on qemu-system-x86_64: -object -sandbox: Parameter 'qom-type' does not accept value '-sandbox' 2022-09-25 04:21:18.636+0000: shutting down, reason=failed And here is the XML: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>evdev VNC</name> <uuid>7bafda78-eb87-7a41-da13-e4c92791ccd1</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>14</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='21'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='23'/> <vcpupin vcpu='4' cpuset='7'/> <vcpupin vcpu='5' cpuset='25'/> <vcpupin vcpu='6' cpuset='9'/> <vcpupin vcpu='7' cpuset='27'/> <vcpupin vcpu='8' cpuset='11'/> <vcpupin vcpu='9' cpuset='29'/> <vcpupin vcpu='10' cpuset='13'/> <vcpupin vcpu='11' cpuset='31'/> <vcpupin vcpu='12' cpuset='15'/> <vcpupin vcpu='13' cpuset='33'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/7bafda78-eb87-7a41-da13-e4c92791ccd1_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='7' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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='raw' cache='writeback'/> <source file='/mnt/user/domains/evdev VNC/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' 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='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' 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='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='redacted'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' 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='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-object'/> <qemu:arg value='input-linux,id=kbd,evdev=/dev/input/by-id/usb-LITE-ON_Technology_USB_NetVista_Full_Width_Keyboard.-event-kbd,grab_all=on,repeat=on'/> <qemu:arg value='-object'/> </qemu:commandline> </domain>

Hello. I apologize if this is the wrong place to ask for support. I have been unable to get evdev working. I've made multiple attempts across several months. I've recently upgraded to version 6.10.3, but the result is the same. Here is a concise report. I am trying to set up evdev to be used with a VNC-based VM. I am configuring Unraid from a VM which has multiple passed-through USB PCIe host controllers to different VMs, each with a passed through nvme drive and GPU. I have my "primary" USB Ducky keyboard and mouse connected to a four port ATEN switch. Unraid doesn't see these devices. I want to use evdev to eliminate this complexity and free up PCIe lanes which I need for other devices. However, I've read that cycling through multiple VMs may not work. I connected a Lenovo-branded USB keyboard to a USB port which is shared with the host Unraid OS. This device has a single function. This is a re-branded LITE-ON device. root@Tower:/# ls /dev/input/by-id usb-LITE-ON_Technology_USB_NetVista_Full_Width_Keyboard.-event-kbd@ I confirmed that this is the correct device I want to pass through with evdev by running cat and pressing a key on the keyboard before pressing control+c with my "primary" keyboard. root@Tower:/# cat /dev/input/by-id/usb-LITE-ON_Technology_USB_NetVista_Full_Width_Keyboard.-event-kbd }/cr(}/cr}/cr}/cq (}/cq }/cq I edited the qemu.conf configuration with this command root@Tower:/# nano /etc/libvirt/qemu.conf I found the relevant lines and modified them accordingly: cgroup_device_acl = [ "/dev/null", "/dev/full", "/dev/zero", "/dev/random", "/dev/urandom", "/dev/ptmx", "/dev/kvm", "/dev/kqemu", "/dev/rtc","/dev/hpet", "/dev/input/by-id/usb-LITE-ON_Technology_USB_NetVista_Full_Width_Keyboard.-event-kbd" ] I modified the VM XML configuration: <qemu:commandline> <qemu:arg value='-object'/> <qemu:arg value='input-linux,id=kbd,evdev=/dev/input/by-id/usb-LITE-ON_Technology_USB_NetVista_Full_Width_Keyboard.-event-kbd,grab_all=on,repeat=on'/> <qemu:arg value='-object'/> </qemu:commandline> </domain> To make these changes take effect, I reboot the PC. I get this error when I start the VM. internal error: process exited while connecting to monitor: qemu-system-x86_64: -object -sandbox: Parameter 'qom-type' does not accept value '-sandbox' Searches for this error, or parts of this error on Google, the Unraid forums, github, and stackoverflow return no results. I am writing this post, mid-way through my troubleshooting process. After rebooting again, I get these errors I get this error when trying to launch the VNC VM: "error: Failed to attach device from /tmp/hotattach.tmp error: XML error: Invalid value for attribute 'id' in element 'product': '0x0000#remove'. Expected non-negative integer value" My existing VMs with passed-through USB devices lose connection to my primary USB devices! The /etc/libvirt folder is empty. Ultimately, my Unraid PC in this state is unsuable. I need to use another machine to revert the changes I made to my VM configuration and reboot again. This may take multiple attempts, and due to my PC's complex configuration (Slow BIOS boot, HBA BIOS boot), it takes about 5-7 minutes before I can attempt power on. I am about to try editing the permission level which libvirt run at according to this post: https://passthroughpo.st/using-evdev-passthrough-seamless-vm-input/ I made this change: user = "root" # The group for QEMU processes run by the system instance. It can be # specified in a similar way to user. group = "root" #group = "user" I am about to reboot and see if editing these permissions allow the VM to work successfully.

Hi ich777, I have been battling fan speed control issues for months. I have an it8628-isa-0a40, I detailed my issues here: https://github.com/lm-sensors/lm-sensors/issues/373 Today I updated Unraid to 6.10 and saw in the app store your driver and tried it, but unfortunately it didn't work Can you assist? BTW, do you have another method instead of paypal? Edit: I checked https://post.smzdm.com/p/a270z6g2/ again and I found that my IOMMU settings which Unraid added messed up the order of my acpi_enforce_resources=lax setting. I fixed it, rebooted and set sudo modprobe it87 force_id=0x8628, and the devices re-appeared, so I will re-follow the guide. I created a user script "fix_it8686E" which includes the sudo command and i run it "At First Array Start Only", but I'm concerned this will still wipe out the GUI settings on each reboot. Is there a better way?

Short update: changing to Display Port 1.2 did not result in any change. Neither did modifying the xml configuration.

Sorry, I was not clear, let try to use a timeline to explain what's happening... | Time | State/Function | Display Port - Plugged in | HDMI Port - Plugged in | | Begin | Unraid fresh boot | Unraid Video Console (Arch Login) - mirrored | Unraid Video Console (Arch Login) - mirrored| | +00:50 | Launch VM from WebUI | No video | No video | At this point, the TianCore KVM engine starts running. Now, this is what is happening while there is no video (Only if HDMI Port is plugged in, or if I use my other VM, which only has HDMI): The "boot from CD/DVD... press space" line of text appears, and then the VM continues the UEFI process, which lists all the attached drives/partitions to the system. A five second countdown begins and then the UEFI console. I type "exit", then navigate the menus to boot from the partition on the passed through NVME drive. As so as I get into Windows, the display is recognized. So this problem is not a Windows problem. It's a UEFI/TianCore(KVM) issue. I will try making the function adjustment to hostdev1 and I will also try configuring the monitor to use Display Port Version 1.2 to see if that works; that opens another can of worms though.

Hello, I apologize that my first post on these forums is for a support issue. I really like Unraid - its minor inconveniences are far outweighed by its positives. The virtualization and Docker features have revolutionized my computing experience and allowed me to get more out of one system. Now on to my issue described in the title... I have passed through an MSI 960 GTX to a VM. This GPU has multiple outputs. I am using a Display Port output and HDMI simultaneously, but I cannot get video output at the TianoCore VM boot screen if I have the Display Port cable connected. The system reaches the UEFI interface, there's just no video. I sometimes require access to the UEFI interface, so I prefer not to set any automated "boot to OS" UEFI configuration/firmware. However, if I disconnect the Display Port cable, and launch the VM, (or type "reset" at the UEFI interface), the VM will restart and video outputs to the HDMI screen just fine. I have no problems in Windows, both screens work simultaneously. So, this is mostly just a moderately annoying problem - I don't want to have to reach behind my monitor to unplug the Display Port cable each time I reboot the OS (Windows). I have tried each of the 3 Display Port outputs on the GPU and get the same result. Also interestingly, my GPU has an HDMI output, but when I use a passive Display Port to HDMI adapter, (DP > HDMI Adapter > HDMI Cable> Monitor), I get video output at the UEFI screen. I'm less convinced this is a hardware/slot issue since it works in Windows. Plus, due to my complex IOMMU configuration (2 GPUs, multiple PCIe cards), I'm not about to try re-seating the card in a different PCIe slot since re-configuring the Unraid takes 30 minutes per change. The monitor is a BenQ D43-720 4k display with the ability to view multiple inputs simultaneously. (1x 4k, 2x top/bottom or left/right, or 4x 1080p) 1x 4K 60 Hz Display Port input - Connected with 2x 2 meter Display Port cables and a passive coupler/extender 2x 4K 60 Hz HDMI Inputs 1x 4K USB-C Input 2x 1080P HDMI inputs - The HDMI output is connected to this screen through a 5 meter, low quality cable (will not pass 4K HDMI 60 Hz). I performed some searches prior to posting, but could not come up with any relevant results. I also tried Googling, but their changes to their algorithm to prioritize SEO, returns fewer and fewer good results. Unraid Forums search for "display port" Hardware Configuration Intel 10980XE X299 AORUS Gaming 3 Pro Nvidia GeForce GTX 960 Nvidia 1030 - passed through to another VM, no problem with 4K output to an HDMI input. UEFI displays fine. Passed Through Devices to this VM: MSI - Nvidia GeForce GTX 960 (GM206), 2048 MB Bios 84.06.0D.00.1D Link to Techpowerup card information I dumped the bios myself, removed the header, and specified it as the “Graphics ROM BIOS”. USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/980PRO Unraid Software Configuration: I have installed the "VFIO-PCI CFG" plug-in to pass through IOMMU groups. VM Configuration Machine: i440fx-5.1 BIOS: OVMF Hyper-V: Yes USB Controller: 2.0 (EHC) OS Install ISO: Windows.iso Here is the obligatory XML of my configuration. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='10'> <name>Windows 10</name> <uuid>Redacted</uuid> <description>MAIN</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>33030144</memory> <currentMemory unit='KiB'>33030144</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='20'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='22'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='24'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='26'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='28'/> <vcpupin vcpu='10' cpuset='12'/> <vcpupin vcpu='11' cpuset='30'/> <vcpupin vcpu='12' cpuset='14'/> <vcpupin vcpu='13' cpuset='32'/> <vcpupin vcpu='14' cpuset='16'/> <vcpupin vcpu='15' cpuset='34'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/REDACTED_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='8' 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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows.iso' index='2'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:be:10:cf'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-10-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x65' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/cache/isos/GM206_no_header.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x65' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x18' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>