VMware is working as designed. The following is the latest Intel Driver Version: 1.9.5. Currently, with this Driver patch, the Trusted Virtual Function (VF) set on the VM can stay Trusted persistently between VM reboots.
NOTE: VLAN Tag Stripping Control feature is currently not available on Windows VF drivers. Some know issues, VF adapter cannot receive any packet after VM reboot. The probability of issue occurrence increases with the overall number of VFs and number of VMs reboots.
Workaround: power off and on VMs with VFs instead of rebooting them. More info: Release_Notes_i40en-1.9.5
Workaround:
At the moment, Intel team has provided the TrustMode configurations, which allows to override the policy on a per VF basis.
- Type ”esxcli intnet sriovnic vf set -v $VFID -n %VMNICID -s off” at VM startup, to disable spoof checking for that VF at the PF.
- Type ”esxcli intnet sriovnic vf set -v $VFID -n %VMNICID –t on” at VM startup, to set that VF as trusted mode at the PF.
Example:
esxcli intnet sriovnic vf -n vmnic0 -v 1 -t on
esxcli intnet sriovnic vf -n vmnic0 -v 1 -t off
- Enable VF spoof-check for VF 1
esxcli intnet sriovnic vf -v 1 -n vmnic0 -s on
- Disable VF spoof-check for VF 1
esxcli intnet sriovnic vf -v 1 -n vmnic0 -s off
For more information refer to release notes in More info: Release_Notes_i40en-1.9.5 [ see attachment ]