vMotion failing with error 0xbad0020 as migrate module is not enabled on ESXi host
search cancel

vMotion failing with error 0xbad0020 as migrate module is not enabled on ESXi host

book

Article ID: 414122

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Unable to vMotion Virtual Machines (VMs) from a problematic host to any other host.

  • Migrating from the problematic host: When attempting to vMotion VMs from the problematic host to another host, the process progresses to 20% and eventually fails with the following error:

    "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."

  • Migrating to the problematic host: When attempting to vMotion VMs from working hosts to the problematic host, the following error is observed:

    "A general system error occurred. Launch failure"

Log Analysis: From the hostd logs of the impacted host, the following snippets are observed:

YYYY:MM:DDTHH::MM:xxxx Db(167) Hostd[<PROCESS_ID>]: [Originator@<ORIGINATOR_ID> sub=Vigor.Vmsvc.vm:/vmfs/volumes/<DATASTORE_UUID>/<VM_NAME>/<VM_NAME>.vmx] VMotionInitiateSrc: Start message: Failed to initialize migration at source.  Error 0xbad0020.  Not supported.
YYYY:MM:DDTHH::MM:xxxx Db(167) Hostd[<PROCESS_ID>]: -->
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: [Originator@<ORIGINATOR_ID> sub=Vmsvc.vm:/vmfs/volumes/<DATASTORE_UUID>/<VM_NAME>/<VM_NAME>.vmx] VigorMigrateNotifyCb:: hostlog state changed from emigrating to failure
YYYY:MM:DDTHH::MM:xxxx Db(167) Hostd[<PROCESS_ID>]: [Originator@<ORIGINATOR_ID> sub=Vmsvc.vm:/vmfs/volumes/<DATASTORE_UUID>/<VM_NAME>/<VM_NAME>.vmx] VMotionStatusCb [<MIGRATION_ID>]: Failed with error
[N3Vim5Fault20GenericVmConfigFaultE:0x000000f97de7ceb0]
YYYY:MM:DDTHH::MM:xxxx Db(167) Hostd[<PROCESS_ID>]: [Originator@<ORIGINATOR_ID> sub=Vmsvc.vm:/vmfs/volumes/<DATASTORE_UUID>/<VM_NAME>/<VM_NAME>.vmx] VMotionStatusCb: Firing ResolveCb
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: [Originator@<ORIGINATOR_ID> sub=Vcsvc.VMotionSrc.<MIGRATION_ID>] ResolveCb: VMX reports needsUnregister = false for migrateType MIGRATE_TYPE_VMOTION
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: [Originator@<ORIGINATOR_ID> sub=Vcsvc.VMotionSrc.<MIGRATION_ID>] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->    faultMessage = (vmodl.LocalizableMessage) [
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->       (vmodl.LocalizableMessage) {
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->          key = "msg.checkpoint.init.migration.failure",
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->          arg = (vmodl.KeyAnyValue) [
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->             (vmodl.KeyAnyValue) {
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->                key = "1",
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->                value = "<VALUE>"
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->             },
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->             (vmodl.KeyAnyValue) {
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->                key = "2",
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->                value = "Not supported"
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->             }
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->          ],
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->          message = "Failed to initialize migration at source.  Error 0xbad0020.  Not supported."
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->       }
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->    ],
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->    reason = "Failed to initialize migration at source.  Error 0xbad0020.  Not supported.",
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: -->    msg = "Failed to initialize migration at source.  Error 0xbad0020.  Not supported.
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: --> "
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: --> }
YYYY:MM:DDTHH::MM:xxxx In(166) Hostd[<PROCESS_ID>]: [Originator@<ORIGINATOR_ID> sub=Vmsvc.vm:/vmfs/volumes/<DATASTORE_UUID>/<VM_NAME>/<VM_NAME>.vmx] State Transition (VM_STATE_EMIGRATING -> VM_STATE_ON)

Environment

  • VMware vSphere ESXi 8.x.
  • VMware vSphere ESXi 9.x.

Cause

The vMotion (migrate) module is not enabled on the impacted ESXi host.

Resolution

Perform the following steps to verify and resolve the issue:

  1. Enable vsish on the ESXi host by connecting via SSH and running the following command:

    [root@<ESXI_HOST>:~] vsish

  2. Navigate to the migrate configuration directory to verify if the module is enabled:

    /> cd /config/Migrate/intOpts/

  3. Check the current status of the module:

    /config/Migrate/intOpts/> get /config/Migrate/intOpts/Enabled

    Expected Output:

    Vmkernel Config Option {
   Default value:1
   Min value:0
   Max value:1
   Current value:1
   hidden config option:0
   Description:Enable hot migration support
   Host specific config option:0
   Exclude option from config manager:0
   Option update requires reboot:0
   Option update requires maintenance mode:0
}

    Note: If the module is not enabled, the Current value will show as 0.

  4. Enable the module (If the Current value is 0), by running the following command:

    /config/Migrate/intOpts/> set /config/Migrate/intOpts/Enabled 1

  5. Retry the vMotion operation. It should now execute successfully.

Powered by Wolken Software