fartmaster

Members
  • Posts

    8
  • Joined

  • Last visited

fartmaster's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. Let me just start with I am sorry to join the other 1000 posts about GPU passthrough, but it seems as though any fix I try will not cooperate. So, I have a server that runs as a media server (plex, sonarr, radarr etc.) which uses a GTX1660 Super for transcoding, all works as intended. My house mate handed me his old GTX650ti so I thought I would have a crack at GPU passthrough for remote gaming (retro games, nothing too serious). So I have been searching and following guides for about a month now trying to get it to work, I am currently at the point where my VM will see the GPU, but refuse to use it (the infamous error 43). I have been following the guide below to try and get my remote gaming machine working: https://forums.serverbuilds.net/t/guide-remote-gaming-on-unraid/4248/9 I have watched and configured my GPU passthrough as shown in all of spaceinvader ones videos. What I can remember I have tried so far: - IOMMU is enabled in BIOS - ensured no issues with old gpu (tested on another pc) - vbios dump edited with hex editor and configured for VM - enabled and disabled hyper-v - edited the xml, here's the entire file as it stands (I have chopped and changed the xml A LOT, so any fixes are very much appreciated): <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>i440parsec</name> <uuid>a8735db1-7631-acd0-24fd-af4a2b6b703f</uuid> <description>Remote Gaming Machine</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='15'/> <emulatorpin cpuset='9'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/a8735db1-7631-acd0-24fd-af4a2b6b703f_VARS-pure-efi-tpm.fd</nvram> </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> <kvm> <hidden state='on'/> </kvm> <vmport state='off'/> <ioapic driver='kvm'/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> </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/i440parsec/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <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/virtio-win-0.1.229-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> <controller type='pci' index='3' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f4:cc:76'/> <source bridge='br0'/> <model type='virtio-net'/> <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'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/vbios/gtx650ti.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> </domain> If anyone is able to get my passthrough working, I would finally be able to get a good nights sleep, hugely appreciate the time and effort. (LATEST DIAGNOSTICS ATTACHED) mothership-diagnostics-20230819-1836.zip
  2. I managed to find a reddit post that links directly to the issue we are having, see below: https://www.reddit.com/r/unRAID/comments/vihdpw/how_do_i_actually_connect_to_my_virtual_machine/ Basically, GPU passthrough is required, when you select the GPU in the VM options, the display should come through the GPU with a monitor connected. I haven't got it working as of yet, but the reddit post basically shows step by step what you need to do, as well as other options you can try. I don't want to completely steal suggestions but the reddit user "Nososs" had this to say: - Passthrough GPU -- Start VM through Unraid GUI -- Connect Monitor Cable to Video Card directly -- There's a lot of guides on how do this, and space invader has one too. - VNC Remote through the Unraid Gui -- Click on the VM -- Select VNC Remote -- You will get a local Console Desktop - Remote Desktop -- If it's a Windows Machine -- You can enable Remote Desktop on it, and then from another PC You can RDP through Remote Desktop Connection (Start ---> Run --- MSTSC) -- (You would RDP to the Windows IP not the Unraid GUI IP) - VNC to Desktop -- If it's a Linux Box then you'll have to find a walkthrough for your appropriate distro and then using a VNC Client from another machine, you can connect directly to the machine that way (You would connect once again to the VM IP not the GUI IP) - If you don't feel like doing 3 or 4 -- You can install some sort of TeamViewer, Splashtop, Anydesk etc..... Also I should mention that SpaceInvaderOne actually has tutorials on GPU passthrough as well Hope this helps, FartMaster
  3. Pushing this again as I have the same question as Markus. Markus, did you end up getting this one working? Basically followed the tutorial, GPU passthrough is up and running and the Lakka VM has started, but nothing opens. I can see the VM in my router settings and can ping it from my PC. Tried different options such as SSH and NoMachine to connect to it with no success. Is there anyone that can help with this? I really hope I just look silly and can connect to the VM extremely easily. Thanks in advance.
  4. I've posted in the past about hardware errors on my server and thought it may have been a docker I was using, but the hardware errors are beginning to show again and my server will crash every couple of days. Is anyone able to decifer my syslog and tell me what I have done wrong? Thanks in advance tower-diagnostics-20230403-1101.zip
  5. So I let my parity-sync finish and started up my dockers one at a time, everything ran fine until I started the Plex Docker. About 30 minutes after starting the Plex Docker my server crashed. Uninstalled Plex and removed it completely, installed the binhex-PlexPass Docker instead and haven't seen any issues since.
  6. So I've done what you suggested, no crashes or freezes after server has been running for 8 hours. Parity-sync is at 50% when it never usually gets past 10-15%. I'd say at this stage it's a pretty good guess to say it's a docker or plugin I have installed. Thanks for the suggestion, I will do what you suggested and turn everything back on 1 at a time to pin point what's causing issues.
  7. Syslog server doesn't seem to be picking anything up, very confused as 95% of my hardware is almost brand new. Starting to get a little concerned lmao
  8. Hey forum, posting here as suggested by the Fix Common Problems plugin. My server seems to be having hardware problems and I can't figure out the cause of the issue. My server will either spin down the array or freeze completely every 30-60 minutes, any ideas? Rather new to Unraid and servers in general, can't read the syslog at all. tower-diagnostics-20230313-1952.zip