January 16, 20224 yr Hi everyone, I am loosing the will to live with UnRAID VMs as I have run out of ideas! Created a new Windows 11 VM and everything worked fine, until I needed to reboot and now I cannot get it to boot at all! What am I doing wrong? VM XML: Quote <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 11</name> <uuid>fd34370c-6e4f-cd0b-55a1-2fa823b2ff7e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows.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='4'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.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/fd34370c-6e4f-cd0b-55a1-2fa823b2ff7e_VARS-pure-efi-tpm.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='4' threads='2'/> <cache mode='passthrough'/> </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='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/Windows 11/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows/Win11_English_x64v1.iso' index='2'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <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.208-1.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='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='0x8'/> <alias name='pci.1'/> <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'/> <alias name='pci.2'/> <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'/> <alias name='pci.3'/> <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'/> <alias name='pci.4'/> <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'/> <alias name='pci.5'/> <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'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </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='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:c4:05:be'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' 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 11/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='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='2'/> </source> <alias name='hostdev0'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </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='0x03' slot='0x00' function='0x1'/> </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='0x00' slot='0x17' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x01' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x07f8'/> <address bus='1' device='6'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0x0809'/> <address bus='1' device='3'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc05b'/> <address bus='1' device='9'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x8087'/> <product id='0x0029'/> <address bus='1' device='10'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='5'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> VM Error In UnRAID: Quote ErrorWarningSystemArrayLogin 2022-01-16T23:02:16.831862Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88376, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831869Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88377, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831876Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88378, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831883Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88379, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831893Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837a, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831903Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837b, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831912Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837c, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831926Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837d, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831936Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837e, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831945Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837f, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831953Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88380, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831961Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88381, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831967Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88382, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831975Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88383, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831982Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88384, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831989Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88385, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831996Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88386, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832003Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88387, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832011Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88388, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832018Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88389, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832027Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838a, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832037Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838b, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832046Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838c, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832053Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838d, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832061Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838e, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832068Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838f, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832076Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88390, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832083Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88391, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832089Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88392, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832097Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88393, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832104Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88394, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832111Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88395, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832119Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88396, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832126Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88397, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832133Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88398, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832140Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88399, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832149Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839a, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832160Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839b, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832168Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839c, 0x0,1) failed: Device or resource busy See images and diagnostics attached. I've tried to split my IOMMU groups, by following @SpaceInvaderOne's guide, but after the reboot, they are all still grouped together? Any ideas? Have I selected the wrong things, causing it to crash? ###-diagnostics-20220116-2341.zip
January 16, 20224 yr Author This is what loads on screen since my reboot: Sent from my TA-1012 using Tapatalk Edited January 16, 20224 yr by Rick Sanchez
January 16, 20224 yr Author Quote 2022-01-16T23:02:16.831862Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88376, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831869Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88377, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831876Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88378, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831883Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88379, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831893Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837a, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831903Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837b, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831912Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837c, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831926Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837d, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831936Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837e, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831945Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837f, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831953Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88380, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831961Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88381, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831967Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88382, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831975Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88383, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831982Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88384, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831989Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88385, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.831996Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88386, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832003Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88387, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832011Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88388, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832018Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88389, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832027Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838a, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832037Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838b, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832046Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838c, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832053Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838d, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832061Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838e, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832068Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838f, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832076Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88390, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832083Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88391, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832089Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88392, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832097Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88393, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832104Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88394, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832111Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88395, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832119Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88396, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832126Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88397, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832133Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88398, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832140Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88399, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832149Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839a, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832160Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839b, 0x0,1) failed: Device or resource busy 2022-01-16T23:02:16.832168Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839c, 0x0,1) failed: Device or resource busy Has anyone got a solution to my problems? Thanks for your help! Edited January 17, 20224 yr by Rick Sanchez
January 17, 20224 yr Try that or the solution from whole thread " Thanks for getting back. I got it working. I uninstalled the AMD Vendor Reset plugin from UnRaid. I disabled `Resizable BAR` and `Above 4G memory/Crypto Currency mining` in my MSI x570 Tomahawk Wifi and everything fell into place. Wow..took me 8 hours 😞 "
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.