thankful-shampoo-15514
09/12/2025, 6:34 AMbrave-garden-49376
09/12/2025, 3:54 PMlsmod | grep mlx
mlx5_ib 401408 0
ib_uverbs 172032 2 rdma_ucm,mlx5_ib
ib_core 430080 10 rdma_cm,ib_ipoib,rpcrdma,iw_cm,ib_iser,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
mlx5_core 1847296 1 mlx5_ib
mlxfw 36864 1 mlx5_core
psample 20480 1 mlx5_core
pci_hyperv_intf 16384 1 mlx5_core
tls 110592 5 cxgb4,bonding,mlx5_core
How you modify the /oem files to make this happen, and introduce the new NIC ports might be the real challenge.
Looks like /oem/90_custom.yaml might be one place to start. Though mine only has these for modprobe lines:
name: Harvester Configuration
stages:
initramfs:
- commands:
- modprobe kvm
- modprobe vhost_net
- modprobe kvm
- modprobe vhost_net
That's the file that has the ifcfg file and bonding config too.
Finally, I can say that I installed with mlx single port NICs and then swapped those out for dual, and when I configured clusters (or whatever is supposed to map to the bonds) they frequently failed to incorporate the NIC ports into the bond configuration - so basically nothing worked. A fresh install with the dual-port NIC in place fixed all errant behavior for this issue.
So, perhaps a rolling fresh install to be safe and least troublesome? I can't speak to how to do this with my limited experience, but it seems like it should be a possible path.thankful-shampoo-15514
09/12/2025, 4:01 PMabundant-camera-87627
09/12/2025, 10:23 PMthankful-shampoo-15514
09/12/2025, 10:26 PMabundant-camera-87627
09/12/2025, 10:28 PMthankful-shampoo-15514
09/12/2025, 10:28 PMabundant-camera-87627
09/12/2025, 10:29 PMthankful-shampoo-15514
09/12/2025, 10:31 PM