kage1414

Members
  • Posts

    22
  • Joined

  • Last visited

Recent Profile Visitors

812 profile views

kage1414's Achievements

Noob

Noob (1/14)

2

Reputation

  1. This was the fix for me. My server was using up more memory than it usually does. Maybe we need better error reporting in this instance? Seems like a simple out-of-memory error that could be easily diagnosable by the user with better error reporting.
  2. Bump, also looking for a solution. Wish their anti-cheat was smarter than just looking for vm usage. I only use Windows for games and I'm not trying to build a dedicated gaming PC
  3. tower-smart-20221207-1051 (1).zip Result was "Completed: Read Failure"
  4. tower-diagnostics-20221207-1044.zip Moved parity disk to an unassigned device (sdi)
  5. My parity disk is disabled as of this afternoon. I know there can be a lot of causes for disabled disks. I've tried some troubleshooting but still having issues. I've tried: Stopping array and removing disk from parity slot Starting Array Stopped again and re-adding (and removing the disk from historical devices) This allows a parity check to start, but the disk gets disabled after a few minutes I've also tried power cycling the server, but this didn't seem to make a difference Is this possible a cable/power issue, or is my drive dead? tower-diagnostics-20221206-2315.zip
  6. Currently waiting on PIA to get their shit together....
  7. No, I’m curious about the logs. Fix common problems is telling me that /var/log is 100% full. I will look at Speedtest and see if I can tone down the logging I’m also aware of the out of memory errors but that’s probably due to running several vms with a lot of memory allocated.
  8. I'm having an issue where my streams will timeout in the middle of a movie or tv episode. I'm streaming from the iOS plex app to a Chromecast. It only happens once per episode or movie but it requires me to switch to my phone and then back to the Chromecast. Any ideas what may be causing it?
  9. I have a NiceHash OS vm that I like to run in the background when I'm not using my gpu or on vacation. I often lose power for several seconds or minutes at a time where I live, and since the GPU draws so much power when mining the UPS can only run for 1-2 minutes on UPS power alone, which is also about the amount of time unraid needs to power down. Thus UPS daemon immediately will shutdown unRaid upon power loss, and If I'm away for several days I have no way to restart unraid once power is regained (I know you can use ACPI, but it won't work if it's a clean shutdown). I don't know how many other miners are using unraid, but I think it could be beneficial to be able to shutdown VMs or Docker containers upon power loss in order to maximize time on UPS, and then start them back up once power is back. It could be defined as a low-power mode where you can define critical containers or vms.
  10. I dumped the gpu bios and passed it through and the gpu is working better than it did. At first it booted, but the VM did not log into Windows and went to a blue screen giving a hardware error. Eventually it stopped booting. I've attached another more recent diagnostics file Anybody with any ideas? tower-diagnostics-20200609-2143.zip
  11. Hey all, I have a Windows gaming VM that runs from an NVME drive. Yesterday I started to setup a sonarr docker container, and also had to remap some paths in my deluge container to use privoxy, and there ended up being an error and the deluge container didn't install. I tried again and the container worked fine, but then I went over to start up my Windows VM, and it booted up but I was getting about 1 fps from the gpu. I stopped and restarted the VM and then it just didn't start and the logs gave the error "vfio: Cannot reset device 0000:03:00.0, depends on group 18 which is not owned". Group 18 is the SATA controller that all of my array drives are attached to so I can't pass that through. I've also tried disabling the USB Controller and it still isn't booting. I've tried a number of different things I've seen around the forums but still haven't found a solution. Here is my Vm xml: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10 - Baremetal</name> <uuid>fdab1aa8-87c8-8514-a27b-2cf05d07cab2</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'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='11'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='12'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='14'/> <vcpupin vcpu='8' cpuset='7'/> <vcpupin vcpu='9' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-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/fdab1aa8-87c8-8514-a27b-2cf05d07cab2_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='5' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </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='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='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> <controller type='pci' index='0' model='pcie-root'/> <interface type='bridge'> <mac address='52:54:00:01:3d:3a'/> <source bridge='br0'/> <model type='virtio'/> <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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x27' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x27' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <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='0x05' slot='0x00' 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='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain> VM log: -uuid fdab1aa8-87c8-8514-a27b-2cf05d07cab2 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=33,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -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 qemu-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.173-2.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.1,drive=libvirt-1-format,id=sata0-0-1 \ -netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:01:3d:3a,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=37,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:27:00.0,id=hostdev0,bus=pci.3,multifunction=on,addr=0x0 \ -device vfio-pci,host=0000:27:00.1,id=hostdev1,bus=pci.4,addr=0x0.0x1 \ -device vfio-pci,host=0000:01:00.0,id=hostdev2,bus=pci.5,addr=0x0 \ -device vfio-pci,host=0000:03:00.0,id=hostdev3,bus=pci.6,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-06-07 16:47:28.310+0000: Domain id=3 is tainted: high-privileges 2020-06-07 16:47:28.310+0000: Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2020-06-07T16:47:31.183134Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.0, depends on group 18 which is not owned. 2020-06-07T16:47:32.254110Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.0, depends on group 18 which is not owned. Another thing worth mentioning, before this issue appeared I never had to pass through my rom bios, but the logs say it's necessary. I've also tried deleting libvirt.img and docker.img but it hasn't changed anything either. I've also isolated the cpus that the vm is using. The system boots fine if I remove the unRaid USB and just boot into Windows, so I don't think that it's the nvme drive. Any ideas? tower-diagnostics-20200607-1243.zip
  12. I've tried it, didn't fix. Stumbled across this post. I booted the VM, remoted in with teamviewer, and installed the drivers and now I've got it working!
  13. I had added one of those parameters at one point (don't remember which one) and it didn't help. Should I add it under Global Configuration or unRaid OS?
  14. Hey all, I'm about at my wits end here with this issue. I've used unRaid for about 3 years now, but I've never attempted any sort of hardware passthrough. I just built a brand new server and have been able to get everything up and running correctly, except that I cannot for the life of me get GPU passthrough working. Ultimately I want to use the GPU for a gaming VM. Below is the hardware for my new server: MSI X570 Gaming Plus Max (current BIOS) Ryzen 7 3700x Sapphire Pulse RX 580 8GB G.SKILL Ripjaws V Series 32GB (2 x 16GB) DDR4 3200 EVGA 500 Watt PSU I've tried using multiple Spaceinvader One tutorials regarding Windows VM setup and GPU Passthrough. Spaceinvader One videos I've followed: The best way to install and setup a windows 10 vm as a daily driver or a Gaming VM Advanced GPU passthrough techniques on Unraid AMD RX 5700XT - Reviewing Passthrough to KVM Virtual Machines How to easily reset a passed through AMD Graphics card without rebooting Other things I've tried: Fully installing windows with Q35 and i440fx chipsets and installing AMD drivers through VNC Using VNC as primary graphics and passing through RX 580 as secondary Using RX 580 as primary sound card* Installing Ubuntu Desktop with Q35 Checked all USB ports/busses using lspci and lsusb to make sure I'm not passing through my unRaid usb disk The closest I get is the monitor switching from the terminal login to a black screen. It seems like it wants to passthrough, but I'm not getting any signal from the graphics card to the monitor. Once it gets to a black screen it doesn't do anything else unless I reboot the host. I've attached my diagnostics file. Under QEMU, "Windows 10" and "Ubuntu Desktop" are fresh installs using Q35. I also attempted to run "Ubuntu - Desktop," an old install of Ubuntu, but was also unsuccessful. *One thing that I did figure out was that my server did not want to passthrough the onboard sound card (29.00.4). Any time I would try that it would completely freeze the server. The syslogs said "vfio-pci 0000:29:00.4: not ready" so I removed it from the VM. I suspected this was because the flash drive was on the same bus, but I just switched the flash bus and tried it again and got the same error. For most of these attempts the only sound card passed through was from the RX 580. tower-diagnostics-20200513-1130.zip And below is my Windows VM XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>65e1c3af-c034-d392-6088-754a83fecc4e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-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/65e1c3af-c034-d392-6088-754a83fecc4e_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <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/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_1809Oct_English_x64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <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.173-2.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <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='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='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </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> <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> <interface type='bridge'> <mac address='52:54:00:43:1e:08'/> <source bridge='br0'/> <model type='virtio'/> <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'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x27' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x27' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x29' slot='0x00' function='0x4'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc077'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc31c'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2516'/> <product id='0x0051'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <memballoon model='none'/> </devices> </domain> The last thing I noticed is that KVM seems to be assigning my GPU and GPU sound to Bus 0x04 & 0x05 (reassigned back to 0x04) with slots at 0x00, whereas on Spaceinvader's tutorial his GPU busses were at 0x00 and his slots were populated.