Symptoms
Unable to apply DRS resource settings on host. . This can significantly reduce the effectiveness of DRS.hostd and vpxa services, as suggested in the article "Unable to apply DRS resource settings on host" error in vCenter Server, does not resolve the alert.YYYY-MM-DDTHH:mm:SS.SSSZ warning vpxd[4###7] [Originator@6876 sub=MoResGroup opID=HB-host-###@###-####] Receive ConfigIssue when processing RP updates from host [vim.HostSystem:host-1###,ESXI_HOST_NAME] type vmodl.fault.SystemError on ManagedObject vim.ResourcePool:pool## for method vim.ManagedEntity.destroy
or
YYYY-MM-DDTHH:mm:SS.SSSZ warning vpxd[4###7] [Originator@6876 sub=MoResGroup opID=HB-host-###@###-####] Receive ConfigIssue when processing RP updates from host [vim.HostSystem:host-1###,ESXI_HOST_NAME] type vmodl.fault.SystemError on ManagedObject vim.ResourcePool:pool## for method vim.ManagedEntity.updateConfig
VMware vCenter Server
When 'inaccessible' virtual machines are present, vCenter Server may be unable to push the appropriate resource settings to the host, triggering the "Unable to apply DRS resource settings" alert.
To resolve this issue, clear the 'inaccessible' status of the virtual machine. The simplest way is to unregister the inaccessible virtual machine from the inventory:
inaccessible' in the inventory.Note: Virtual machines can become 'inaccessible' for a variety of reasons. If you wish to resolve the 'inaccessible' status without removing the VM from the inventory, please refer to Virtual machines appear as invalid or orphaned or inaccessible.