FTR. physical_network=physnet2 was set to address issues with a specific SDN integration.
This was observed on a Queens cloud.
I suspect what we saw is not hardware change or firmware upgrade but the fact the number of enabled VFs in sysfs, e.g. as in /sys/class/net/eno2/device/sriov_numvfs is initially set to 0, and we are enabling the number of VFs during startup. Possibly initial registration happened prior to enabling VFs
FTR. physical_ network= physnet2 was set to address issues with a specific SDN integration.
This was observed on a Queens cloud.
I suspect what we saw is not hardware change or firmware upgrade but the fact the number of enabled VFs in sysfs, e.g. as in /sys/class/ net/eno2/ device/ sriov_numvfs is initially set to 0, and we are enabling the number of VFs during startup. Possibly initial registration happened prior to enabling VFs