Holmesware

Thanks, but I don't have any containers running with an IP address on this server. I did in the past and it settled down when I stopped everything and just used this unit as a file share. I have Pi-Hole running on other unRAID server with an IP and it's fine though. I'll keep digging on this and post what I find. EDIT: Captured the error. I believe this is what your talking about. I've disabled docker on this server. Jul 26 09:41:39 BrewMaster kernel: ------------[ cut here ]------------ Jul 26 09:41:39 BrewMaster kernel: WARNING: CPU: 5 PID: 96 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Jul 26 09:41:39 BrewMaster kernel: Modules linked in: macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding igb i2c_algo_bit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mpt3sas rapl intel_cstate intel_uncore raid_class i2c_i801 nvme scsi_transport_sas i2c_smbus input_leds nvme_core ahci i2c_core led_class acpi_power_meter intel_pch_thermal libahci video ie31200_edac backlight thermal acpi_ipmi button acpi_pad fan ipmi_si [last unloaded: i2c_algo_bit] Jul 26 09:41:39 BrewMaster kernel: CPU: 5 PID: 96 Comm: kworker/5:1 Tainted: P O 5.10.28-Unraid #1 Jul 26 09:41:39 BrewMaster kernel: Hardware name: Supermicro Super Server/X11SSH-LN4F, BIOS 2.5 11/26/2020 Jul 26 09:41:39 BrewMaster kernel: Workqueue: events macvlan_process_broadcast [macvlan] Jul 26 09:41:39 BrewMaster kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Jul 26 09:41:39 BrewMaster kernel: Code: e8 dc f8 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 36 f6 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 6d f3 ff ff e8 35 f5 ff ff e9 22 01 Jul 26 09:41:39 BrewMaster kernel: RSP: 0018:ffffc900001bcd38 EFLAGS: 00010202 Jul 26 09:41:39 BrewMaster kernel: RAX: 0000000000000188 RBX: 0000000000005bdd RCX: 00000000c250a2bb Jul 26 09:41:39 BrewMaster kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffa032e174 Jul 26 09:41:39 BrewMaster kernel: RBP: ffff88815f3c52c0 R08: 000000005796f9da R09: ffff888156c4cb60 Jul 26 09:41:39 BrewMaster kernel: R10: 0000000000000000 R11: ffff8881011b7b00 R12: 00000000000031eb Jul 26 09:41:39 BrewMaster kernel: R13: ffffffff8210b440 R14: 0000000000005bdd R15: 0000000000000000 Jul 26 09:41:39 BrewMaster kernel: FS: 0000000000000000(0000) GS:ffff889037b40000(0000) knlGS:0000000000000000 Jul 26 09:41:39 BrewMaster kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 09:41:39 BrewMaster kernel: CR2: 000014ed89d89000 CR3: 000000000200a003 CR4: 00000000003706e0 Jul 26 09:41:39 BrewMaster kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 26 09:41:39 BrewMaster kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 26 09:41:39 BrewMaster kernel: Call Trace: Jul 26 09:41:39 BrewMaster kernel: <IRQ> Jul 26 09:41:39 BrewMaster kernel: nf_conntrack_confirm+0x2f/0x36 [nf_conntrack] Jul 26 09:41:39 BrewMaster kernel: nf_hook_slow+0x39/0x8e Jul 26 09:41:39 BrewMaster kernel: nf_hook.constprop.0+0xb1/0xd8 Jul 26 09:41:39 BrewMaster kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe Jul 26 09:41:39 BrewMaster kernel: ip_local_deliver+0x49/0x75 Jul 26 09:41:39 BrewMaster kernel: ip_sabotage_in+0x43/0x4d [br_netfilter] Jul 26 09:41:39 BrewMaster kernel: nf_hook_slow+0x39/0x8e Jul 26 09:41:39 BrewMaster kernel: nf_hook.constprop.0+0xb1/0xd8 Jul 26 09:41:39 BrewMaster kernel: ? l3mdev_l3_rcv.constprop.0+0x50/0x50 Jul 26 09:41:39 BrewMaster kernel: ip_rcv+0x41/0x61 Jul 26 09:41:39 BrewMaster kernel: __netif_receive_skb_one_core+0x74/0x95 Jul 26 09:41:39 BrewMaster kernel: process_backlog+0xa3/0x13b Jul 26 09:41:39 BrewMaster kernel: net_rx_action+0xf4/0x29d Jul 26 09:41:39 BrewMaster kernel: __do_softirq+0xc4/0x1c2 Jul 26 09:41:39 BrewMaster kernel: asm_call_irq_on_stack+0x12/0x20 Jul 26 09:41:39 BrewMaster kernel: </IRQ> Jul 26 09:41:39 BrewMaster kernel: do_softirq_own_stack+0x2c/0x39 Jul 26 09:41:39 BrewMaster kernel: do_softirq+0x3a/0x44 Jul 26 09:41:39 BrewMaster kernel: netif_rx_ni+0x1c/0x22 Jul 26 09:41:39 BrewMaster kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Jul 26 09:41:39 BrewMaster kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Jul 26 09:41:39 BrewMaster kernel: process_one_work+0x13c/0x1d5 Jul 26 09:41:39 BrewMaster kernel: worker_thread+0x18b/0x22f Jul 26 09:41:39 BrewMaster kernel: ? process_scheduled_works+0x27/0x27 Jul 26 09:41:39 BrewMaster kernel: kthread+0xe5/0xea Jul 26 09:41:39 BrewMaster kernel: ? __kthread_bind_mask+0x57/0x57 Jul 26 09:41:39 BrewMaster kernel: ret_from_fork+0x22/0x30 Jul 26 09:41:39 BrewMaster kernel: ---[ end trace afda9ed42ec3be7f ]---

