kalfun

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by kalfun

  1. You never transcode 4k, regardless if it's by CPU or iGPU. It just uses way too much resources. Always Direct Play. If you need to transcode 4k to play it, maybe you shouldn't be collecting it in the first place.
  2. What a coincidence, I have the exact same CPU! I guess I'll give it a shot. Thanks for putting this thread together btw!
  3. For anyone running Don't Starve Together: How is the performance? What hardware are you running on? Do you have caves enabled? How is the CPU usage? The reason why I'm asking is because I had DST running on a bare Ubuntu 18.04 install with caves and some server side mods and the process is running at 20% CPU usage while the server was EMPTY. The usage jumps up by 20% every time a person joins. When I have 3 people in the server, the CPU usage spikes up 90%. Any more after that and the game becomes unplayable. My wife was hosting it on her Windows 10 PC with a Ryzen 5 3600 and with the same amount of people, and no issues. So right now, I'm just trying to see if it's worth running in a docker format.
  4. Thanks for jogging my memory! I completely forgot that I have the bounded to vfio-pci.
  5. I have 2 NVME drives installed, but they're not visible under Unassigned Devices. Here's my diagnostic logs: tower-diagnostics-20201116-0320.zip The 2 drives were used in a Windows 10 VM as passthrough drives before. But I've since deleted the VM. Could that be the reason why? How would I go about making them visible again?
  6. You are FREAKING AMAZING! That's exactly what the issue was! I had to pull the dump off my own 1070ti for it to passthrough! Thank you so very much!
  7. I downloaded from Techpowerup. And yes, I removed the header from that dump. In the video, he left the file extension as ".dump" but it should be ".rom", no?
  8. I'm getting permission denied or the folder doesn't exist when I run the commands. How can I rectify this?
  9. Thanks to @paperblankets for pointing me in the right direction! For anyone who couldn't passthrough a single Nvidia card, and you already tried techpowerup's ROMs - dump your own card's ROM and try again. _____________ Unraid noob here Running Unraid 6.6.6 I'm trying to passthrough a 1070ti to my Ubuntu VM, which is installed in slot 1. I've installed Ubuntu at least 10 times and tried multiple combinations of what I've read online to get this to work. However, none of the following has worked for me. I've tried installing Ubuntu with VNC first, then switch to the GPU. I've followed this SpaceInvader's video. I tried this. Switched the Unraid USB from UEFI to Legacy Tried both OVMF and Seabios I've also tried adding the 1070ti to the Win10 VM, but that didn't work. The VM would start but all my monitors were blank. ***I cannot move the GPU as my system is custom watercooled.*** My system: I have a Windows 10 VM running with a passed-through 1080ti as well, and I had no problems with that machine. This is my XML: (I noticed that this XML has CPU 0 pinned, which I know should be reserved for Unraid. I've altered the pinnings in my own XML, but everything else is the same) <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Ubuntu Plex Machine</name> <metadata> <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='18'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='20'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='22'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/40325eb3-c630-81ab-d184-40583141d0d6_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='6' threads='1'/> </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/Ubuntu Plex Machine/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/ubuntu-18.04.1-desktop-amd64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </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='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xf'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:b5:8e:7d'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='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='0x42' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/Ubuntu Plex Machine/vbios/evga1070ti.rom'/> <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='0x42' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain>
  10. I'm new to unraid and I followed this video by Spaceinvader One. I have the bare metal Windows 10 set up, and I have the VM portion set up as well (correctly, I hope). But every time I start the VM, the entire system reboots. Specs: OS: Unraid 6.6.6 CPU: Threadripper 1950x stock clocks (3.4GHz) Motherboard: ASRock x399 Taichi Cooling: Custom Watercooled loop GPU: 1x Asus GTX 1080ti, 1x EVGA GTX 1070ti RAM: 32GB PSU: EVGA 850W I posted in Reddit yesterday, and I figured I'll post here too. Someone asked me to run this command on putty and start the VM after: tail -f /var/log/syslog And I got the following: Jan 17 12:43:11 tower dnsmasq[31396]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify Jan 17 12:43:11 tower dnsmasq-dhcp[31396]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Jan 17 12:43:11 tower dnsmasq-dhcp[31396]: DHCP, sockets bound exclusively to interface virbr0 Jan 17 12:43:11 tower dnsmasq[31396]: reading /etc/resolv.conf Jan 17 12:43:11 tower dnsmasq[31396]: using nameserver 192.168.1.1#53 Jan 17 12:43:11 tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Jan 17 12:43:11 tower dnsmasq[31396]: read /etc/hosts - 2 addresses Jan 17 12:43:11 tower dnsmasq[31396]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Jan 17 12:43:11 tower dnsmasq-dhcp[31396]: read /var/lib/libvirt/dnsmasq/default.hostsfile Jan 17 12:43:24 tower sshd[32034]: Accepted none for root from 192.168.1.126 port 58248 ssh2 Jan 17 12:44:26 tower kernel: vfio-pci 0000:09:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Jan 17 12:44:26 tower kernel: br0: port 2(vnet0) entered blocking state Jan 17 12:44:26 tower kernel: br0: port 2(vnet0) entered disabled state Jan 17 12:44:26 tower kernel: device vnet0 entered promiscuous mode Jan 17 12:44:26 tower kernel: br0: port 2(vnet0) entered blocking state Jan 17 12:44:26 tower kernel: br0: port 2(vnet0) entered forwarding state Jan 17 12:44:28 tower avahi-daemon[5176]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe34:84ad. Jan 17 12:44:28 tower avahi-daemon[5176]: New relevant interface vnet0.IPv6 for mDNS. Jan 17 12:44:28 tower avahi-daemon[5176]: Registering new address record for fe80::fc54:ff:fe34:84ad on vnet0.*. Jan 17 12:44:29 tower kernel: vfio-pci 0000:09:00.0: enabling device (0000 -> 0003) Jan 17 12:44:29 tower kernel: vfio_ecap_init: 0000:09:00.0 hiding ecap 0x19@0x900 Jan 17 12:44:29 tower kernel: vfio-pci 0000:0b:00.3: enabling device (0000 -> 0002) Jan 17 12:44:29 tower kernel: vfio_ecap_init: 0000:08:00.0 hiding ecap 0x19@0x168 Jan 17 12:44:29 tower kernel: vfio_ecap_init: 0000:08:00.0 hiding ecap 0x1e@0x190 Jan 17 12:44:29 tower kernel: vfio-pci 0000:0a:00.3: enabling device (0000 -> 0002) Jan 17 12:44:29 tower kernel: vfio-pci 0000:43:00.3: enabling device (0000 -> 0002) Someone else suggested it could be my PSU not providing enough power. Any ideas before I go out and buy a new PSU?