Search the VMware Knowledge Base (KB)
View by Article ID

Applying DRS settings to an ESX or ESXi host generates an error (1004667)

  • 68 Ratings

Symptoms

  • Cannot apply DRS resource settings to an ESX host.
  • Attempting to apply DRS resource settings to an ESX host through vCenter Server may result in these errors:

    Unable to apply DRS resource settings on host (Reason: A general system error occurred: Invalid Fault). This can significantly reduce the effectiveness of DRS.

    Unable to apply DRS settings on the host. The object has already been deleted or has not been completely created. This can significantly reduce the effectiveness of DRS


  • The hostd.log file contains entries similar to:

    [2009-02-10 'TaskManager' 131554224 info] Task Created : haTask-pool6-vim.ResourcePool.updateChildResourceConfiguration-69471
    [2009-02-10 'vm:/vmfs/volumes/4641d0de-5a0b6ca4-7964-0019b9b90cc3/XP_VM/XP_VM.vmx' 131554224 error] Invalid transition requested (VM_STATE_TOOLS_UPGRADING -> VM_STATE_RECONFIGURING): Tasks running
    [2009-02-10 'TaskManager' 131554224 info] Task Completed : haTask-pool6 vim.ResourcePool.updateChildResourceConfiguration-69471
    [2009-02-10 'Vmomi' 131554224 info] Activation [N5Vmomi10ActivationE:0x8eebb68] : Invoke done [updateChildResourceConfiguration] on [vim.ResourcePool:pool6]
    [2009-02-10 'Vmomi' 131554224 info] Throw vim.fault.TaskInProgress
    [2009-02-10 'Vmomi' 131554224 info] Result:
    (vim.fault.TaskInProgress) {
    dynamicType = <unset>,
    task = 'vim.Task:haTask-880-vim.VirtualMachine.upgradeTools-57306',
    msg = ""
    }
    [2009-02-10 'SOAP' 131554224 error] Method vim.ResourcePool.updateChildResourceConfiguration threw undeclared fault of type vim.fault.TaskInProgress

Resolution

This is a known issue affecting vSphere 3.x, 4.x, and 5.x.

This issue is resolved in:
 
Caution: Disabling DRS when the cluster is part of vCloud Director will stop vCloud Director from working properly and should not be done. Contact support for assistance with this issue. For more information, see Filing a Support Request in My VMware (2006985).
 
Note: VMware recommendeds to migrate active virtual machines off the host prior to running these steps. Also to move vmkernel interfaces to a standard vSwitch to prevent connectivity issues. For more information, see Disabling vNetwork Distributed Switches (1010718).
 
To work around this issue:
 

ESX

Apply these measures in escalating order:
  1. Recreate the pools.xml file:

    1. Log in as root to the ESX host with an SSH client.
    2. Run this command:

      # mv /etc/vmware/hostd/pools.xml /tmp

    3. Restart the management agents on the ESX host. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490).

      Caution: Ensure that Automatic Startup/Shutdown of virtual machines is disabled before running this command or you risk rebooting the virtual machines. For more information, see Restarting hostd (mgmt-vmware) on ESX hosts restarts hosted virtual machines where virtual machine Startup/Shutdown is enabled (1003312).

  2. Check virtual machines for pending VMware Tools installations and cancel them.
  3. If there are no pending VMware Tools installations found, you may have to manually install VPXA. For more information on manually installing the VPX Agent, see Verifying and reinstalling the correct version of the VMware vCenter Server agents (1003714).
  4. Remove the ESX host from the DRS cluster, then re-add it to the cluster:

    Note: Before removing the ESX host from the cluster verify if the cluster is EVC Enabled. If the cluster is EVC enabled, vmotion the virtual machines to another ESX host in the same cluster. If the ESX has already being removed from the EVC cluster, see Re-adding an ESX host to an EVC cluster (1012864).

    1. Right-click on the host and click Disconnect in the VI Client.
    2. Right-click on the host and click Remove.
    3. Right-click on the cluster and click Add Host.
    4. Follow the wizard prompts to re-add the host to the cluster.

  5. Disable and re-enable DRS in the cluster:

    Note: Disabling DRS removes all the resource pools in the cluster.

    Caution: Disabling DRS when the cluster is part of vCloud Director will stop vCloud Director from working properly and should not be done. Please contact support for assistance with this issue. For information, see Filing a Support Request in My VMware (2006985).

    1. Right-click on the cluster and click Edit Settings.
    2. Deselect Enable VMware DRS. You receive a warning indicating that turning off DRS destroys all resource pools in the cluster.
    3. Click OK to turn off DRS and destroy all resource pools.
    4. Right-click on the cluster and click Edit Settings.
    5. Select Enable VMware DRS and click OK.

      Note: In vSphere 5.1, a new option for retaining Resource Pools when disabling DRS is added. For more information, see Retaining resource pools when disabling VMware DRS Clusters (2032893).