Changed Status to Closed

Changed Status to Open

Thanks, but I don't have any containers running with an IP address on this server. I did in the past and it settled down when I stopped everything and just used this unit as a file share. I have Pi-Hole running on other unRAID server with an IP and it's fine though. I'll keep digging on this and post what I find.

I have multiple servers with this exact same issue. <SERVERNAME> winbindd[21875]: idmap_hash_initialize: The idmap_hash module is deprecated and should not be used. Please migrate to a different plugin. This module will be removed in a future version of Samba Not sure I understand the solution or even the problem. Which Plug-in is the issue? Plugins: CA Fix Common Problems Unassigned Devices User Scripts ZFS for unRAID 6

Finally found this, looks like I got a bad stick of RAM. I'm running ECC RAM and reseated the ram during the first server crash. memtest didn't show anything after a quick run, didn't have time do a full test. Heat is not an issue with my setup. I have a good quality 750W PSU. Going to swap the DIMM on channel 0 with the one in channel 3 and see if this shows up again. Mar 4 07:03:17 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:04:56 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:15:59 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:19:42 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:22:31 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:23:28 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:25:47 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:26:18 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:26:38 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:55:16 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:58:00 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 07:59:02 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 08:01:05 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 08:09:12 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 08:09:58 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 08:10:03 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 08:18:00 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 08:21:35 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Mar 4 08:21:56 kernel: EDAC MC0: 1 CE ie31200 CE on mc#0csrow#1channel#0 (csrow:1 channel:0 page:0x0 offset:0x0 grain:8 syndrome:0x52) Edit: To help find what DIMM is having the error: root@system~: grep "[0-9]" /sys/devices/system/edac/mc/mc*/csrow*/ch*_ce_count /sys/devices/system/edac/mc/mc0/csrow0/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow0/ch1_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow1/ch0_ce_count:34 <- ERROR COUNT /mc0/csrow1/ch0 /sys/devices/system/edac/mc/mc0/csrow1/ch1_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow2/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow2/ch1_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow3/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow3/ch1_ce_count:0 mcX = Memory Controller (single, dual CPU) chX = Channel 0, Channel 1, Channel 3 (single, dual, triple Channel RAM) csrowX = see chart Channel 0 Channel 1 Channel 3 ============================================ csrow0 | DIMM_A0 | DIMM_B0 | DIMM_C0 | csrow1 | DIMM_A0 | DIMM_B0 | DIMM_C0 | ============================================ ============================================ csrow2 | DIMM_A1 | DIMM_B1 | DIMM_C0 | csrow3 | DIMM_A1 | DIMM_B1 | DIMM_C0 | ============================================ ============================================ csrow4 | DIMM_A1 | DIMM_B1 | DIMM_C0 | csrow5 | DIMM_A1 | DIMM_B1 | DIMM_C0 | ============================================ ============================================ csrow6 | DIMM_A1 | DIMM_B1 | DIMM_C0 | csrow7 | DIMM_A1 | DIMM_B1 | DIMM_C0 | ============================================ root@system~: dmidecode -t memory | grep 'Locator' Locator: DIMMA1 <- THIS ONE - DIMM_A0 Bank Locator: P0_Node0_Channel0_Dimm0 Locator: DIMMA2 Bank Locator: P0_Node0_Channel0_Dimm1 Locator: DIMMB1 Bank Locator: P0_Node0_Channel1_Dimm0 Locator: DIMMB2 Bank Locator: P0_Node0_Channel1_Dimm1 EDIT: Moved the stick of RAM and got an error in another slot. Ordering new stick of RAM. /sys/devices/system/edac/mc/mc0/csrow0/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow0/ch1_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow1/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow1/ch1_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow2/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow2/ch1_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow3/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow3/ch1_ce_count:1 <- NEW ERROR EDIT2: /sys/devices/system/edac/mc/mc0/csrow3/ch1_ce_count:2 <- NEW ERROR Errors have slowed but at least I have a second error now. RAM incoming. EDIT3: replaced defective DIMM, 4 days no error. Turned on WDS. Watching Logs and CPU useage. WDS script still running. EDIT4: No more memory errors and WDS is running without eating a full CPU. Calling this solved.

