vnic_type=direct was allowed to select PF in older relesase and its still valid for it to select type-pci i belive i will have to look.
change that added support for vnic-type=direct-phsyical broke backwards compatiabliy with the old behaver of direct mean vf or pf but type-pci may be an expction to that.
and yes the assment in https://bugs.launchpad.net/nova/+bug/1892361/comments/3
is correct this bug will only be hit if you updated the firmware of bios config of a device that was previously not capable of support sriov to one that is.
this could also happen if you replaced a non sriov vf capable nic with one that does
the workaround for that case is to remove the nic, start the agent, add an nic and start the agent.
what release of openstack was this observed in?
vnic_type=direct was allowed to select PF in older relesase and its still valid for it to select type-pci i belive i will have to look.
change that added support for vnic-type= direct- phsyical broke backwards compatiabliy with the old behaver of direct mean vf or pf but type-pci may be an expction to that.
and yes the assment in https:/ /bugs.launchpad .net/nova/ +bug/1892361/ comments/ 3
is correct this bug will only be hit if you updated the firmware of bios config of a device that was previously not capable of support sriov to one that is.
this could also happen if you replaced a non sriov vf capable nic with one that does
the workaround for that case is to remove the nic, start the agent, add an nic and start the agent.