Error: "Unable to apply DRS resource settings on host" after a Powered-on Virtual Machine is moved to a Resource Pool
Article ID: 369896
Updated On:
Products
Issue/Introduction
- An ESXi host in the vCenter Server reports the following error approximately 10 minutes after moving a powered-on Virtual Machine to a resource pool:
Unable to apply DRS resource settings on host. This can significantly reduce the effectiveness of DRS.
- On the vCenter Server, in
/var/log/vmware/vpxd/vpxd.log,the below warning is reported:
Receive ConfigIssue when processing RP updates from host [vim.HostSystem:{host moid},{host IP address}] type vim.fault.InsufficientMemoryResourcesFault on ManagedObject vim.ResourcePool:{resource pool moid} for method vim.ResourcePool.moveInto
Environment
VMware vSphere ESXi 8.x
Cause
This error may occur on ESXi when a Virtual Machine's memory requirements are miscalculated during its migration into a resource pool. This miscalculation results in a synchronization conflict between ESXi and the vCenter Distributed Resource Scheduler (DRS).
Consequently, the ESXi host continues to associate the Virtual Machine with its original resource pool while DRS performs calculations based on the new resource pool.
Resolution
This issue is fixed in ESXi 8.0 U3 build 24022510.
Workaround
- Avoid changing Virtual Machine resource pools while a Virtual Machine is powered on.
- If the error occurs after a powered-on Virtual Machine is moved to a resource pool, follow the below steps:
- Power off the Virtual Machine.
- Move the Virtual Machine to the desired resource pool.
- Power on the Virtual Machine.
Additional Information
- The error "
Unable to apply DRS resource settings on host. This can significantly reduce the effectiveness of DRS."is not sufficient to match to the issue in this article. - If there is no association to a powered-on VM moving to a resource pool, then refer to KB: "Unable to apply DRS resource setting on host" error in vCenter Server.
Feedback
