Ross_The_Devil

So as the title says, now that Unraid natively supports zfs i have two pools set up. neither of which will mount at boot. I did set a user scripts to mount each one individually at array start, but this obviously isnt quick enough for unraid as i use one of the pools for the storage of my docker containers and libvirt image, so both docker and vm fail to start giving path errors (Obviously doesnt exists until i manually mount the two pools) So is there a way for unraid to natively mount these pools (Without destroying them and recreating them, have over 8TB of data that i just cba to move around again).

So quick one. Ive set up a VM (Ubuntu Server) used virtio-net (and just virtio) as networking and selected Br0 (This is set up on unraids networking settings) but i have no connectivity. Troublshooting using dhclient shows the discover go out to the network, checking my firewall i can see the request and the reply being senbt back, but the vm fails to obtain an ip. I passed through a network port and that worked straight away, switched back tothe virtual net and nothing (Tried all the virtual nics) if however i change to virbr0 i get connectivity, although this is nat'd and thats not what i need. So what else can i do with regards to br0. Side note, dockers work using br0.(Vlan number here) but using one of the br0.(vlans) on the vm still results in no connectivity. (have tried deleting network.cfg and re-setting up networking. still nothing. Unraids on 6.12.4

That bit of advice is appreciated, i have since changed all my ip/subnets to stay within the realms of the private ip space. However the issue still persists, when the direct link is used, unraid and dockers loose conectivity.

So, Homelab use, but i use vlans, segregate everything i can. So i have my main vlan (10) and the rest trunked to unraid on a 10g link. its set native to 10 as i found unraid doesnt play nice with networking for eth0 with the use of vlans, so (10) comes in natively and anything else can access the other vlans perfectly fine, sorted! I aquired a couple of 40g NIC's, ones in my main PC and the other in unraid, both are set to ethernet mode, and both work! i gave them both a unique ip 14.1.1.11 and 14.1.1.10. i can use each others ip to ping each other and even transfer files. did a speed test and again very happy. so that was set to eth2. left eth0 as main connection for unraid to the lans and wan. Now the proplem, when this was set like this all outgoing traffic from unraid was going via the 14.1.1.10 ip address and not the 12.1.1.10 set for the vlan/lan. Once the faster direct link was disconnected unraid behaved again, but id really like the faster link for a direct link between pc and unraid as it makes file management so much quicker. Is there something i should be looking for in the configuration of this link? I did some checking and unraid was using the 14.1.1.10 ip address on the vlan. i made sure not to use a default gateway on th2 (direct link) as i am under the impression the use of a gateway will make it a lan connection, take away the gateway and itll be treated as direct? But yeah, how do i do a direct link between unraid and the pc with this faster link whilst maintaining the lan for docker/vms/unraid etc. Side note both unraid and pc are connected to the same lan/vlan but i am blocking traffic between the two using the switch.

So i managed to solve the two devices not fully showing in windows. It seems passing through a different usb controller did the trick. I suspect this has to do with how the on board audio and wifi chips are connected. As when booted barebones to windows both show up as usb devices, so yeah changing the usb controller which i passthrough has fixed this issue for me. Only took me 15 more hours :)

