dubbly

Members
  • Posts

    95
  • Joined

  • Last visited

Everything posted by dubbly

  1. Struggling to figure out what is causing this problem. I added a drive as my array and cache were full. Everything looked good but when I start the dockers I get the following repeating error in the logs. However, when I turn off the docker service it goes away. Looking for assistance regarding how to diagnose the issue and resolve. Thank you Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: [ 6] BadTLP Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: [ 6] BadTLP Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: [ 6] BadTLP Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: [ 6] BadTLP Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: [ 6] BadTLP Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:17 tower kernel: pcieport 0000:00:01.3: [ 6] BadTLP Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:17 tower kernel: pcieport 0000:00:03.1: [ 6] BadTLP Jul 18 11:06:18 tower kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:18 tower kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:18 tower kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:18 tower kernel: pcieport 0000:00:01.3: [ 6] BadTLP Jul 18 11:06:18 tower kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:18 tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:18 tower kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00000040/00006000 Jul 18 11:06:18 tower kernel: pcieport 0000:00:03.1: [ 6] BadTLP Jul 18 11:06:18 tower kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0 Jul 18 11:06:18 tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jul 18 11:06:18 tower kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00000040/00006000
  2. So, for the last 3 or 4 parity checks (even ones that I initiate manually) I constantly get 2-8 errors. I haven’t been able to figure out what is causing it. I have my server on a UPC and haven’t had any power outages. So, it isn’t likely an unclean shutdown. Attached diagnostics and sever logs. Last parity check information and time below. Thank you for your assistance. Unraid Parity check: 10-06-2020 13:41 Notice [TOWER] - Parity check finished (2 errors) Duration: 18 hours, 23 seconds. Average speed: 123.4 MB/s tower-syslog-20200614-1810.zip tower-diagnostics-20200614-1110.zip
  3. It isn’t possible to play with with the Switch or Xbox One remotely to a custom server nativity. There is a beta Docker (I forget the name) to trick an Xbox to do This. Not sure if it will work for a switch.
  4. Questions: 1. How can I make sure that I completely remove everything from a docker that I have installed? I installed Marina DB and want to uninstall, delete everything, including databases and start over. 2. Is there a simple (one step or two step) way to remove all old containers, templates and data for dockers that I no longer use?
  5. I have screwed up my database while messing around and deleted mysql.db. Not a big deal because I am trying to learn about databases. Question, can someone walk me through the steps of completely deleting everything and starting over please!
  6. Goal: Connect to networks so that an Xbox at another location can see (as if it was on the same LAN) my unraid Minecraft server. Issue: The Xbox One version of Minecraft can only seen servers run by individuals on the same LAN. Not via entering a remote server address. Our extended family member only has the Xbox version of Minecraft Current Setup: Both locations have there own unraid server with wireguard setup so that I can initiate wireguard from a phone or a PC on both. However, I can't seem to figure out how to set-it up so that: 1. the two unraid servers connect directly and setup as one LAN 2. the remote Xbox can see the Minecraft server as if it were on the LAN. Does it need to be on the same IP domain?
  7. Thank you everyone. I have successfully added a Texture Pack. Question: Is it possible to add skin packs?
  8. I am currently having difficulty passing through a Fresco Logic FL1100 USB 3.0 Host Controller (rev 10). Tried a number of methods pass it through including the VIFO plugin. Originally, posted detailed info in the VM (KVM) forum but haven't received a response in a week. Realize that it might be in the wrong place. Suggestions are be apricated!
  9. I have a working VM that functions just fine with VNC and GPU passthrough. However, I added a fresco Logic USB 3.0 controller by following SpaceInvader One's instructions. After selecting the fresco logic and starting the VM it reports 'No bootable device'. I remove the controller and all is good again. Below are my settings and things that I have tried. Flash drive: tried both pci-stub.ids=1b73:1100 and vfio-pic.ids=1b73:1100 Also tried the VFIO plugin blow are my settings i am trying to pass through IOMMU group 21. Could this because the even though the groups are separate the internal hubs used by each group appear to be shared: For Example: The same Root Hub and other Hubs appear in all of the USB seperate groups. IOMMU Groups ----- IOMMU group 0: [8086:191f] 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) IOMMU group 1: [8086:1901] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) IOMMU group 2: [8086:1912] 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) IOMMU group 3: [8086:a12f] 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) [8086:a131] 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) IOMMU group 4: [8086:a13a] 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) IOMMU group 5: [8086:a102] 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31) IOMMU group 6: [8086:a110] 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) IOMMU group 7: [8086:a111] 00:1c.1 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #2 (rev f1) IOMMU group 8: [8086:a112] 00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) IOMMU group 9: [8086:a145] 00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31) [8086:a121] 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) [8086:a170] 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) [8086:a123] 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) IOMMU group 10: [8086:15b8] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) IOMMU group 11: [1002:675d] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] [1002:aa90] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] IOMMU group 12: [1b21:1242] 03:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller IOMMU group 13: [1b21:1187] 04:00.0 PCI bridge: ASMedia Technology Inc. Device 1187 IOMMU group 14: [1b21:1187] 05:01.0 PCI bridge: ASMedia Technology Inc. Device 1187 IOMMU group 15: [1b21:1187] 05:04.0 PCI bridge: ASMedia Technology Inc. Device 1187 IOMMU group 16: [1b21:1187] 05:05.0 PCI bridge: ASMedia Technology Inc. Device 1187 IOMMU group 17: [1b21:1187] 05:06.0 PCI bridge: ASMedia Technology Inc. Device 1187 IOMMU group 18: [1b21:1187] 05:07.0 PCI bridge: ASMedia Technology Inc. Device 1187 IOMMU group 19: [1b21:0612] 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) IOMMU group 20: [1b21:0612] 09:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) IOMMU group 21: [1b73:1100] 0a:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) ----- USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1b1c:0c08 Corsair H80i v2 Bus 001 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 001 Device 004: ID 045e:0024 Microsoft Corp. Trackball Explorer Bus 001 Device 005: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 001 Device 006: ID 0c45:5011 Microdia USB Wired Keyboard Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append pci-stub.ids=1b73:1100 pcie_acs_override=downstreamn initrd=/bzroot label Unraid OS GUI Mode kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest VM XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Q35 Windows 10</name> <uuid>907821d3-7a46-5118-14d8-db23690dd00f</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> </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='2' 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='raw' cache='writeback'/> <source file='/mnt/user/domains/Q35 Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows 10 19H2/Windows 10 19H2.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <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.173-2.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <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'/> <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'/> <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'/> <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'/> <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'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:b1:f9:04'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' 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> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> Thank you!
  10. Thank you all. For this discussion regarding moding worlds and textures. If anyone has any suggestions for where to find some bedrock worlds and packs for 1.14.60 that would be great. the peegs mod sounds cool.
  11. Thank you. The instructions above worked perfectly! Skin Packs: Is it possible to add skin packs to the server using the same instructions to add textures? Or, do skin packs have to be installed by each individual separately?
  12. Ahh... I somehow missed your post about the floppy! I read it and also found the following which was the key. I followed the instructions and blam! Thank you so much for your suggestion. It was key.
  13. Did you ever figure this issue out? I am stuck at this spot as well.
  14. For some reason I am not able to find a way to open an load the drivers in XP setup. Pressing F6 should work as shown in the image above. However, no options exist to load drivers when I press S. I wonder if I need to add a virtual floppy drive.
  15. Ohhh... I have always started with the spaceinvader one's videos. Good suggestion on the docs! Reading now.
  16. Q35 didn't solve the problem However, pressing F6 while loading brought up the following screen (see image). It seems that it can't find a mass storage device to save to. At least that is how I read it. Pressing S resulted in no additional drivers found. I wasn't able to see a way to load the drivers. This seems like progress. Suggestions?
  17. I can try Q35. Yes, there is an opportunity to load drivers. I am just not sure what to load. I will see if I can show a screen shot of the options. Thanks
  18. Thank you for the suggestion. Just tried reducing to a single core and experienced the same issue. Any other ideas?
  19. Made some progress based on assistance from rachid596 and also gareth_iowc. The XP VM now appears to boot the ISO and begin installing. However, I now get a blue screen right when it says "starting windows," see the image below. After the blue screen I need to force quit the VM. Then it WILL NOT boot/install again. In that see is "booting from HDD" with no action. I can destroy the VM and setup new and end up in the same loop. Screen shots and config file below. I wonder if my XP SP3 ISO is somehow corrupted or the HDD doesn't function. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows XP</name> <uuid>557a0dec-0d49-bffd-94f1-3b3910ced0b5</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows XP" icon="windowsxp.png" os="windowsxp"/> </metadata> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='6'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> </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='2' 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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows XP/en_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-73974.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <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.160-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <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/user/domains/Windows XP/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:45:e7:cd'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> This is just before the blue screen: Blue Screen: This is what I see if I restart after the blue screen.
  20. Setting up a second minecraft server? Thank you so much for this wonderful docker. It has made my family and friends time at home during the shut down much more enjoyable! I would like to setup a second server on the same unraid box to try to explore texture pack /add-ins. Looking for guidance on how to setup a second server and without creating conflicts.
  21. I have some old windows XP based music software and files that I created a long time ago. They won't run on windows 7. So, I am trying to get an XP VM based on a Windows XP SP3 to run but am struggling. I have tried a number of virtIO drivers and but every time it halts at "Booting from hard drive" and pegs a single cpu at 100% until force shut down. Suggestions and help is appreciated. Logs and Images below:
  22. I deleted my domains share a few years ago because I wasn't using VM. I am now interested in exploring a VM. Can i just create a share called domains? Or, do I need to do something else? What settings should I use? For example, should domains be on the cache drive?
  23. Thank you for thIs discussion about addon and instruction. Suggestions for add-ons to try on the latest bedrock is appreciated.