This is the issue I'm having, 1 cpu pegged at 100%, wdss is the process, this goes on until the kernel start panicing or running out of memory. Trying the restart script at the end of the thread and will report back. https://forums.unraid.net/topic/85073-wsdd-100-using-1-core/page/2/ EDIT: Script did not reset the 100% cpu usage. Disabled WDS. Kept script running for now.

When you try and make the disk bootable it gives this message. The assumption is NTFS would be valid, but that is for Make Bootable script only. I also read somewhere that NTFS is needed for UEFI boot, but I can't find that part now. Thanks for clearing it up, I'm amazed that it booted as well.

This issue demonstrated on 6.8.3 and 6.9.0 ASUS Prime x570-PRO board Intel I211AT NIC No IP address and no eth0 device on inital boot. Samsung FIT Plus 64 GB flash drive: Formated NTFS - Booted to command prompt no eth0 Formated FAT32 - Booted to command prompt - got IP ADDRESS!!! and eth0 present.

Sorry, here they are. Thanks for looking. brewmaster-diagnostics-20210226-0651.zip

SOLUTION Unable to run a video card at address 06:00.0 Solution: Don't use it. Six video cards only need Five. Might be something to do with the motherboard trying to force SLI. System has been running well for a while now. Building a second one.

I'm not good with decoding syslog kernel panics and need some help please. System Specs: Supermicro X11SSH-LN4F - c states disable in bios Xeon E3-1240 v6 64 GB DDR4 ECC 2 ZFS pools, one Nytro SSD pool and one HDD pool UNRAID disk is on an nvme, using a Samsung Fit flash drive. No longer running VMs or Dockers but ran stable with them. Got some remote replication to another machine. Enabled saving syslog to the flash drive and waited for another failure. Found a Kernel panic Feb 23rd 1412 and repeats going forward. The system worked but cranky. System gets worse around Feb 24th 1400. Out of memory errors at Feb 24th 1408 and repeats. kernel: Out of memory: Kill process 12302 (monitor) score 0 or sacrifice child System required hard reboot Feb 24th 1443. Been digging through forums and google and come up with possible bad RAM issues but it's ECC RAM. Possible left over routes from VMs and Dockers. Easy to remote but can't see that doing it. Takes about 6 days to blow up. Currently rebooting on day 4. There is a record of a boot where the two pools tried mounting to the same mount point. Ignore that, it got fixed. Another Kernel panic at Feb 24th 17:24 but it doesn't repeat. System stable from this point on. Thanks in advance. syslog

Update: All 5 VM's were running when I came back on Tuesday (3 days uptime). Next test will be under load.

