Search results

https://enterprise-support.nvidia.com/s/article/howto-configure-and-probe-vfs-on-mlx5-drivers it says probing is the default config, for whatever reason, dumb also note

cx5 stores config on the card if im not mistaken, could be set there to probe vfs

uh its a function of mlx5_core that makes the vf show up as usable interfaces to the system, ie enp5s0f2v0, if im not mistaken i could be wrong and thats not what those are, just saying thats what they look like since they are mounted as devices for the host to use there will be problems to pass...

looks like you are probing the vfs, pretty sure you dont want that if you are passing them through

what does a pfsense instance do for you that isp supplied equipment or existing wifi appliance does not? that hardware is overkill for a virtualized pfsense 100mbit you can with vlans, use only the one nic usb will add latency and overhead

additionally regarding mellanox part numbers, the third letter in the suffix being a C indicates cx3 pro version ie -FCCT dont know about Ps and Qs

https://www.hpe.com/psnow/doc/c04111517.pdf

is Dell CX322A really cx3 pro? maybe the wrong firmware on there

2.42.5000 SRIOV is still "broken" with nv_cfg disabled [ 8.137305] mlx4_core 0000:01:00.0: requested vfs (16) > available vfs (0). Continuing without SR_IOV this seems to be how they encourage people to buy new hardware, perfect fit for nvidia

1. enable sr-iov options on the host motherboard, sr-iov vt-d etc etc 2. enable sriov in the card, which probably involves reflashing the firmware, not sure when they went to dynamic firmware variables (CX3 pro?) 3. configure mlx4_core module parameters, num_vfs and optionally...

I haven't been able to get this to work with CX2 or CX3. Blacklist mlx4_core no effect. "Blacklist with fake install" no effect. "allow_unsafe_interrupts" guest starts, sees card then host freezes or kernel fault VFs passthrough fine, except not windows guest on CX3 unless you patch the...

this is usually a diver version mismatch between the driver that lives under system devices and the driver the lives under network adaptors