December 30, 20223 yr been trying to unified my nas and gaming pc using a type 1 hypervisor for the past few days. tried proxmox and esxi but not much luck (probably a end user error), lastly been trying unraid which so far make this easy enough, i was able to do some testing (windows vm, that has some usb devices, nvme ssd, gpu, etc) passed trough and the nas vm (xpenology/redpill/dsm 7) running my current storage/ iscsi gaming disk. i was able to do some gaming tests but i notice the same mouse tracking issue i once had (not sure if this related to overheating, usb bw or interference issue). however now the windows vm is bsod if the dsm vm is running. i have followed some guides and info for the most part but does anyone has a guide or any insight on how to make this happen? thank you in advance. system specs: Model: Custom M/B: ASUSTeK COMPUTER INC. PRIME X570-PRO Version Rev X.0x - s/n: BIOS: American Megatrends Inc. Version 4408. Dated: 10/27/2022 CPU: AMD Ryzen 7 5800X 8-Core @ 3800 MHz HVM: Enabled IOMMU: Enabled Cache: 512 KiB, 4 MB, 32 MB Memory: 64 GiB DDR4 (max. installable capacity 128 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 Kernel: Linux 5.19.17-Unraid x86_64 OpenSSL: 1.1.1s Uptime:
December 31, 20223 yr You posted about some problem you are having in a couple of old threads, but didn't actually explain what your problem was. Didn't seem likely your problem was really related to those old threads and I have locked them and directed everyone here instead. Please don't post in multiple threads about the same problem. It makes it impossible to coordinate responses.
January 1, 20233 yr Author am sorry if me replying to an old thread that no body replied/ a thread that sounds very similar to the issue am having activated some kind of alarm go off or made u uncomfortable. i just spent money in your pro license for your product and am a little frustrated. am having some major issues and am in need some kind of support and possibly a fix otherwise i would like my money back and will go back to using two boxes, simple as that. Edited January 1, 20233 yr by aniel
January 1, 20233 yr Almost everyone on this forum, including moderators such as myself, are fellow Unraid users trying to help each other. So, it is not MY product. Free support is on the forum from your fellow users. Old threads might be OK to post to, but often another thread that reminds you of a problem you are having is often very different in the details. And you didn't give any details in those other threads. The main point I wanted to make, though: 19 hours ago, trurl said: Please don't post in multiple threads about the same problem. It makes it impossible to coordinate responses. Help us help you.
January 2, 20233 yr @aniel I apologize for the heavy-handed moderation. Let me see if I can get this back on track by posting a few links. Maybe some of this material you are already aware of. https://wiki.unraid.net/Manual/VM_Management https://wiki.unraid.net/Manual/VM_Guest_Support https://forums.unraid.net/topic/51703-vm-faq/ https://www.youtube.com/watch?v=CfUvY65qt-k&list=PL6MCtOroZNDDz61KrezJhhSlpKYGd--60&index=7 And now that I have bumped this thread, I will butt out and hope others will step in.
January 2, 20233 yr Author aww thank you this means a lot. also i have a little more inside and ai also joined the uraid discord but am yet to find a solution Edited January 2, 20233 yr by aniel
January 2, 20233 yr Author here are my vms xml: windows vm: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>aniel-windows-gaming-vm</name> <uuid>73b12f6b-58a1-bf5d-443c-4cd20b89d41b</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>17301504</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='10'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='11'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='12'/> <vcpupin vcpu='8' cpuset='5'/> <vcpupin vcpu='9' cpuset='13'/> <vcpupin vcpu='10' cpuset='6'/> <vcpupin vcpu='11' cpuset='14'/> </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/73b12f6b-58a1-bf5d-443c-4cd20b89d41b_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> </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='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.225-2.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </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:7a:d1:48'/> <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='0x0a' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/> </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='0x0c' slot='0x00' function='0x4'/> </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> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc08b'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1038'/> <product id='0x1610'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x022b'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <memballoon model='none'/> </devices> </domain> xpenology/redpill/dsm 7 vm: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>xpenology (redpill)</name> <uuid>09d8390b-87b9-9ab2-8ca6-9b0b4ff509cb</uuid> <metadata> <vmtemplate xmlns="unraid" name="CentOS" icon="linux.png" os="centos"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='7'/> <vcpupin vcpu='1' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/09d8390b-87b9-9ab2-8ca6-9b0b4ff509cb_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='1' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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/VMs/xpenology (redpill)/arpl.img'/> <target dev='hdc' bus='usb'/> <boot order='1'/> <address type='usb' bus='0' port='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='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' 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='0x03' 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='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='00:11:32:f9:6d:35'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x02' 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='2'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <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='0x04' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> i did some more ts as described in this video by changing it from passthrough to model and i still getting the same issue. also i have to mention that i thought/ the issue is related to either the virtio drivers and/or the combination of the two vm (sw and/or hw wise) but what makes it more strange is that i get it stable if remove the virtio driver from the windows vm however i did tried passing taught a nic to the windows vm thinking this was related to the virtio networking driver but no the windows vm still crashed when passing trough the physical nic/ as soon as i plug in the cable.) Edited January 2, 20233 yr by aniel
January 4, 20233 yr Author this is disgusting, you guys suck. am getting no response, no support, no acknowledge, no anything. am very disappointed. Edited January 4, 20233 yr by aniel
January 4, 20233 yr Community Expert On 1/2/2023 at 5:27 PM, aniel said: here is the diagnostic: tower-diagnostics-20230102-1226.zip 86.94 kB · 2 downloads Does it work ok if just running one VM?
January 4, 20233 yr Community Expert 37 minutes ago, aniel said: yes there are in qemu and libvirt logs but cant same what the issue is a present. Configs look ok. You have a lot of pci devices passed thru can you screen print the template and I will try and look tomorrow.
January 4, 20233 yr Author more info (btw idk how to print): tower-syslog-20230104-2230.zip /sys/bus/pci/devices/0000:04:00.0/iommu_group/devices/0000:04:00.0 Binding... Successfully bound the device 1000:0072 at 0000:04:00.0 to vfio-pci --- Processing 0000:07:00.3 1022:149c Vendor:Device 1022:149c found at 0000:07:00.3 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:07:00.3/iommu_group/devices/0000:07:00.3 Binding... Unbound 0000:07:00.3 from xhci_hcd Successfully bound the device 1022:149c at 0000:07:00.3 to vfio-pci --- Processing 0000:08:00.0 1022:7901 Vendor:Device 1022:7901 found at 0000:08:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:08:00.0/iommu_group/devices/0000:08:00.0 Binding... Successfully bound the device 1022:7901 at 0000:08:00.0 to vfio-pci --- Processing 0000:09:00.0 1022:7901 Vendor:Device 1022:7901 found at 0000:09:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:09:00.0/iommu_group/devices/0000:09:00.0 Binding... Successfully bound the device 1022:7901 at 0000:09:00.0 to vfio-pci --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:01.0/0000:03:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:04:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:07:00.3 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:08:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:08:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:09:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:09:00.0
January 5, 20233 yr Community Expert 8 hours ago, aniel said: more info (btw idk how to print): tower-syslog-20230104-2230.zip /sys/bus/pci/devices/0000:04:00.0/iommu_group/devices/0000:04:00.0 Binding... Successfully bound the device 1000:0072 at 0000:04:00.0 to vfio-pci --- Processing 0000:07:00.3 1022:149c Vendor:Device 1022:149c found at 0000:07:00.3 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:07:00.3/iommu_group/devices/0000:07:00.3 Binding... Unbound 0000:07:00.3 from xhci_hcd Successfully bound the device 1022:149c at 0000:07:00.3 to vfio-pci --- Processing 0000:08:00.0 1022:7901 Vendor:Device 1022:7901 found at 0000:08:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:08:00.0/iommu_group/devices/0000:08:00.0 Binding... Successfully bound the device 1022:7901 at 0000:08:00.0 to vfio-pci --- Processing 0000:09:00.0 1022:7901 Vendor:Device 1022:7901 found at 0000:09:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:09:00.0/iommu_group/devices/0000:09:00.0 Binding... Successfully bound the device 1022:7901 at 0000:09:00.0 to vfio-pci --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:01.0/0000:03:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:04:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:07:00.3 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:08:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:08:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:09:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:09:00.0 How do you access the GUI, I use the sniip & scetch tool in windows. Was look for some like this.
January 20, 20233 yr Author Solution so it ended up being a windows issue (most likely some kind of driver interference). after uninstalling a couple of sw that i had some suspicion, running a "windows repair tool" issue went away but after notice some performance loss i decided to go back to using two boxes. thank u to all of those that provided support and my apologies for pming some of you and getting frustrated for an "end user error" situation.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.