ESXi

Apply these measures in escalating order:
  1. Restarting the Management Services can resolve the issue on the host. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490)

  2. Recreate the pools.xml file:
    1. Log in as root to the ESXi in troubleshooting mode. For more information, see Tech Support Mode for Emergency Support (1003677).

    2. Issue the command:

      # mv /etc/vmware/hostd/pools.xml /tmp

    3. Restart the management agents on the ESXi host. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490).

      Caution: Ensure Automatic Startup/Shutdown of virtual machines is disabled before running this command or you risk rebooting the virtual machines. For more information, see Restarting hostd (mgmt-vmware) on ESX hosts restarts hosted virtual machines where virtual machine Startup/Shutdown is enabled (1003312).

  3. Check virtual machines for pending VMware Tools installations and cancel them.
  4. If there are no pending VMware Tools installations found, you may have to manually install VPXA.

    To manually install VPXA, see Verifying and reinstalling the correct version of the VMware vCenter Server agents (1003714)

  5. Remove the ESXi host from the DRS cluster, then re-add it to the cluster:

    Note: Before removing the ESX host from cluster verify if the cluster is EVC Enabled. If the cluster is EVC enabled, vMotion the virtual machines to another ESX host in the same cluster first. If the ESX host has already being removed from the EVC cluster, see Re-adding an ESX host to an EVC cluster (1012864).

    1. Right-click on the host and click Disconnect in vSphere Client.
    2. Right-click on the host and click Remove.
    3. Right-click on the cluster and click Add Host.
    4. Follow the wizard prompts to re-add the host to the cluster.

  6. Disable and re-enable DRS in the cluster:

    Note: Disabling DRS removes all the resource pools in the cluster.

    Caution: Disabling DRS when the cluster is part of vCloud Director will stop vCloud Director from working properly and should not be done. Contact support for assistance with this issue. For more information, see How to file a Support Request in My VMware (2006985).

    1. Right-click on the cluster and click Edit Settings.
    2. Deselect Enable VMware DRS. You receive a warning indicating that turning off DRS destroys all resource pools in the cluster.
    3. Click OK to turn off DRS and destroy all resource pools.
    4. Right-click on the cluster and click Edit Settings.
    5. Select Enable VMware DRS and click OK.

      Note: In vSphere 5.1, a new option for retaining Resource Pools when disabling DRS has been added. For more information, see Retaining resource pools when disabling VMware DRS clusters in the vSphere Web Client (2032893).
Note: An alarm can be configured to warn of this issue by setting it to monitor CPU and Memory usage below 1%. For more information refer to the appropriate documentation for VMware vCenter Server.

Tags

enable-drs  drs-advance-options

See Also

Update History

10/17/2012 - Added additional symptom. 05/15/2013 - update title, cleaned hostd.logs of superfluous info, added language and release status, added kb 1013037 to the replaces list. 11/04/2014 - Added 5.5 products.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 68 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 68 Ratings
Actions
KB: