####-##-##T##:##:##.###Z error vpxd[166116] [Originator@#### sub=MoHost opID=HB-host-######@#####-#######f] [ReplaceVmMoRefs] Linked vm 0 not found on host vim.HostSystem:host-#####, ignored
####-##-##T##:##:##.###Z error vpxd[166116] [Originator@#### sub=MoHost opID=HB-host-######@#####-#######f] [ReplaceVmMoRefs] Linked vm 0 not found on host vim.HostSystem:host-#####, ignored
..
####-##-##T##:##:##.###Z error vpxd[166197] [Originator@#### sub=MoHost opID=memlmfc2-#######-auto-#yor#-h5:#######-##-#########] [ReplaceVmMoRefs] Linked vm 0 not found on host vim.HostSystem:host-#####, ignored
####-##-##T##:##:##.###Z error vpxd[166197] [Originator@#### sub=MoHost opID=memlmfc2-#######-auto-#yor#-h5:#######-##-#########] [ReplaceVmMoRefs] Linked vm 0 not found on host vim.HostSystem:host-######, ignored
VMware vCenter Server 8.0.x
VMware vSphere ESXi 8.0.x
This issue can occur when the vCenter Server (vpxd) service has outdated autostart information in its cache that relate to no longer existing virtual machines. In some situations this information might not get cleared, thus causing the Autostart manager to fail applying new changes to the autostart configuration.
Broadcom engineering is aware of this issue.
To work around this, please apply one of the options:
Restart the vCenter Server service (vpxd) to clear the cached autostart settings:
# service-control --stop vpxd && service-control --start vpxd
Unregister the ESXi host holding the virtual machine you want to configure autostart for from the vCenter inventory and add it back.
This will lead to the cached settings for any object on the host to be invalided.
However, this option should be selected with caution, as removing/readding the ESXi host can result in additional reconfiguration being required, especially if the host is a member of a distributed switch or of a VSAN datastore.