So, having used unraid for a while, enjoying it to say the least, but im having an issue with a windows 10 vm and pci passthrough. From what i can tell i have gotten lucky with my iommu groups, and have managed to passthrough my gpu just fine, but certain other devices just arent playing ball. I have a wireless card 'AX200' that has wireless 6 and bluetooth, the wireless part of the card shows up in windows, the bluetooth does not, once the drivers are installed windows reports the device is disconnected. Also tried passing through on board audio to make use of spdif but that just wont show in device manager on the vm at all. Specs are as follows AMD 3960x Threadripper 24c MSI Creators mobo 128GB ram (Not ecc) 8 hdd's using zfs and zfs plugin. VFIO config is as follows Group 0 00:01.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 1 00:01.11022:1483PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge Group 2 00:02.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 3 00:03.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 4 00:04.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 5 00:05.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 6 00:07.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 7 00:07.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] Group 8 00:08.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 9 00:08.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] Group 10 00:14.01022:790bSMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.31022:790eISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) Group 11 00:18.01022:1490Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 0 00:18.11022:1491Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 1 00:18.21022:1492Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 2 00:18.31022:1493Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 3 00:18.41022:1494Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 4 00:18.51022:1495Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 5 00:18.61022:1496Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 6 00:18.71022:1497Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 7 Group 12 01:00.01987:5012Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01) Group 13 02:00.01022:148aNon-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function Group 14 03:00.01022:1485Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP Group 15 03:00.31022:148cUSB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller *USB devices attached to controllers bound to vfio are not visible to unRAID* Group 16 20:01.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 17 20:02.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 18 20:03.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 19 20:03.11022:1483PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge Group 20 20:04.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 21 20:05.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 22 20:07.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 23 20:07.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] Group 24 20:08.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 25 20:08.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] Group 26 21:00.010de:1e04VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] (rev a1) 21:00.110de:10f7Audio device: NVIDIA Corporation TU102 High Definition Audio Controller (rev a1) 21:00.210de:1ad6USB controller: NVIDIA Corporation TU102 USB 3.1 Host Controller (rev a1) *USB devices attached to controllers bound to vfio are not visible to unRAID* 21:00.310de:1ad7Serial bus controller [0c80]: NVIDIA Corporation TU102 USB Type-C UCSI Controller (rev a1) *USB devices attached to controllers bound to vfio are not visible to unRAID* Group 27 22:00.01022:148aNon-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function Group 28 23:00.01022:1485Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP Group 29 23:00.11022:1486Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP Group 30 23:00.31022:148cUSB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller USB devices attached to this controller: Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Group 31 23:00.41022:1487Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Group 32 40:01.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 33 40:01.11022:1483PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge Group 34 40:01.31022:1483PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge Group 35 40:02.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 36 40:03.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 37 40:03.11022:1483PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge Group 38 40:04.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 39 40:05.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 40 40:07.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 41 40:07.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] Group 42 40:08.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 43 40:08.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] Group 44 41:00.01022:57adPCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream Group 45 42:02.01022:57a3PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge Group 46 42:03.01022:57a3PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge Group 47 42:04.01022:57a3PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge Group 48 42:05.01022:57a3PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge Group 49 42:08.01022:57a4PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 47:00.01022:1485Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 47:00.11022:149cUSB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller *USB devices attached to controllers bound to vfio are not visible to unRAID* 47:00.31022:149cUSB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller *USB devices attached to controllers bound to vfio are not visible to unRAID* Group 50 42:09.01022:57a4PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 48:00.01022:7901SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) Group 51 42:0a.01022:57a4PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 49:00.01022:7901SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) Group 52 43:00.01b21:3242USB controller: ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller *USB devices attached to controllers bound to vfio are not visible to unRAID* Group 53 44:00.01d6a:07b1Ethernet controller: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02) Group 54 45:00.08086:2723Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) Group 55 46:00.08086:1539Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) Group 56 4a:00.01000:0072Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) Group 57 4b:00.010de:1c82VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) 4b:00.110de:0fb9Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) Group 58 4c:00.01022:148aNon-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function Group 59 4d:00.01022:1485Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP Group 60 60:01.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 61 60:02.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 62 60:03.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 63 60:04.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 64 60:05.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 65 60:07.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 66 60:07.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] Group 67 60:08.01022:1482Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge Group 68 60:08.11022:1484PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] Group 69 61:00.01022:148aNon-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function Group 70 62:00.01022:1485Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP And vm config is as follows <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Windows 10 (Ross)</name> <uuid>72a0ff18-a3bb-e549-5ed2-a98334c9b9eb</uuid> <description>Ross&apos;s Gaming VM</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>28835840</memory> <currentMemory unit='KiB'>28835840</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='18'/> <vcpupin vcpu='1' cpuset='42'/> <vcpupin vcpu='2' cpuset='19'/> <vcpupin vcpu='3' cpuset='43'/> <vcpupin vcpu='4' cpuset='20'/> <vcpupin vcpu='5' cpuset='44'/> <vcpupin vcpu='6' cpuset='21'/> <vcpupin vcpu='7' cpuset='45'/> <vcpupin vcpu='8' cpuset='22'/> <vcpupin vcpu='9' cpuset='46'/> <vcpupin vcpu='10' cpuset='23'/> <vcpupin vcpu='11' cpuset='47'/> </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/72a0ff18-a3bb-e549-5ed2-a98334c9b9eb_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </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='hypervclock' present='yes'/> <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.189.iso' index='3'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/Storage/ISO/spaces_win_clover.img' index='2'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/wwn-0x5000c50052ed2bc8' index='1'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <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'/> <alias name='pci.2'/> <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='0x12'/> <alias name='pci.3'/> <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'/> <alias name='pci.4'/> <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='0x8'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x9'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xa'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xb'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0xc'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='10' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0xd'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='12' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='12' port='0xe'/> <alias name='pci.12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='13' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='13' port='0xf'/> <alias name='pci.13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='14' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='14' port='0x14'/> <alias name='pci.14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='15' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='15' port='0x15'/> <alias name='pci.15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:7c:03:a9'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-Windows 10 (Ross)/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/Storage/Back_Up/BIOS/VGA/2080TI.dump'/> <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='0x21' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <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='0x23' slot='0x00' function='0x4'/> </source> <alias name='hostdev2'/> <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='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x3'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x2'/> </source> <alias name='hostdev5'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x3'/> </source> <alias name='hostdev6'/> <address type='pci' domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/> </source> <alias name='hostdev7'/> <address type='pci' domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x45' slot='0x00' function='0x0'/> </source> <alias name='hostdev8'/> <address type='pci' domain='0x0000' bus='0x0d' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Absolutely nothing showing in the vm logs at all so nothing to paste. Any help pointing me in what im doing wrong would be much apprecaited. Ive tried for hours and hours alone and i've still gotten no where.