Search the VMware Knowledge Base (KB)
View by Article ID

"Failed to add memory page" error during vMotion after upgrade (2143943)

  • 13 Ratings
Language Editions

Symptoms

After upgrading from ESXi 5.0/5.1 to ESXi 5.5 Update 3b or 6.0 Update 1b, you experience this symptom:

Performing a vMotion of a virtual machine from an ESXi 5.0/5.1 host to a ESXi 5.5 Update 3b or 6.0 Update 1b host fails.

Note: For additional symptoms and log entries, see the Additional Information section.

Purpose

The issue of vMotion of virtual machine failing after upgrading from ESXi 5.0/5.1 to ESXi 5.5 Update 3b or 6.0 Update 1b is resolved in ESXi 6.0 Update 2.

Resolution

This issue is resolved in:

To work around this issue if you do not want to upgrade, power off the virtual machine and then power on.

Additional Information

You experience these additional symptoms:

On the source ESXi host:
  • In the /vmfs/volumes/datastore/virtual_machine/vmware.log file, you see entries similar to:

    /vmfs/volumes/datastore/virtual_machine/virtual_machine.vmx: Cannot remove symlink /var/run/vmware/root_0/1453212583391267_303401/configFile: No such file or directory
    2016-01-19T14:09:43.973Z| vmx| I120: Vix: [303401 mainDispatch.c:3964]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
    2016-01-19T14:09:43.973Z| vmx| I120: Msg_Post: Error
    2016-01-19T14:09:43.973Z| vmx| I120: [vob.swap.migrate.invalidindex.mig] The migration swap type is not supported for migration.
    2016-01-19T14:09:43.973Z| vmx| I120: [vob.migrate.addpage.swapped.invalidindex] Received invalid swap slot data (0xc000f3ba) for pgNum 0x201.
    2016-01-19T14:09:43.973Z| vmx| I120: [vob.vmotion.addpage.failed.status] vMotion migration [aae0118:1453212580328954] failed to add memory page 0x201 to VM: Bad parameter


  • In the /var/log/vmkernel file, you see entries similar to:

    2016-01-19T14:09:43.818Z cpu19:2550920)WARNING: VMotionUtil: 4356: 1453212580328954 S: socket connected returned: Already disconnected
    2016-01-19T14:09:43.818Z cpu19:2550920)WARNING: VMotionUtil: 6814: 1453212580328954 S: failed to flush stream buffer: Already disconnected
    2016-01-19T14:09:43.818Z cpu19:2550920)WARNING: VMotionUtil: 1670: 1453212580328954 S: failed writing stream completion: Already disconnected
    2016-01-19T14:09:43.839Z cpu8:2767161)WARNING: Migrate: 4983: 1453212580328954 S: Migration considered a failure by the VMX.  It is most likely a timeout, but check the VMX log for the true error.


  • In the /var/log/hostd file, you see entries similar to:

    2016-01-19T14:09:43.807Z [FFAAEAD0 verbose 'vm:/vmfs/volumes/datastore/virtual_machine/virtual_machine.vmx'] VMotionCmdCb [1453212580328954] 'start': done
    2016-01-19T14:09:43.843Z [2803DB90 info 'vm:/vmfs/volumes/datastore/virtual_machine/virtual_machine.vmx'] Disconnect check in progress.
    2016-01-19T14:09:43.844Z [295C9B90 verbose 'vm:/vmfs/volumes/datastore/virtual_machine/virtual_machine.vmx'] Handling message _vmx2: vMotion migration [aae0118:1453212580328954] socket connected returned: Already disconnected
    --> vMotion migration [aae0118:1453212580328954] failed to flush stream buffer: Already disconnected
    --> vMotion migration [aae0118:1453212580328954] failed writing stream completion: Already disconnected
    --> Migration to host <<unknown>> failed with error Already disconnected (0xbad002e).
    -->
    2016-01-19T14:09:43.844Z [2803DB90 info 'vm:/vmfs/volumes/datastore/virtual_machine/virtual_machine.vmx'] Disconnect check in progress.
    2016-01-19T14:09:43.844Z [295C9B90 warning 'vm:/vmfs/volumes/datastore/virtual_machine/virtual_machine.vmx'] Failed to find activation record, event user unknown.


On the Destination ESXi host:
  • In the /var/log/vmkernel file, you see entries similar to:

    2016-01-19T14:09:43.807Z cpu18:33744)MigrateNet: vm 33744: 2096: Accepted connection from <source_ip>
    2016-01-19T14:09:43.807Z cpu18:33744)MigrateNet: vm 33744: 2138: data socket size 0 is less than config option 562140
    2016-01-19T14:09:43.807Z cpu18:33744)MigrateNet: vm 33744: 2166: dataSocket 0x410ab6838a10 receive buffer size is 562140
    2016-01-19T14:09:43.807Z cpu18:33744)VMotionUtil: 3396: 1453212580328954 D: Stream connection 2 added.
    2016-01-19T14:09:43.811Z cpu21:303408)WARNING: Swap: 787: The migration swap type is not supported for migration.
    2016-01-19T14:09:43.811Z cpu21:303408)WARNING: VmMemMigrate: 1976: Received invalid swap slot data (0xc000f3ba) for pgNum 0x201.
    2016-01-19T14:09:43.811Z cpu21:303408)WARNING: VMotionRecv: 1116: 1453212580328954 D: failed to add memory page 0x201 to VM: Bad parameter

    2016-01-19T14:09:43.811Z cpu21:303408)WARNING: VMotionUtil: 1476: 1453212580328954 D: failed draining stream completion: Bad parameter
    2016-01-19T14:09:43.811Z cpu21:303408)WARNING: Migrate: 269: 1453212580328954 D: Failed: Bad parameter (0xbad0007) @0x418021e56f9a
    2016-01-19T14:09:43.818Z cpu5:303401)WARNING: Migrate: 5291: 1453212580328954 D: Migration considered a failure by the VMX.  It is most likely a timeout, but check the VMX log for the true error.

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Tags

vmotion, upgrade, memory page, bad parameter

See Also

Update History

02/22/2016 - Added the details of ESXi 5.5 patch ESXi550-201602001, which resolves this issue. 03/21/2016 - Added the details of the ESXi 6.0 Update 2 release, which resolves this issue.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 13 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 13 Ratings
Actions
KB: