KeyBoardDabbler
Members-
Posts
62 -
Joined
-
Last visited
Converted
-
Gender
Male
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
KeyBoardDabbler's Achievements
-
Ahh this explains the need for a rule allowing port 53 traffic from VLAN80 to LAN for the containers to function properly.
-
KeyBoardDabbler started following Drive failure? (write error) and DNS resolution
-
I'm hoping someone can help me because I feel I am seriously missing the concept of DNS and what I am trying to achieve. Short version I have a VLAN80 network for the dedicated game servers containers I am hosting on unraid, this network has restricted access to the rest of the network, quite standard. In opnsense i have set networks to use different DNS servers set via the DHCP settings for the related network. For some reason that i do not understand VLAN80 needs a rule to allow 53 to LAN. I suspect unraid Containers use host’s DNS settings? Long version I read that using the same DNS servers for each network could expose the internal network structure. So with that in mind, I have configured VLAN80 to use Cloudflare as an external DNS resolver. To clarify SYSTEM: SETTINGS: GENERAL: DNS servers = 9.9.9.9, 149.112.112.112 SERVICES: DHCPV4: [VLAN80_DMZ]: DNS servers = 1.1.1.1, 1.0.0.1 Services: Unbound DNS: General Network Interfaces = LAN Outgoing Network Interfaces = WAN Using `dig` devices on LAN use the default DNS. Using `dig` devices on VLAN80 use the CloudFlare DNS. Devices on VLAN80 have internet access but can't access LAN network. Devices on VLAN80 are assigned the correct IP, I.e. 10.0.80.23 Here is the problem unraid containers using the bond0.80 network (VLAN80) do not have internet ` # docker run --rm --network bond0.80 busybox nslookup www.google.com ;; connection timed out; no servers could be reached` Starting the game server containers fail to load, and using packet capture I can see requests to LAN port 53. ethertype IPv4 (0x0800), length 79: (tos 0x0, ttl 64, id 11339, offset 0, flags [DF], proto UDP (17), length 65) 10.0.80.25.59421 > 192.168.1.1.53: [udp sum ok] 6081+ A? cdn.steamstatic.com. (37) ethertype IPv4 (0x0800), length 79: (tos 0x0, ttl 64, id 16259, offset 0, flags [DF], proto UDP (17), length 65) 10.0.80.25.49361 > 192.168.1.1.53: [udp sum ok] 6081+ A? cdn.steamstatic.com. (37) So I created an `Allow Port 53 from VLAN80 net to Lan net`. Sure enough the game server containers start up. Why is it needing access to LAN, going back to the start wasn't the point to not expose the internal network?
-
[Support] ich777 - Gameserver Dockers
KeyBoardDabbler replied to ich777's topic in Docker Containers
Below is the link to the reddit discussion if anyone wants to take a read of the extra info. optimizing Palworld -
I followed your suggestion and ran the extended SMART test on both effected drives, reported no errors found and disks still are still down. I dont realy understand the error log file for the pool device because there is a error but it states the test completed with 0 errors. Disk 11 (disabled, contents emulated) SMART self-test history: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 46186 - # 2 Extended offline Completed without error 00% 29232 - SMART error log: No Errors Logged Pool device (1 smart error) SMART self-test history: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 23636 - SMART error log: ATA Error Count: 2 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 2 occurred at disk power-on lifetime: 23612 hours (983 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 c8 18 08 04 Error: UNC at LBA = 0x040818c8 = 67639496 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 48 e0 35 08 44 00 4d+09:58:45.407 READ FPDMA QUEUED 60 00 a0 00 34 08 44 00 4d+09:58:45.407 READ FPDMA QUEUED 60 00 40 98 33 08 44 00 4d+09:58:45.407 READ FPDMA QUEUED 60 00 10 08 32 08 44 00 4d+09:58:45.407 READ FPDMA QUEUED 60 00 40 58 31 08 44 00 4d+09:58:45.407 READ FPDMA QUEUED Error 1 occurred at disk power-on lifetime: 23608 hours (983 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 b8 18 08 04 Error: UNC at LBA = 0x040818b8 = 67639480 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 e0 3f 08 44 00 4d+05:58:54.385 READ FPDMA QUEUED 60 00 00 e0 35 08 44 00 4d+05:58:54.384 READ FPDMA QUEUED 60 00 00 e0 2b 08 44 00 4d+05:58:54.382 READ FPDMA QUEUED 60 00 00 e0 21 08 44 00 4d+05:58:54.382 READ FPDMA QUEUED 60 00 a8 38 1f 08 44 00 4d+05:58:48.725 READ FPDMA QUEUED
-
Hi guys, Can someone with more experience spare a moment to look at my diagnostics file. I came home today and have noticed `Disk 11` is being emulated and various errors in the log file. Has this drive failed or should I look at maybe the sata cable first? If the drive has failed, would I need to replace the drive or is it possible to remove disk 11 from the array and rebuild the missing data into existing drives as i have plenty of extra storage. Also i just noticed that a pool device is also reporting a smart error `Reported uncorrect` ? holy-grail-diagnostics-20230823-1539.zip
-
Guide: How To Use Rclone To Mount Cloud Drives And Play Files
KeyBoardDabbler replied to DZMM's topic in Plugins and Apps
I just tried running the below command, it did copy the correct files from the shared drive to my local directory but the folder/ file names are now obscured in the local folder. Is it possible to remove the crypt on copy? #!/bin/bash # Relocate moviesclasic > local rclone copy tdrivesportsppv:crypt/6uub5b0iurd8j74m2dddn77dcs /mnt/user0/sports-ppv \ --user-agent="transfer" \ -vv \ --buffer-size 512M \ --drive-chunk-size 512M \ --tpslimit 8 \ --checkers 8 \ --transfers 4 \ --order-by modtime,ascending \ --exclude *fuse_hidden* \ --exclude *_HIDDEN \ --exclude .recycle** \ --exclude .Recycle.Bin/** \ --exclude *.backup~* \ --exclude *.partial~* \ --drive-stop-on-upload-limit exit I tried the built in file explorer via the unraid webui and copied some files from "/mnt/user/mount_rclone/tdrive_sports_ppv_vfs/sports_ppv" to "/mnt/user0/sports-ppv". This worked as expected but i dont think this is the best method to transfer large folder. -
Guide: How To Use Rclone To Mount Cloud Drives And Play Files
KeyBoardDabbler replied to DZMM's topic in Plugins and Apps
So i have also recently received the email notice that my drive will change to read only due to being over the storage limit. It has been a great service over the last few years considering the cost, but i knew this day would come. Luckily i have been building up my local storage in this time. What is the best way for me to start copying files from gdrive to local storage. Should i just use rsync and copy from the rclone mounts to the relevant local folder. Thanks -
Hi all, I have two identical servers but recently having issues with 1 of them. Now i am not sure if this is unraid related or something that happened after upgrading the network card in my opnsense firewall. Upon rebooting all systems i noticed i did not have access to all of the services hosted on server 2 through HAProxy on opnsense. I can access everything hosted on server 1 just fine. One thing i noticed is when opening the docker containers webui through unraid it loads the wrong local ip address (192.168.1.105). Normally in Settings > Network Settings > IPv4 address assignment: Static 192.168.1.104. I tried changing this to automatic and opnsense assigned a new lease, I then set the static mapping in opnsense to 192.168.1.104 and surly enough i can access unraid webui but same issue persists when accessing the docker containers. I confirmed the container xml file is set correctly to WebUI: http://[IP]:[PORT:8096]/ but it still opens at .105 even when unraid is running on .104. I also tried stop/ starting docker and rebooting. Lastly to confirm it is unraid related i manually set the above webui parameter to the actual local ip (.104) and i was able to access the service through the HAProxy as expected. holy-grail-diagnostics-20230731-2136.zip
-
6.12.0 System hangs on boot after update
KeyBoardDabbler replied to elephantintheroom's topic in General Support
I found myself in the same situation, updated the gigabyte motherboard bios over the weekend and was unable to boot unraid. Deleted the vfio-pci.cfg file and I was back in action. While I do not host any VM, I did previously bind the 2x gpu's in my system so it's good to know that hardware IDs can change -
System wont boot after update [6.12.2 > 6.12.3]
KeyBoardDabbler replied to KeyBoardDabbler's topic in General Support
thankyou cYnIx for pointing me in the right direction. I found the solution in the below post. It was the vfio-pci.cfg which prevented the OS from loading. It makes sense because i have an identical server minus the GPU's which updated with no issues. -
System wont boot after update [6.12.2 > 6.12.3]
KeyBoardDabbler replied to KeyBoardDabbler's topic in General Support
It looks like the only diagnostic zips available are the ones that I have generated in the past. Thankyou for the suggestions, this is why I wanted guidance because I am not sure which files are safe to try this with without messing something up. I will try this later No not atall, I will try rolling back the version. My only concern is that I made a backup before rebooting the server, this was after clicking update in the webui. I guess I can use the create tool and build 6.12.2 and try copying my config folder across or will this not work due to being taken after the update. I will have a backup of the flash drive but it will be store on the nvme drive in the server 🤦 -
I was running on version 6.12.2, i confirmed all plugins are upto date and stopped all running containers. I proceeded to update to 6.12.3, I got the notification stating it was okay to now reboot, before doing so i took a copy of the flash drive. My system goes past the bios screen and motherboard displays FF which is normal when unraid starts but the monitor stays active and only displays black. I have left it on multiple occasion like this for a period of time but the system does not go any further. After searching the forum i then tried the following. In case of corruption, reformatted the usb using the unraid create tool and transferred the config folder from backup across. Same issue. With a brand new usb drive, using the unraid create tool on version 6.12.3 and transferred the config folder from backup across. Same issue. With the new usb i used unraid create tool once again and build version 6.12.3 but this time i did not copy across my config folder. System booted and i monitor loaded login prompt. I was able to access the webui login page via local network. The above has identified it not hardware related but a issue with my config folder? I also read that majority of the time when unraid does not boot its due to a installed plugin and to boot in safe mode. I can not do this due to the black screen (monitor is active though, blue not amber led) Following the guidance in the above link i tried editing the file syslinux/syslinux.cfg that controls the boot menu on the USB drive and move the 'default' entry to the section for Safe boot but the same issue persists and i cant boot the OS. Can someone please help with how i should proceed next. FLASH: scandisk cruzer fit 8GB CPU: i9-10900 MB: z590 aorus master RAM: 96GB DDR4 3200mhz GPU: GTX-1060 mini GPU: GTX-1060 mini
-
[Guide] InvokeAI: A Stable Diffusion Toolkit - Docker
KeyBoardDabbler replied to mickr777's topic in Docker Containers
Thankyou for making this container available. Only one of my gpu cards seem to be utilized. InvokeAI maxs out the load on the same gpu each time. Both cards are showing in the system device menu, both cards show within the nvidia drivers plugin and I have the container ExtraParams --gpus all. I there a way to test this? I am currently running; unraid: 6.12.rc3 invokeai: v2.3 image -
Code 43 with GPU passthrough on my Windows 11 VM
KeyBoardDabbler replied to aymanibousi's topic in VM Engine (KVM)
thankyou for your input. Honestly I will just pass on playing this game as I don't wont to risk being banned. I imagine that would bring more problems -
Code 43 with GPU passthrough on my Windows 11 VM
KeyBoardDabbler replied to aymanibousi's topic in VM Engine (KVM)
Sorry to jump in here but I am hoping you may have an idea to resolve a error code 43 I am dealing with. I have a working Win 10 VM, GPU passed through and audio also working. However a new game has been released but the Easy Anti Cheat throws up a error that the game cant be played on a virtual machine. I followed the steps marked here but this is when my GPU stops working. My monitors stay in standby, so I remote desktop into the VM and noticed in device manager that windows has disabled my GPU because of error code 43. I tried running the game while connected through RD and the changes fixed the EAC error but disabled the GPU. Working XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='6'> <name>Windows 10</name> <uuid>fc7761e9-0522-d29b-f2b5-5ab5feb145de</uuid> <description>Graeme PC</description> <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'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='15'/> <vcpupin vcpu='8' cpuset='6'/> <vcpupin vcpu='9' cpuset='16'/> <vcpupin vcpu='10' cpuset='7'/> <vcpupin vcpu='11' cpuset='17'/> <vcpupin vcpu='12' cpuset='8'/> <vcpupin vcpu='13' cpuset='18'/> <vcpupin vcpu='14' cpuset='9'/> <vcpupin vcpu='15' cpuset='19'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/fc7761e9-0522-d29b-f2b5-5ab5feb145de_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> </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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/My PC/vdisk1.img' index='4'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/S6P7NJ0T307369R/My PC/vdisk2.img' index='3'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <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/Windows 10.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.221-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='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='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <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:df:3c:d1'/> <source bridge='br0'/> <target dev='vnet5'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' 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-6-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> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/gtx1060-6gb.rom'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0046'/> <address bus='1' device='6'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0221'/> <address bus='1' device='10'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0529'/> <address bus='1' device='11'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0c00'/> <address bus='1' device='8'/> </source> <alias name='hostdev5'/> <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> Not working (error 43) with the changes made to get around the EAC error <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='6'> <name>Windows 10</name> <uuid>fc7761e9-0522-d29b-f2b5-5ab5feb145de</uuid> <description>Graeme PC</description> <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'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='15'/> <vcpupin vcpu='8' cpuset='6'/> <vcpupin vcpu='9' cpuset='16'/> <vcpupin vcpu='10' cpuset='7'/> <vcpupin vcpu='11' cpuset='17'/> <vcpupin vcpu='12' cpuset='8'/> <vcpupin vcpu='13' cpuset='18'/> <vcpupin vcpu='14' cpuset='9'/> <vcpupin vcpu='15' cpuset='19'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/fc7761e9-0522-d29b-f2b5-5ab5feb145de_VARS-pure-efi.fd</nvram> <smbios mode='host'/> </os> <features> <acpi/> <apic/> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> <feature policy='disable' name='hypervisor'/> </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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/My PC/vdisk1.img' index='4'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/S6P7NJ0T307369R/My PC/vdisk2.img' index='3'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <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/Windows 10.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.221-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='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='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <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:df:3c:d1'/> <source bridge='br0'/> <target dev='vnet5'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' 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-6-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> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/gtx1060-6gb.rom'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0046'/> <address bus='1' device='6'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0221'/> <address bus='1' device='10'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0529'/> <address bus='1' device='11'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0c00'/> <address bus='1' device='8'/> </source> <alias name='hostdev5'/> <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>