-
Wireless Mouse Sticking
Ive been having this problem since I created my VM a year ago. Ive tried both SteelSeries Apex and Logitec wireelss keyboard. Eventually when gaming or using the VM the keyboard will stick on a key and that key repeats until i power cycle the keyboard switch. Then it works for a while then sticks on a random key again., Any thoughts
-
At wits end with Games crashing Windows VM with AMD passthrough
I felt like we were close. VM booted great. Went into windows..started Cyberpunk...almost got to game play and the VM froze again. I even DDU'ed the drivers and reinstalled the newest AMD. I guess im going to have to sell this card and buy an nVidia. I cant thank you so much for your time.
-
At wits end with Games crashing Windows VM with AMD passthrough
OK 4g and UP are enabled in the BIOS. GPU/Soundcard are bound and in their own IMMOU groups. Not sure what this means "also you used vmd for modprobe not vfio..." I bound my NVME and USB hub because I boot the VM from the NVME (no vDISK) and the USB hub so i can attach USB disks to VM. here are current diags with edited XML. Here are latest tower-diagnostics-20250702-0148.zip
-
At wits end with Games crashing Windows VM with AMD passthrough
OK all steps done! booted into new GRUB line with all changes made. Here is my diag. prob just need to tweak the VM. not going to start it up until i hear back. Thanks again pal! tower-diagnostics-20250701-2349.zip
-
At wits end with Games crashing Windows VM with AMD passthrough
Ok i fixed the issue we are back in business with a standard syslinux.cfg like you wrote. onto the next
-
At wits end with Games crashing Windows VM with AMD passthrough
OK i screwed up something in the syslinux.cfg and now unraid wont boot. I took the usb drive to my pc and opened the syslinux.cfg and pasted a default one but its read only and wont let me save what do i do?
-
At wits end with Games crashing Windows VM with AMD passthrough
omg these instructions are amazing. yes intel motherboard I just resat my GPU in the motherboard...and disabled CSM and 4g in the BIOS. I will now do all your steps and post back
-
At wits end with Games crashing Windows VM with AMD passthrough
Yea I found that ROM online for that card and uploaded it to unraid. Ill remove the ROM line and try. LMK on the CFIO settings pleae and thanks!!!!!!
-
At wits end with Games crashing Windows VM with AMD passthrough
None of this worked sorry. Made all the adjustments. Unpinned CPUs and let unraid decide. DDU me display driver and installed from scratch. Booted great and windows itself is fine coming out from the AMD HDMI but first game i opened the VM crashes
-
At wits end with Games crashing Windows VM with AMD passthrough
Thank you so much I will try this. So unpin all of the CPUs from this VM as well as make the edits above?
-
gonzoflick started following At wits end with Games crashing Windows VM with AMD passthrough
-
At wits end with Games crashing Windows VM with AMD passthrough
Ive tried everything. Community drivers, old drivers, multiple re-installs. Same results. My AMD RX6750 passes through just fine however when i start games they load but then eventually freeze up and the VM becomes unresponsive. Im guessing I should have gone with nvidia but I didnt and hate to think I wasted $300. Here is my VM Config and diags. Is anything noticably wrong? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11</name> <uuid>4c428f86-dc51-5435-fafd-aa3a4e1581e0</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" iconold="windows11.png" icon="windows11.png" os="windowstpm" webui="" storage="default"/> </metadata> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>17301504</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='12'/> <vcpupin vcpu='1' cpuset='13'/> <vcpupin vcpu='2' cpuset='14'/> <vcpupin vcpu='3' cpuset='15'/> <vcpupin vcpu='4' cpuset='16'/> <vcpupin vcpu='5' cpuset='17'/> <vcpupin vcpu='6' cpuset='18'/> <vcpupin vcpu='7' cpuset='19'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-9.2'>hvm</type> <loader readonly='yes' type='pflash' format='raw'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram format='raw'>/etc/libvirt/qemu/nvram/4c428f86-dc51-5435-fafd-aa3a4e1581e0_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='4' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> </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/Win11_24H2_English_x64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='1'/> <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.266-1.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='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='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:c4:d9:aa'/> <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='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/isos/vbios/amdrx6750xt.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </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='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' 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='0x06' slot='0x00' function='0x0'/> </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='0xc08b'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1c4f'/> <product id='0x0002'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <watchdog model='itco' action='reset'/> <memballoon model='none'/> </devices> </domain> tower-diagnostics-20250701-1707.zip
-
M.2 Came lose. reported as missing. plugged back in and now array wont start
OK so i did a New Config on all drives and the array started with both cache drives showing green. parity is rebuilding. my dockers are all gone. i did a restore from the appdata plugin (after creating a new docker vdisk) and still my dockers arent showing. now what
-
M.2 Came lose. reported as missing. plugged back in and now array wont start
Both disks show now in cache pool. one is green the other blue. when starting array i get "wrong pool state" too many wrong of missing devices. diags attatched. please help array down! tower-diagnostics-20250405-2015.zip
-
LSI controller shows up but doesnt show attatched disk
Cable wasnt connected tightly. it is now and drive showed right up. thanks!
-
LSI controller shows up but doesnt show attatched disk
Ok thanks Ill check the cable. How do I run memtest on the cache pool?
gonzoflick
Members
-
Joined
-
Last visited