Cliff

I tried upgrading from stable to the latest beta after reading it worked well. But now I don't have any network, after booting it just says "ipv4 & ipv6 address not set" How can I fix this ? can I revert from the terminal or is it possible to fix the newtwork ? Motherboard: Asus tuf gaming x570-plus CPU AMD 3900X

I am the only one who get the status "stalled" on all downloads ? Most often torrents starts of att full speed then after a minute or so torrents get stalled and all network activity halts. after a few minutes all torrents start again. And then it continues in the same way stalled/downloading. I have been using rutorrent before and have never had this problem. I have 10TB free space, 1000/1000 Mbit/s connection and all torrents have lots of seeds/pers What can cause this problem ?

Solved. My Wireguard VPN file was generated to include a killswitch. If I just generated a plain ipv4 wireguard-config it works.

I am trying to use with wireguard and it looks like it starts ok. But I can't access the webui. Does anyone have any tips ? 2020-09-08 07:55:37.050982 [INFO] VPN_ENABLED defined as 'yes' 2020-09-08 07:55:37.064807 [INFO] DISABLE_IPV6 is set to '1' 2020-09-08 07:55:37.080506 [INFO] Disabling IPv6 in sysctl 2020-09-08 07:55:37.100444 [INFO] VPN_TYPE defined as 'wireguard' 2020-09-08 07:55:37.121190 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf dos2unix: converting file /config/wireguard/wg0.conf to Unix format... 2020-09-08 07:55:37.138884 [INFO] VPN remote line defined as '<hidden>:51820' 2020-09-08 07:55:37.155440 [INFO] VPN_REMOTE defined as '<hidden>' 2020-09-08 07:55:37.171694 [INFO] VPN_PORT defined as '51820' 2020-09-08 07:55:37.187473 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2020-09-08 07:55:37.203097 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2020-09-08 07:55:37.219644 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2020-09-08 07:55:37.237433 [INFO] NAME_SERVERS defined as '1.1.1.1,192.168.0.1' 2020-09-08 07:55:37.252383 [INFO] Adding 1.1.1.1 to resolv.conf 2020-09-08 07:55:37.267698 [INFO] Adding 192.168.0.1 to resolv.conf 2020-09-08 07:55:37.282799 [INFO] Starting WireGuard... Warning: `/config/wireguard/wg0.conf' is world accessible [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add <hidden>/32 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a wg0 -m 0 -x [#] wg set wg0 fwmark 51820 [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 [#] ip -4 rule add not fwmark 51820 table 51820 [#] ip -4 rule add table main suppress_prefixlength 0 [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 [#] iptables-restore -n [#] iptables -I OUTPUT ! -o wg0 -m mark ! --mark $(wg show wg0 fwmark) -m addrtype ! --dst-type LOCAL -j REJECT && ip6tables -I OUTPUT ! -o wg0 -m mark ! --mark $(wg show wg0 fwmark) -m addrtype ! --dst-type LOCAL -j REJECT 2020-09-08 07:55:37.403790 [INFO] Docker network defined as 172.17.0.0/16 2020-09-08 07:55:37.421942 [INFO] Adding 192.168.0.0/24 as route via docker eth0 2020-09-08 07:55:37.438087 [INFO] ip route defined as follows... -------------------- default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7 192.168.0.0/24 via 172.17.0.1 dev eth0 -------------------- iptable_mangle 16384 1 ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle 2020-09-08 07:55:37.460711 [INFO] iptable_mangle support detected, adding fwmark for tables 2020-09-08 07:55:37.542791 [INFO] iptables defined as follows... -------------------- -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i wg0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 51820 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT ! -o wg0 -m mark ! --mark 0xca6c -m addrtype ! --dst-type LOCAL -j REJECT --reject-with icmp-port-unreachable -A OUTPUT -o wg0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 51820 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -------------------- 2020-09-08 07:55:37.706126 [INFO] ENABLE_SSL is set to yes 2020-09-08 07:55:37.721200 [SYSTEM] If you use Unraid, and get something like a 'ERR_EMPTY_RESPONSE' in your browser, add https:// to the front of the IP, and/or do this: 2020-09-08 07:55:37.737314 [SYSTEM] Edit this Docker, change the slider in the top right to 'advanced view' and change http to https at the WebUI setting. 2020-09-08 07:55:37.753404 [INFO] /config/qBittorrent/config/qBittorrent.conf already has the line WebUICertificate.crt loaded, nothing to do. 2020-09-08 07:55:37.769123 [INFO] /config/qBittorrent/config/qBittorrent.conf already has the line WebUIKey.key loaded, nothing to do. 2020-09-08 07:55:37.784654 [INFO] /config/qBittorrent/config/qBittorrent.conf does have the WebUI\HTTPS\Enabled already set to true. 2020-09-08 07:55:37.801460 [INFO] A group with PGID 100 already exists in /etc/group, nothing to do. 2020-09-08 07:55:37.817167 [INFO] An user with PUID 99 already exists in /etc/passwd, nothing to do. 2020-09-08 07:55:37.833101 [INFO] UMASK defined as '002' 2020-09-08 07:55:37.849904 [INFO] Starting qBittorrent daemon... Logging to /config/qBittorrent/data/logs/qbittorrent.log. 2020-09-08 07:55:38.868764 [INFO] qBittorrent PID: 269 2020-09-08 07:55:38.874078 [INFO] Started qBittorrent daemon successfully... The only thing I changed was the default port 8080 and that I tried adding my router ip as a nameserver (but that made no difference)

I have had my Windows 10 VM running fine for over a year but I had an power outage that shut down my unraid server and now my Win10 VM refuses to start. The logs get spammed with: 2020-09-03T18:47:25.794965Z qemu-system-x86_64: vfio_region_write(0000:04:00.0:region1+0x1b7a78, 0xff2067b2ff2067b2,8) failed: Device or resource busy 2020-09-03T18:47:25.794973Z qemu-system-x86_64: vfio_region_write(0000:04:00.0:region1+0x1b7a80, 0xff2067b2ff2067b2,8) failed: Device or resource busy 2020-09-03T18:47:25.794979Z qemu-system-x86_64: vfio_region_write(0000:04:00.0:region1+0x1b7a88, 0xff2067b2ff2067b2,8) I am using an GTX 1060 with a dumped bios, could it be that the bios dump got corrupt? ocr can it be something else ? Edit: I just noticed one change, I have two GPUs and before I could only see the booting and unraid startup info if I connected a monitor to my second gpu. But now I see the bootup-info on my primary gpu. Is this a bios issue or do I need to re-apply some settings to unraid to switch the primary gpu ? I have also stubbed both gpus using the VFIO-Plugin

Is there any planned updates regarding Wireguard ? I think the possibility to route only specific docker-traffic through the Wireguard interface is wanted by many.

Is there still no possibility to only route specific docker traffic through a wireguard connection ?. I really only need wireguard for my ruTorrent traffic, but when enabling wireguard using my mullvad.net provider the vpn screws up a lot of my other containers network like plex, lms, homeassistant. If not, is this something that someone is working on ?

How do I undo changes made by the plugin? My unraid server will not boot anymore

I have installed a few docker containers but my img is already started to fill up as I get notifications about the docker image is over 70% full. I have seen other users having alot more docker apps than me, do they have a larger docker image or have I misconfigured anything? Most dockers use default settings so I would think that that is correct.

Ok How do I do that? When I boot in safemode I cant see any plugins. And when I boot normally I can only use the terminal

After running fine for weeks my unraid-server started reacting slow in the gui and when using home assistant docker. So I rebooted the server and after that the server is only accessible using safe mode. When I start unraid normally the terminal shows the same info as usual and gives me an ip but the web-ui is not accessible. If I reboot in safemode I can start the array and my virtual machines, but how do I figure out what is wrong? unraid-diagnostics-20200324-1828.zip

I am using Home Assistant docker in host mode and am trying to add plex and spotify access. But when settign up the acces from HA I get redirected and then directed back which then throws an error that the site cant be reached. So I click authorize in HA, I get redirected to a plex login-page and after logging in plex redirects me to: http://10.65.249.194:8123/auth/plex/callback?flow_id=ba59d3dc2bf342b681c1e541f79710fb Which I guess is a internal docker ip adress. Same thing happens with spotify. How can I fix this?

I am using a Asus TUF x570-Plus motherboard and am trying to pass two separate USB controllers into two separate VM's After reading several posts on the forum I have placed the Unraid usb on the 0b:00.3 USB controller. I have also passed 06:00.0, 06:00.1, and 06:00.3 controllers using the VIFO-PCI plugin. My Windows 10 VM is using 06:00.1 and it works perfectly. But I have not got my other VM's to be able to use the 06:00.3 controller as nothing happens when I plug anything in the ports. When looking in the log for the other VM I get this: 2020-03-11T16:02:11.664422Z qemu-system-x86_64: vfio: Cannot reset device 0000:06:00.0, depends on group 27 which is not owned.

Is there any USB PCIe x1 card that have multiple usb controllers ? So that I can add one card but passthrough two groups of usb slots to two different VM's ? I have only found the Sonnet "Allegro Pro USB 3.0" that have multiple controllers and works in unraid. But it is PCIe x4

I am using a Asus tuf x570-plus motherboard but the IOMMU-groups seams to be identical. After reading the whole thread I have placed the unraid usb on the 0b:00.3 USB controller. I have also passed 06:00.1, and 06:00.3 controllers using the VIFO-PCI plugin. My Windows 10 VM is using 06:00.1 and it works perfectly. But I have not got my other VM's to be able to use the 06:00.3 controller as nothing happens when I plug anything in the ports. I am not sure which ports is connected to 06:00.3 but I have tried all ports on my unraid server. Or is it connected to the single USB-C connector ? Do I also need to pass through: Group 26 06:00.0 1022:1485 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP Edit: passing through Group 26 did not change anything. When looking in the log for the other VM I get this: 2020-03-11T16:02:11.664422Z qemu-system-x86_64: vfio: Cannot reset device 0000:06:00.0, depends on group 27 which is not owned.

Is there some way to add a USB-Switch to unraid so that I can use the same keyboard/mouse to all my VM's ? I tried connecting the keyboard/mouse to my switch and just plugged it in and it worked directly my WIN 10 VM. But as soon as I switched input the VM froze and I had to reboot my entire server to get it running again.

Removing the ipv6 from the config-file made no difference. When I flip the inactive-button to active it resets after clicking "done"

Thanks, for the answer. Another stupid question: Is it possible to only route specific containers through wireguard? Rigth now I only have the need for ruTorrent to use wireguard.

Can I use a Radeon RX 550 to run Catalina ?

Can anyone tell me what I am doing wrong ? I signed up with an VPN-service that offers wireguard (mullvad.net) and downloaded the config.file and imported it. But wireguard does not connect.

I was playing around with wireguard and made some error so that I lost access to the unraid server. I also had the option for wireguard to autostart enabled. How can I disable wireguard from the unraid boot prompt?

Ok I created a new VM template with exactly the same info but I also used a vBios dump that I created my self. And now it works.

I just managed to get a Windows 10 VM running and have pass through both gpu and gpu audio. But when windows starts there is a red cross on the audio-icon in the lower right. I also tried using VIFO-PCI plugin and selected the gpu+audio but that made no difference and I have tried running the MSI-util and selected the gpu there to. In device manager I only have "NVIDIA Virtual Audio Device (Wave Extensible) (WDM)" under sound controllers. My system: Ryzen 3900X x570 Motherboard Nvidia GTX 1060 6GB log-file: -overcommit mem-lock=off \ -smp 8,sockets=1,cores=8,threads=1 \ -uuid c5d62b79-62ba-c55a-208f-56ef96d4feb9 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=32,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x9,chassis=1,id=pci.1,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xb,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0x8,chassis=5,id=pci.5,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0xc,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x4 \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.173-2.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.1,drive=libvirt-1-format,id=sata0-0-1 \ -netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e3:ce:1c,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -device vfio-pci,host=0000:04:00.0,id=hostdev0,bus=pci.3,addr=0x0 \ -device vfio-pci,host=0000:04:00.1,id=hostdev1,bus=pci.4,addr=0x0 \ -device vfio-pci,host=0000:03:00.0,id=hostdev2,bus=pci.5,addr=0x0 \ -device usb-host,hostbus=5,hostaddr=2,id=hostdev3,bus=usb.0,port=2 \ -device usb-host,hostbus=5,hostaddr=3,id=hostdev4,bus=usb.0,port=3 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-02-29 12:10:05.348+0000: Domain id=1 is tainted: high-privileges 2020-02-29 12:10:05.348+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) -overcommit mem-lock=off \ -smp 8,sockets=1,cores=8,threads=1 \ -uuid c5d62b79-62ba-c55a-208f-56ef96d4feb9 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=32,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x9,chassis=1,id=pci.1,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xb,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0x8,chassis=5,id=pci.5,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0xc,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x4 \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.173-2.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.1,drive=libvirt-1-format,id=sata0-0-1 \ -netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e3:ce:1c,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -device vfio-pci,host=0000:04:00.0,id=hostdev0,bus=pci.3,addr=0x0 \ -device vfio-pci,host=0000:04:00.1,id=hostdev1,bus=pci.4,addr=0x0 \ -device vfio-pci,host=0000:03:00.0,id=hostdev2,bus=pci.5,addr=0x0 \ -device usb-host,hostbus=5,hostaddr=2,id=hostdev3,bus=usb.0,port=2 \ -device usb-host,hostbus=5,hostaddr=3,id=hostdev4,bus=usb.0,port=3 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-02-29 12:10:05.348+0000: Domain id=1 is tainted: high-privileges 2020-02-29 12:10:05.348+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 10</name> <uuid>c5d62b79-62ba-c55a-208f-56ef96d4feb9</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='5'/> <vcpupin vcpu='1' cpuset='17'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='19'/> <vcpupin vcpu='4' cpuset='9'/> <vcpupin vcpu='5' cpuset='21'/> <vcpupin vcpu='6' cpuset='11'/> <vcpupin vcpu='7' cpuset='23'/> </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/c5d62b79-62ba-c55a-208f-56ef96d4feb9_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </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'> <topology sockets='1' cores='8' threads='1'/> </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.173-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <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> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x9'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0xa'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xb'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </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='0xc'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </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='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <interface type='bridge'> <mac address='52:54:00:e3:ce:1c'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <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='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x04' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <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='0x03' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc318'/> <address bus='5' device='2'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='5' device='3'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

I am at work right now, but I just added the line from the unraid gui in the main/flash/syslinux and added it to the default unraid-section. Last thing I tried before work was to change in bios to boot from uefi and also added the gpu/audio in the VFIO-PCI plugin. During the reboot some unraid info was showing but it never displayed the ip and prompt which is the last thing in the bootup so maybe the "video=efifb:off" worked now. But the monitor was still on and displayed some info. I could still enter the web-ui, and when trying to create a new VM with the gpu/audio/NVMe I got an error-message on start that indicated that the vBios (asus1060.dump )could not be found. I had before just added it using xml but when I tried using the menu I could navigate through folders but the vbios-file never shows when selecting the correct folder. I also tried moving the file to different folders but I could not get the file to show in any of the folders. Is that normal?

I have ordered a new secondary gpu to try to get any progress. But while waiting I noticed some posts saying that I must add "video=efifb:off" to syslinux to be able to use the primary gpu in a VM. But even when adding that line to syslinux I still get the Unraid bootup displaying which I guess should not happen