VxRail: vMotion fails with error "A general system error occurred: Invalid fault"

Summary: This is a vMotion issue, which fails due to general error or source host vMotion network error, even though vMotion VMkernel port is properly configured.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

vMotion fails when migrating to a specific host or hosts.
There are enough vMotion VMkernel ports configured and can ping successfully.

The following errors are seen when vMotion is attempted: 

A general system error occurred: Invalid fault

 The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct


vmware.log

2024-05-21T16:58:32.347Z In(05) vmx - [msg.checkpoint.migration.nodata] The vMotion failed because the destination host did not receive data from the source host on the vMotion network.  Please check your vMotion network settings and physical network configuration and ensure they are correct.
2024-05-21T16:58:32.347Z In(05) vmx - Migrate: cleaning up migration state.
2024-05-21T16:58:32.347Z In(05) vmx - VigorTransport_ServerSendResponse opID=lw189jgb-62232-auto-1c0p-h5:70028930-8b-01-fe-39c9 seq=6: Completed Bootstrap request with messages.
2024-05-21T16:58:32.347Z In(05) vmx - Migrate: Final status reported through Vigor.
2024-05-21T16:58:32.347Z In(05) vmx - MigrateSetState: Transitioning from state 12 to 0.
2024-05-21T16:58:32.347Z In(05) vmx - Msg_Post: Error
2024-05-21T16:58:32.347Z In(05) vmx - [msg.checkpoint.migration.nodata] The vMotion failed because the destination host did not receive data from the source host on the vMotion network.  Please check your vMotion network settings and physical network configuration and ensure they are correct.


Source VM ESXi hostd.log:

2024-05-21T16:56:37.835Z info hostd[2100617] [Originator@6876 sub=Vcsvc.VMotionSrc.7107587418190845405 opID=lw189jgb-62050-auto-1bvn-h5:70028810-9c-01-f0-63dc] ResolveCb: VMX reports needsUnregister = false for migrateType MIGRATE_TYPE_VMOTION
2024-05-21T16:56:37.835Z info hostd[2100617] [Originator@6876 sub=Vcsvc.VMotionSrc.7107587418190845405 opID=lw189jgb-62050-auto-1bvn-h5:70028810-9c-01-f0-63dc] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.checkpoint.init.migration.failure",
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "1",
-->                value = "195887136"
-->             },
-->             (vmodl.KeyAnyValue) {
-->                key = "2",
-->                value = "Not supported"
-->             }
-->          ],
-->          message = "Failed to initialize migration at source.  Error 0xbad0020.  Not supported."
-->       }
-->    ],
-->    reason = "Failed to initialize migration at source.  Error 0xbad0020.  Not supported.",
-->    msg = "Failed to initialize migration at source.  Error 0xbad0020.  Not supported.


Destination VM ESXi Hostd.log:

2024-05-21T16:58:32.348Z info hostd[2109598] [Originator@6876 sub=Vcsvc.VMotionDst.7107587418190845405 opID=lw189jgb-62232-auto-1c0p-h5:70028930-8b-01-fe-39c9] ResolveCb: VMX reports needsUnregister = true for migrateType MIGRATE_TYPE_VMOTION
2024-05-21T16:58:32.348Z info hostd[2109598] [Originator@6876 sub=Vcsvc.VMotionDst.7107587418190845405 opID=lw189jgb-62232-auto-1c0p-h5:70028930-8b-01-fe-39c9] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.checkpoint.migration.nodata",
-->          message = "The vMotion failed because the destination host did not receive data from the source host on the vMotion network.  Please check your vMotion network settings and physical network configuration and ensure they are
correct.",

 

Cause

This occurs when the setting "Migrate.Enabled" is set to disabled in the advanced settings.
Note: This issue may also occur due to a duplicate IP address on your network. Ensure that the IP addresses for your vCenter Servers and ESX/ESXi hosts are unique.

Resolution

To resolve this issue, follow the steps below:

  1. Connect vSphere or VMware Infrastructure Client to your vCenter Server.

  2. Select the ESXi host.

  3. Select the Configuration tab.

  4. Select Advanced Settings under Software.

  5. Select Migrate and change Migrate.Enabled to 0.

  6. Select OK and close.

  7. Select Advanced Settings.

  8. Select Migrate and change Migrate.Enabled to 1.

  9. Select OK and then Close.

Note: If you see the invalid parameter error after resetting "Migrate.Enabled" to 1, see Performing a vMotion or adding a network card to a virtual machine fails with the error: Necessary module isn't loaded. (2013128) This hyperlink is taking you to a website outside of Dell Technologies.

If these steps do not resolve the issue, try increasing the timeout for migration network operations after Step 4 above. Then go to the remaining steps. Ensure to repeat these steps on the destination host.
To increase the timeout for migration network operations:

  1. Select the Configuration tab.

  2. Select Advanced Settings under Software > Migrate.

  3. Change Migrate.NetTimeout to 60s. The default is 20s.

  4. Select OK and then Close.

Affected Products

VxRail
Article Properties
Article Number: 000225285
Article Type: Solution
Last Modified: 14 Jul 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.