Storage vMotion in virtual machines with Advanced Option Latency Sensitivity of High in ESXi 5.5 fails with the error: Failed to power on VM

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Storage vMotion fails in virtual machines when Latency Sensitivity is set to High
• You see entries similar to:
  
  The VM failed to resume on the destination during early power on.
  Failed to power on VM.
  Could not power on VM : msg.vmk.status.VMK_BAD_PARAM.
  Group vm.3787099: Invalid memory allocation parameters for virtual machine vmm0: VMName. (min: 0, max: 1048576, minLimit: -1, shares: -3, units: pages)
  Invalid memory reservation for a fully preallocated virtual machine: the minimum must be equal to memsize (1048576 pages).

Environment

VMware vSphere ESXi 5.5
VMware vCenter Server 5.5.x

Resolution

This is a known issue affecting vCenter Server and ESXi 5.5.

This issue is resolved in:

• VMware ESXi 5.5 Update 3. For more information, see the VMware ESXi 5.5 Update 3 Release Notes. Download the latest version, available at VMware Downloads.
• vCenter Server 5.5 Update 3. For more information, see the VMware vCenter Server 5.5 Update 3 Release Notes. Download the latest version, available at VMware Downloads.

To work around this issue:

1. Log in to the vSphere Web Client.
2. Right-click on the virtual machine you want to perform a Storage vMotion and click Edit Settings.
3. Select the VM Options tab.
4. Locate Latency Sensitivity and change the setting to Normal.
5. Click OK to save the changes.
6. Execute the Storage vMotion process.
7. After completing, you can restore the Latency Sensitivity to its previous value.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box in the Actions panel. ESXi 5.5 において [詳細] オプションの [待ち時間感度] が [高] になっている仮想マシンが、次のエラーで Storage vMotion に失敗する： Failed to power on VM