Attempting to vMotion multiple virtual machines fails with the error: Operation cannot be performed while vApp operation is in progress
search cancel

Attempting to vMotion multiple virtual machines fails with the error: Operation cannot be performed while vApp operation is in progress

book

Article ID: 301837

calendar_today

Updated On:

Products

VMware

Issue/Introduction




Symptoms:
  • You cannot vMotion a vApp with multiple virtual machines.
  • Attempting to vMotion multiple virtual machines at once from a vApp fails with an error in Recent Task:

    Operation cannot be performed while vApp operation is in progress

  • You are able to successfully vMotion one virtual machine at a time.
  • In the vpxd.log file, you see errors similar to:

    T10:24:29.273-05:00 [06260 error 'Default' opID=2CC1B0F5-00000121] (Log recursion level 2) vim.fault.VAppTaskInProgress

    ------ In-memory logs end --------
    T10:24:29.273-05:00 [06260 error 'Default' opID=2CC1B0F5-00000121] Section for VMware VirtualCenter, pid=1152, version=5.0.0, build=build-623373, option=Release
    -->
    T10:24:29.273-05:00 [06260 info 'Default' opID=2CC1B0F5-00000121] [VpxLRO] -- FINISH task-31060 -- vm-2868 -- vim.VirtualMachine.migrate -- 52651d20-1dd9-ac51-9d4a-a3c7c8efca50(52552953-d9c5-4797-c28a-04977414f78c)
    T10:24:29.273-05:00 [06260 info 'Default' opID=2CC1B0F5-00000121] [VpxLRO] -- ERROR task-31060 -- vm-2868 -- vim.VirtualMachine.migrate: vim.fault.VAppTaskInProgress:
    --> Result:
    --> (vim.fault.VAppTaskInProgress) {
    --> dynamicType = <unset>,
    --> faultCause = (vmodl.MethodFault) null,
    --> task = 'vim.Task:task-31059',
    --> msg = "",
    --> }
    --> Args:
    -->
    --> Arg pool:
    -->
    --> Arg host:
    --> 'vim.HostSystem:host-3383'
    --> Arg priority:
    --> "highPriority"
    --> Arg state:
    -->

    T10:55:46.265-05:00 [06172 info 'Default' opID=ECEDA6B2-00000656] [VpxLRO] -- BEGIN task-31067 -- vm-2868 -- vim.VirtualMachine.migrate -- 52257f05-f3a2-e8f8-7217-4d697b010c2d(529e0162-353e-914c-ab18-dae12bebeee8)

    T10:55:46.265-05:00 [06172 info 'Default' opID=ECEDA6B2-00000656] [VpxLRO] -- FINISH task-31067 -- vm-2868 -- vim.VirtualMachine.migrate -- 52257f05-f3a2-e8f8-7217-4d697b010c2d(529e0162-353e-914c-ab18-dae12bebeee8)

    T10:55:46.265-05:00 [06172 info 'Default' opID=ECEDA6B2-00000656] [VpxLRO] -- ERROR task-31067 -- vm-2868 -- vim.VirtualMachine.migrate: vim.fault.VAppTaskInProgress:


Cause

This issue occurs because the entire vApp is held as an exclusive lock when a vMotion is performed. This prevents further vMotion operations from being performed.

Resolution

This issue is resolved in vSphere 5.0 and 5.1. For more information about this version, see VMware vCenter Server 5.0 Update 3 Release Notes. You can download the latest release from the VMware Download Center.

To work around this issue when you cannot upgrade, vMotion individual virtual machines contained in the vApp.


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box