SoleInvictus

Members
  • Posts

    24
  • Joined

  • Last visited

Everything posted by SoleInvictus

  1. Why didn't I think of this?! It's so simple. I think I need a nap. Thank you!
  2. I have a kitten that loves to push buttons, especially when the HDD activity indicator light is integrated into it. Thanks to my little button murderer, I have had so many server shutdowns recently. I tried following the script and instructions found here to change button behavior but it doesn't work - the system keeps shutting down when the power button is pressed. Does anyone have any advice on how to change the power button's behavior? I'll update with version number - I'm pretty sure it's 6.12.4 but I have to go home and turn my server back on to verify. Thanks, kitten!
  3. Oh man, I see it now! You're absolutely right - I'll just use DelugeVPN. I was doing it this way because one site I use requires one's Torrent client to connect using the same IP as one's browser; however, I can just pass DelugeVPN's network to a Firefox container and achieve the same effect.
  4. Of course. Two ways: the IP address shown in the webGUI, plus I got a nasty email from my ISP regarding certain alleged activities, which is what made me realize all this was going on. What's extra weird is the IP in the GUI shows my ISP assigned IP, but curl ifconfig.io shows my VPN IP. I'm super confused here. Here's a recent copy of the log. Thank you so much for your help. supervisord - Copy.log Edit: something just occurred to me. Am I just starting up deluge too soon after system reboots? Is there a time period before privoxyvpn fully connects where that container allows access to the Internet without the VPN?
  5. I have a weird one. I use binhex-privoxyvpn to connect to my commercial VPN, PIA, then I route a few containers through that container so they're also using that VPN. This includes binhex-deluge. I do this by setting the network to none, then using "--net=container:binhex-privoxyvpn" in extra parameters for each container. Easy enough. I've noticed that binhex-deluge is frequently exposed, connecting to my home network and showing my home IP. From what I understood, the connection was supposed be killed if this were to happen, yet it keeps happening without any interruption - binhex-deluge just kept chugging along, oblivious to being on the absolute wrong network. This doesn't happen for the other containers. For example, I have a Firefox container set up similarly. While binhex-deluge is showing my home IP, Firefox shows my VPN's IP. They are set up identically, beyond having different port numbers. Any idea what's going on? I'm not sure where to even start, so please let me know which config info, if any, to post. Thank you! Edit: if this is a stupid way to configure this, I'm open to ideas. Just don't want to leak my IP.
  6. It's failure all around! I can no longer get SeaBIOS to work with my 3080. It will boot to the UEFI shell, but no further, under OVMF. Unfortunately, it won't even recognize my disk image as a drive under OVMF, so it's reinstallation time! After a refresh reinstall, it works fine, just gotta load everything back from scratch. Booo.
  7. Unfortunately, I upgraded a week after they recompiled the driver. I'm also not using the Nvidia-driver plug in, it's for a VM, so it doesn't apply to my case anyhow. I appreciate the input, any other ideas are welcome!
  8. After updating to 6.11.0, I can no longer get my VM to boot with my GTX 3080 Ti - it just sticks at a black screen. I've dumped the vBIOS and still have the same problem. I've rebooted the system. I've pleaded with it. I'm not quite sure where to go from here. It works just fine if I roll back to 6.9.4, but I'd really like to stop using the older version. Here are many configs/logs. Please let me know if I can do anything else to help! Boot Device Config default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS kernel /bzimage append pcie_acs_override=downstream,multifunction initrd=/bzroot label Unraid OS (No VGA) menu default kernel /bzimage append pcie_acs_override=downstream,multifunction video=efifb:off initrd=/bzroot label Unraid OS GUI Mode kernel /bzimage append pcie_acs_override=downstream,multifunction initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest VM config <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Living Room</name> <uuid>0c894896-76da-65e7-b2ec-0cdf280237c7</uuid> <description>Living Room</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'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='16'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='17'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='18'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='19'/> <vcpupin vcpu='8' cpuset='8'/> <vcpupin vcpu='9' cpuset='20'/> <vcpupin vcpu='10' cpuset='9'/> <vcpupin vcpu='11' cpuset='21'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <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='6' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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='raw' cache='writeback'/> <source file='/mnt/disks/S5H9NS1NA26184P/Living Room/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Living Room/vdisk2.img' index='1'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:24:bb:5c'/> <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-1-Living Room/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <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> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x32' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/vBIOS/GTX 3080.rom'/> <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='0x32' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2a' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> VM Boot Log 2022-10-01 01:06:01.728+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.19.9-Unraid, hostname: Catpanzer LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-1-Living Room' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-1-Living Room/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-1-Living Room/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-1-Living Room/.config' \ /usr/local/sbin/qemu \ -name 'guest=Living Room,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-Living Room/master-key.aes"}' \ -machine pc-i440fx-5.1,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,topoext=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \ -m 32256 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":33822867456}' \ -overcommit mem-lock=off \ -smp 12,sockets=1,dies=1,cores=6,threads=2 \ -uuid 0c894896-76da-65e7-b2ec-0cdf280237c7 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=34,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -blockdev '{"driver":"file","filename":"/mnt/disks/S5H9NS1NA26184P/Living Room/vdisk1.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":"raw","file":"libvirt-2-storage"}' \ -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-2-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Living Room/vdisk2.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.0,addr=0x5,drive=libvirt-1-format,id=virtio-disk3,write-cache=on \ -netdev tap,fd=35,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:24:bb:5c,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=33,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"}' \ -device 'vfio-pci,host=0000:32:00.0,id=hostdev0,bus=pci.0,addr=0x6,romfile=/mnt/user/vBIOS/GTX 3080.rom' \ -device vfio-pci,host=0000:32:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ -device vfio-pci,host=0000:2a:00.0,id=hostdev2,bus=pci.0,addr=0x9 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0)
  9. That makes three of us! I'm having the exact same issue and ran through the same sequence of troubleshooting steps. 6.9.2 for me until it's rectified.
  10. I had the same issue and fixed it - I needed to add my home network's IP range into the "allowedIPs" setting for my PC's peer configuration. For example, my network starts at 192.168.1.1, so my setting is AllowedIPs = 192.168.1.1/24 . Now it works!
  11. The title pretty much says it all. I'm running 6.9.2. I was able to pass through my primary GPU (1650 super) to a VM no problem prior to installing the Nvidia driver plugin. After installing it, I'm able to pass it through but Windows says there's an issue with the device (code 43) and defaults to the Windows lo-res basic drivers, and I can still see the blinking cursor of the Unraid command prompt on the screen. The screen will periodically glitch out, go black, and come back. I've tried both removing the driver plugin and rebuilding the VM, and the issue persists. I swapped the card with my secondary GPU and the problem sticks with the slot - whichever card is primary has the issue. If I just boot Unraid to the GUI, it works just fine no matter which card is primary. Any ideas before I rolled to a backup version (which I don't want to do since I haven't backed up for a couple of weeks because I'm dumb)? Edit: I fixed it! By adding the video=efifb:off string to my boot options (added after append, like this: append pcie_acs_override=downstream,multifunction video=efifb:off initrd=/bzroot), Unraid released its hold on my primary card and I'm now able to pass it through to a VM. It's more of a workaround than a fix, but it gets the job done for now. Hopefully this might help somebody else who gets stuck. VM XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Desktop</name> <uuid>6fb45c52-99a2-83dc-2163-541085f946d0</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='15'/> <vcpupin vcpu='8' cpuset='4'/> <vcpupin vcpu='9' cpuset='16'/> <vcpupin vcpu='10' cpuset='5'/> <vcpupin vcpu='11' cpuset='17'/> </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/6fb45c52-99a2-83dc-2163-541085f946d0_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='6' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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='raw' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_970_EVO_1TB_S5H9NS1NA26184P/Desktop/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Desktop/vdisk2.img' index='1'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0f:98:7f'/> <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-2-Desktop/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='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x32' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x32' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2a' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> catpanzer-diagnostics-20210425-1817.zip
  12. It takes about a minute or two, then you're up and running again with your existing OS install and no data lost. If that's "FML" worthy, Unraid probably isn't for you. It's not Windows 10, it requires occasional maintenance and troubleshooting.
  13. You'll have to make a new VM in unraid. You can just point it to your existing disc images so you don't have to do everything from scratch.
  14. Hey all! I've got another weird one I can't figure out. In my VMs and only my VMs, periodically I'll be unable to access certain sites. I can ping them just fine but they time out when I try to access them through any browser. After a few minutes, it'll randomly start working again. After a bit, another site will drop off. It's driving me crazy. The sites are seemingly at random, too - sometimes it's duckduckgo, other times reddit or netflix. It's not my DNS server as I've tried multiple, and it's only my VMs - other systems on the same network work just fine. Even Unraid itself works fine in the GUI when this happens. Any idea what could be going on?
  15. That did it! You're the best, thank you! We shall name our now functional word processing VM in your honor. For anyone else who might read this seeking to fix the same issue, here's what I did to fix the issue and, most importantly, keep it from happening again. Install The Correct Drivers - The Musical 1) Download Windows 10 64 bit WHQL Radeon Software Crimson version 16.10.1 (I got them from guru3d.com, drivers these old weren't available on AMDs site) and copy it to a USB drive. 2) Install Windows 10 like normal. When Windows boots for the first time, simply disable the network connection to prevent it from automatically updating the display drivers 3) Install previously downloaded drivers from USB drive. Disable Automatic Driver Updates - A Waltz of Seven Steps The previous instructions worked too well - Windows 10 would uninstall the drivers for the device altogether. Oops! 1) Right click the Start button and select Control Panel. 2) Make your way to System and Security. 3) Click System, then Advanced System Settings (in the left sidebar). 4) Select the Hardware tab. 5) Press the Device Installation Settings button. 6) Choose No, and then press the Save Changes button. 7) Now high five yourself, virtually high five testdasi for being awesome and helpful. You'll now have to update all of your drivers manually, display drivers or not, but at least you'll be able to do anything at all!
  16. Hi all! I'm stumped, hoping to get some help. I'm trying to run a Windows 10 VM. I have a couple of R9 380Xs lying around and I thought one would fit the bill. Oh, how I was wrong. I'm able to install Windows 10 and even make it through the initial boot just fine. As soon as I install the drivers, though, the VM locks up immediately upon the driver being initialized. After that, I am unable to get into Windows using the video card - it gets to the "spinning balls" stage of loading, the balls juggle for a few moments, then it locks up. Using VNC works just fine, both before and after installing the driver. There are no errors or warnings in the log. I've tried: Disabling/enabling CSM (currently disabled) and booting from UEFI and legacy Booting with and without vBIOS Hyper-V (in VM settings) enabled and disabled Changing between UVMF and seaBIOS, and between Q35 and i440fx All of these changes in various combinations I'm running unRAID 6.8.2. Here's my system hardware and VM XML: M/B: ASUSTeK COMPUTER INC. MAXIMUS VIII HERO (BIOS is up to date) CPU: Intel® Core™ i5-6600K CPU @ 3.50GHz GPU: XFX AMD R9 380X <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='6'> <name>Desktop</name> <uuid>90bcd89d-9ca1-0c0c-9683-2a9e93cf3346</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/90bcd89d-9ca1-0c0c-9683-2a9e93cf3346_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'> <topology sockets='1' cores='4' threads='1'/> </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='raw' cache='writeback'/> <source file='/mnt/disks/SPCC_M2_PCIe_SSD_7EBD079C096100503819/domains/Desktop/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_1909_English_x64.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.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='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> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:21:d2:3e'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-6-Desktop/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x02' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <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='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <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>
  17. I apologize. I had a rough day, was a little frustrated coming home and seeing that my second question to the forum would also likely yield no responses, and had a tongue loosened from a little too much whiskey. As you said, it's users helping users. No one is paid to do any of this, there are no expectations of participation. If I'm frustrated with so many forum questions remaining similarly unanswered, the best thing I can do is become an expert myself and start answering questions for others. I spent most of last night and a chunk of this morning figuring out my problem. For anyone having similar issues, the only way I can fix the input latency issue is: Use SeaBIOS and Q35 for my VM. For some reason, my VMs will only boot with OVMF if I use i440fx. I absolutely, positively cannot run anything at 3840x2160 (at any refresh rate), only 1920x1080 at most. I had originally set the desktop resolution to 3840x2160@60hz and games set similarly. I tried setting games alone at 1920x1080 but still experienced input latency. For whatever reason, if the desktop is set to 3840x2160, any programs, no matter their set resolution or refresh rate, will also experience input lag. This issue wasn't present before unRAID, so it appears to be related to using a VM. I hope someone else finds this to be of use!
  18. Bueller? Bueller? I got one hit from Reddit suggesting enabling MSI interrupts (didn't work) but have found the unRAID community to be completely silent the two times I've had a question. I'm kind of disappointed, I heard unRAID had a stellar support community.
  19. I had deleted the original post since I realized I originally posted in the wrong area. Sounds like we were working simultaneously.
  20. Hey all! I have an issue with input lag. I have what I'd guesstimate is about 200 - 300 ms of input lag - enough where if I zip my mouse left to right, when the mouse hits the right side of the mousepad, the cursor is still only halfway from its starting point. I understand a certain amount of input lag is normal in any system but this is just nuts. I've compared it to my laptop, while using the same hardware, and the lag isn't even noticeable. This goes for any input type: keyboard, mouse, or controller, wireless or wired. So far, I've tried: Unpinning CPU 0 as a tribute to Unraid's processing needs. Moving input devices to different USB controllers Booting my VM with and without its vBIOS Changing the USB controller setting from qemu to nec Challenging the input lag to a duel - it did not deign to respond Any help would be appreciated! I'm running 6.8.0. Here's my system hardware and VM XML: M/B: ASUSTeK COMPUTER INC. MAXIMUS VIII HERO Version Rev 1.xx - s/n: 151158051401424 BIOS: American Megatrends Inc. Version 3802. Dated: 03/15/2018 CPU: Intel® Core™ i5-6600K CPU @ 3.50GHz GPU: Nvidia GeForce 1660 Ti Memory: 16 GiB DDR4 <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Living_Room</name> <uuid>be85e0a5-387f-b6a8-6b12-3487a11bd7f9</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-4.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/be85e0a5-387f-b6a8-6b12-3487a11bd7f9_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'> <topology sockets='1' cores='4' threads='1'/> </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='raw' cache='writeback'/> <source file='/mnt/user/domains/Living_Room/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Living_Room/vdisk2.img'/> <target dev='hdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <interface type='bridge'> <mac address='52:54:00:21:54:3d'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <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='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> catpanzer-diagnostics-20200117-1617.zip
  21. Super noob question. I'm using an Nvidia 1660 ti with 6.8 (although this is just a general question). It works just fine whether I use its vBIOS or not. I've looked around online a bit but can't find the answer to my question - what exactly does using the vBIOS achieve, or did I just luck out with it working with or without the vBIOS?
  22. Hello! What I love most about unRAID is having a useful way to store my family's data, shared or not, and to host multiple systems from one computer. We temporarily live in a 5th wheel but need two computers - not having to have two towers is huge for us. One thing I'd love to see is assignable space limits for shares. Certain members of the household have a nasty habit of saving way too much junk and never going through it, so placing a limit on the junk saving would be super helpful