Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
After installing or upgrading to ESXi 5.5 Patch 8, you experience these symptoms: Fails to resume a HWv8 or lower virtual machine suspended on a host prior to ESXi 5.5 Patch 8 upgrade (build 4179633). You may see the error: The features supported by the processors in this machine are different from the features supported by the processors in the machine on which the virtual machine state was saved. With the following conditions, vMotion of a virtual machine fails from a host running ESXi 5.5 prior to build 4179633 to a host running ESXi 5.5 build 4179633. You may see the error: A general system error occurred: The source host detected that the destination failed to resume. Note: The above symptoms affect on virtual machine with following conditions. Virtual machine with Hardware version 8.Virtual machine running in an EVC enabled cluster.Virtual machine has not been power cycled after EVC changes. The above two symptoms only appear on certain Intel processors. For example: Intel(R) Xeon(R) CPU E7-4880Intel(R) Xeon(R) CPU E7-8867Intel(R) Xeon(R) CPU E5-2680Intel(R) Xeon(R) CPU E5-2660Intel(R) Xeon(R) CPU E5-2650Intel(R) Xeon(R) CPU E5-2620 Note: The problems may occur on some Intel Processors that are not listed here. The /vmfs/volumes/datastore/virtual_machine/vmware.log file shows entries similar to: YYYY-MM-DDT<time>| vmx| I120: evcCompatibilityMode = 1 YYYY-MM-DDT<time>| vmx| I120: Error: This host does not support a feature required by the VM. YYYY-MM-DDT<time>| vmx| I120: Features: 0x00200000 YYYY-MM-DDT<time>| vmx| I120: CPUID test failed: 1.edx. YYYY-MM-DDT<time>| vmx| I120: Msg_Reset: YYYY-MM-DDT<time>| vmx| I120: [msg.checkpoint.cpucheck.fail.feature] The features supported by the processors in this machine are different from the features supported by the processors in the machine on which the virtual machine state was saved. YYYY-MM-DDT<time>| vmx| I120: ---------------------------------------- YYYY-MM-DDT<time>| vmx| I120: CPUID ignoring mismatch on restore. YYYY-MM-DDT<time>| vmx| I120: guestCpuFeatures = 0x2000fc YYYY-MM-DDT<time>| vmx| I120: MigrateSetStateFinished: type=2 new state=11 YYYY-MM-DDT<time>| vmx| I120: MigrateSetState: Transitioning from state 10 to 11. YYYY-MM-DDT<time>| vmx| I120: [msg.checkpoint.migration.failedReceive] Failed to receive migration. YYYY-MM-DDT<time>| vmx| I120: Msg_Post: Error YYYY-MM-DDT<time>| vmx| I120: [msg.checkpoint.migration.failedReceive] Failed to receive migration. </time></time></time></time></time></time></time></time></time></time></time></time></time></time>The /var/log/hostd.log file on the source host shows entries similar to: YYYY-MM-DDT<time> [664C1B70 verbose 'Vmsvc.vm:/vmfs/volumes/path/to/virtual_machine/virtual_machine.vmx'] VMotionLastStatusCb: Failed with error 7: The source detected that the destination failed to resume. YYYY-MM-DDT<time> [664C1B70 verbose 'Vmsvc.vm:/vmfs/volumes/path/to/virtual_machine/virtual_machine.vmx'] VMotionLastStatusCb:: hostlog state changed from emigrating to failure YYYY-MM-DDT<time> [664C1B70 info 'Vcsvc.VMotionSrc (1472650463322557)'] ResolveCb: VMX reports needsUnregister = false for migrateType MIGRATE_TYPE_VMOTION YYYY-MM-DDT<time> [664C1B70 info 'Vcsvc.VMotionSrc (1472650463322557)'] ResolveCb: Failed with fault: (vmodl.fault.SystemError) {dynamicType = <unset>,faultCause = (vmodl.MethodFault) null,reason = "The source detected that the destination failed to resume.",msg = "",} </time></time></time></time> Note : The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This is a known issue affecting ESXi 5.5 Patch 8, ESXi550-201608001 build 4179633. This issue is resolved in ESXi 5.5 Patch Release ESXi550-201609001 build 4345813, available at VMware Patch Downloads. For more information on downloading patch, see How to download patches in Customer Connect (1021623). For more information, see VMware ESXi 5.5, Patch Release ESXi550-201609001(2146717). To work around this issue, power off the virtual machine and perform a cold migration.
How to download patches in Customer ConnectPowering on a virtual machine from a suspend state or reverting to a snapshot fails