What I'm trying to do and mostly successful at this point is create an UNRAID box with 5 GPU's, monitors, keyboards and mice so I can have multiple, physical Windows 10 VM's running at once. I've got an ASUS PRIME X-570-PRO board becuase it has 6 PCIe Slots, with a Ryzen 9 3900X CPU and 32 GB of RAM and 6 nVidia GT 710 PCIe 1x video cards with good HDMI cables. Storage is a single Samsung 512 NVMe. PSU is a Corsair RM850x. Case is a rack mount 4U with plenty of fans. BIOS on the Motherboard is latest stable release. I've read LOTS of forums to ge to this point so let me list the sucesses so far: Succeses: - All Video cards are in their own IOMMU groups with their respective sound devices EDIT: See post below about USB Manager - skips this whole USB XML mess - Using Logitech Wireless Keyboard and Mice with a USB 3.0 7 port hub, I was able to map the Logitech Unifier based on it's Address Bus and Device Number. The sucky thing is that if you make a change to the VM, you have to uncheck all the Logitech devices, save it, then add the XML code manually afterwards. xml example <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> *** This Number is the same for every Logitech Unifier <product id='0xc52b'/> *** This Number as well <address bus='5' device='4'/> *** This is were the magic is. </source> <address type='usb' bus='0' port='1'/> *** This I believe related to the USB Hub. </hostdev> - Dumping the BIOS of all the video cards. Even though they are all the same, you need a seperate file for each VM - Creating a Windows 10 version 1909 VM with hardware GPU passthough and a specific Logitech Keyboard and Mouse works just fine. - I can even use the Primary Video Card as a pass though so I don't need 6 video cards, I only need 5 video cards. Where It Fails. - The 5th VM just doesn't want to accept the driver for the video card. It'll run at the standard resolution of a basic video adapter (800x600) and the device manager has an exclamation mark on the GT 710 saying there was an issue and shut it down. In the Device Listing below it shows cards at addresses: 04:00.0 - Works 05:00.0 - Works 06:00.0 - Works (this one usually flakes out) 08:00.0 - Works 0c:00.0 - Works (Primary Video Card) Edit: This is the first time I've had it boot with this hardware addressing scheme and I think it's working. What I have tried. - Swapping all video card around. (possible bad card) - Dummping the specific bios out of each card and matching them up their serial number. (the serial numbers are almost sequential) - Going from 6 Cards to 5 Cards (using the primary card as passthough) - Put in a GT 730 video card (which works but still number 5 is not alive) What I have noticed. - The problem gets worse if you add the sound devices to the VM's. (I only get 2 VM to work at proper resolution) What I'm yet to try. - Now that I have 5 video cards I'm going to cycle through the empty slot. (Change which slot is empty) The Ask: HELP! Edit: I helped my self by moving the video cards around. I've posted the System Information and one of the VMs XML files. I hope I'm missing something. The Purpose: Will be revealed upon success. It's 2 parts Fun and 1 part Work. Edit: It's a Mobile 5 Workstation machine for light duty work on a hanger floor. 1 power cord, 1 ethernet cable. The fun part is where I load up a random 4-5 player retor arcade game for Fridays (Bomberman, Gauntlet, etc) SOLUTION: Move cards around and try different address configurations until one works. SOLVED: Not until this thing is stable. SECOND ASK: ANY IDEA WHY? Thank you, Holmesware IOMMU group 0:[1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 1:[1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2:[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 3:[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4:[1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 5:[1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 6:[1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7:[1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 8:[1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 9:[1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 10:[1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 11:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 12:[1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 IOMMU group 13:[1022:57ad] 01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream IOMMU group 14:[1022:57a3] 02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 15:[1022:57a3] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 16:[1022:57a3] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 17:[1022:57a3] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 18:[1022:57a3] 02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 19:[1022:57a3] 02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 20:[1022:57a4] 02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:1485] 09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:149c] 09:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] 09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 21:[1022:57a4] 02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 0a:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 22:[1022:57a4] 02:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 0b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 23:[144d:a808] 03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 IOMMU group 24:[10de:128b] 04:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) [10de:0e0f] 04:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) IOMMU group 25:[10de:128b] 05:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) [10de:0e0f] 05:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) IOMMU group 26:[10de:128b] 06:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) [10de:0e0f] 06:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) IOMMU group 27:[8086:1539] 07:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 28:[10de:128b] 08:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) [10de:0e0f] 08:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) IOMMU group 29:[10de:128b] 0c:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) [10de:0e0f] 0c:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) IOMMU group 30:[1022:148a] 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 31:[1022:1485] 0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 32:[1022:1486] 0e:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 33:[1022:149c] 0e:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 34:[1022:1487] 0e:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows10 2</name> <uuid>0f65f96e-2665-8b69-9f1e-25af41d896cf</uuid> <description>Hydra2</description> <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='2'/> <vcpupin vcpu='1' cpuset='14'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='15'/> </cputune> <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/0f65f96e-2665-8b69-9f1e-25af41d896cf_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disk1/domains/Windows10-gfx08_2/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <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/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='pci' index='7' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </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:3b:f9:82'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' 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'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <rom file='/mnt/disk1/isos/Hydra2-710.rom'/> <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='0xc52b'/> <address bus='5' device='3'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='none'/> </devices> </domain>