[VMC On AWS] vMotion fails after graphics configuration is modified while VM is running

Products

• VMware Cloud on AWS

Issue/Introduction

This article provides the steps to diagnose and remediate vMotion failures caused by graphics settings being modified while the VM was running.

Symptoms:

A VM is unable to complete a vMotion, with the destination vmware.log containing any of the following as mentioned below :

****
SVGA: 3d checkpoint is unsupported by this host
Msg_Question:
[msg.svga.compatFeatureCheckFailed] This virtual machine's snapshot is expecting graphics features that VMware is unable to provide on this host. Restoring the VM might be possible, but could cause serious problems if the guest OS is relying on any of the missing features.

****
  restoring SVGA
Progress 0% (none)
Progress 101% (none)
MigrateSetStateFinished: type=2 new state=12
MigrateSetState: Transitioning from state 11 to 12.
Migrate: Caching migration error message list:
[msg.checkpoint.migration.failedReceive] Failed to receive migration.
[msg.checkpoint.mrestoregroup.failed] An error occurred restoring the virtual machine state during migration.
Msg_Post: Error
[msg.checkpoint.mrestoregroup.failed] An error occurred restoring the virtual machine state during migration.
[msg.checkpoint.migration.failedReceive] Failed to receive migration.
----------------------------------------
In vCenter Server logs you see entries similar to:
 
****
error = (vim.fault.GenericVmConfigFault):
message = "The source detected that the destination failed to resume."
 

Cause

A VM that has had some of its graphics configuration modified while the VM is running may get into an inconsistent state wherein it is unable to vMotion to another host or Suspend/Resume.

These options could have been changed by:

•  An administrator mannually editing them in the UI, under VM Options > Advanced -> Configuration Parameters -> Edit Configuration.

• A scripting API such as PowerCLI, or VIM.

• Another VMware product or 3rd party tool.

Resolution

This can be resolved by a full PowerOff/PowerOn of the affected VM, which will allow the new configuration options to take effect.

Additional Information

Impact/Risks:

Incorrectly changing the VM's raw configuration options while the VM is running or suspended places the VM at risk of problems such as data corruption, VM failure, or an inability to vMotion or Resume the VM.