Alarm on ESXi hosts "Unable to apply DRS resource settings on host"
search cancel

Alarm on ESXi hosts "Unable to apply DRS resource settings on host"

book

Article ID: 392008

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Random ESXi hosts have alarm “Unable to apply DRS resource settings on host xxx in xxx. . This can significantly reduce the effectiveness of DRS.”

vpxa.log reports error:
Got exception when invoking VMOMI method; <<last binding: <<TCP '127.0.0.1 : xxxx'>, <TCP '127.0.0.1 : 8307'>>>, /sdk>, vim.ResourcePool.updateChildResourceConfiguration, N5Vmomi5Fault15InvalidArgument9ExceptionE(Fault cause: vmodl.fault.InvalidArgument
Failed: Update VM-name in RP(vim.ResourcePool:ha-root-pool), code=VmUpdateDec, falut=[N5Vmomi5Fault15InvalidArgumentE:0x000000c8aee4a930]

hostd.log reports warning:
Insufficient CPU reservation for latency-sensitive VM. Expected CPU reservation: xxxx MHz, actual: 0 MHz

Some VMs configured Latency Sensitivity = high but did not reserve full cpu resource.

 

Environment

VMware vCenter Server

VMware vSphere ESXi

Resolution

1. Change VM configuration Latency Sensitivity to normal:

VM > Edit settings > VM Options > Advanced > Latency Sensitivity > Normal

2. Restart ESXi host vpxa and hostd service:

/etc/init.d/hostd restart
/etc/init.d/vpxa restart