I'm seeing the same errors in my systems after V2T. Only on a few VMs though, most go over without issue.
Don't know the cause or the fix but the VMs that did give this error did now have functioning networking after the vmotion migration. As a workaround we disabled the nic on the VM and re-enabled it and the VMs have not had any issue with networking after that.
The alarms remain though and if I resolve them in the UI they will reappear. I would love to see some resolution to this issue.