"Unable to apply DRS resource settings on host" after deactivating DRS
search cancel

"Unable to apply DRS resource settings on host" after deactivating DRS

book

Article ID: 393138

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • The summary page of an ESXi host in vSphere Client shows a warning banner with the following message:

Unable to apply DRS resource settings on host. This can significantly reduce the effectiveness of DRS.

  • This warning has been shown since after DRS was deactivated.

  • The VMs with vTPM configured were added to a Resource Pool.

  • Messages similar to the following messages can be seen in the ESXi hostd.log:

####-##-##T##:##:##.###Z info hostd[2100299] [Originator@6876 sub=Vimsvc.TaskManager opID=HB-SpecSync-host-13009@448496-20ebe250-33-8476 user=vpxuser] Task Created : haTask-pool1-vim.ManagedEntity.destroy-3138011964
####-##-##T##:##:##.###Z warning hostd[2101028] [Originator@6876 sub=Hostsvc opID=HB-SpecSync-host-13009@448496-20ebe250-33-8476 user=vpxuser] HostCtl error in Remove: Can not delete non-empty group: pool1
####-##-##T##:##:##.###Z info hostd[2101028] [Originator@6876 sub=AdapterServer opID=HB-SpecSync-host-13009@448496-20ebe250-33-8476 user=vpxuser] AdapterServer caught exception: N7Hostsvc21HaPlatformConfigFault9ExceptionE(Fault cause: vim.fault.PlatformConfigFault
--> )
--> [context]zKq7AVICAgAAAD3hGgEUaG9zdGQAAH3kP2xpYnZtYWNvcmUuc28AALJvHAAt2RoAUloWAWQ0TWhvc3RkAAHW4qEBuL1PATAtqAEyPqgBJXyYAfa/iQGXiIkBC46JAnsj72xpYnZpbS10eXBlcy5zbwAB5UxQABwxKwCNbCsAUmE8Azt9AGxpYnB0aHJlYWQuc28uMAAEragObGliYy5zby42AA==[/context]
####-##-##T##:##:##.###Z info hostd[2101028] [Originator@6876 sub=Vimsvc.TaskManager opID=HB-SpecSync-host-13009@448496-20ebe250-33-8476 user=vpxuser] Task Completed : haTask-pool1-vim.ManagedEntity.destroy-3138011964 Status error

Environment

VMware vCenter Server 7.0

VMware vCenter Server 8.0

Cause

When DRS is deactivated, Resource Pools are permanently deleted from the cluster.

There is a problem at the time of this deletion, the VMs in it are relocated to the parent Resource Pool, but the associated tpm2emu process does not get relocated.

Otherwise, the Resource Pool will not become empty and consequently it cannot be deleted.

Resolution

Broadcom is aware of this issue and working on a fix.

As a workaround, for VMs that have been added to a resource pool and have vTPM configured, do one of the following:

  • Migrate the VMs to other ESXi hosts and migrate them back to the original host.
  • Shutdown the VMs and Power-on again.