While I don’t have the groupings, here’s what items are in seperate groups
All motherboard chipset items but two USB ports and the security TPM chip are in the same group. This makes sense to keep them in their own group, as you would need a USB port for encrypted key to load to boot with the TPM chip turned on and setup. These items include:
- All USB ports except for the 2 USB ports next to the 1gb NIC
- Both NICs
- All SATA ports
- Lower M.2 slot
- Bottom PCIe 2.0 x 16 (x4 electrically) slot at the bottom
- HD Audio
- The 1x PCIe slots
- Wireless NIC and Bluetooth
Items that are in separate groups are:
- Two USB ports and the Security TPM chip
- NVMe drive
- The top and middle PCIe 3.0 slots
Using ESXi, I was only able to passthrough the items that are in the separate groups list, but none of the motherboard chipset items. Honestly I feel that KVM + QEMU or Proxmox would be much more friendly about passing through certain items, but I have no experience with these hypervisors, so I can’t really say. At the least, KVM + QEMU running in Linux would be able to use the Aquantia NIC, as it has Linux drives (Aquantia NICs are not support by VMware and thus have no drivers, which SUCKS). Additionally, I was not able to do any Raw Device Mappings for hard drives to VMs on ESXi due to the SATA/RAID controller (presumably) not having a SCSI serial number, which makes sense for a consumer board. Sucks, but makes sense.
If anyone has any experience working with this board in Proxmox or KVM+QEMU on Linux, I’d love to hear if you were able to passthrough those main motherboard chipset items.