Ask Your Question

Revision history [back]

Nova aborts your migration because it is taking too long. Most probably your instance is too busy: Nova has transferred a memory page, the instance modifies that page so that it has to be copied again, and so on until Nova gives up.

Other factors are the sheer size of the instance and the capacity of the network used for migration. Which is, by default, the management network.

Recommendations:

  • Calm your instance down
  • Improve networking
  • Use config parameters to influence Nova's migration behaviour; see the admin guide for instructions.

Nova aborts your migration because it is taking too long. Most probably your instance is too busy: Nova has transferred a memory page, the instance modifies that page so that it has to be copied again, and so on until Nova gives up.

Other factors are the sheer size of the instance and the capacity of the network used for migration. Which is, by default, the management network.

Recommendations:

  • Calm your instance down
  • Improve networking
  • Use config parameters to influence Nova's migration behaviour; see the admin guide for instructions. EDIT: It depends on your OpenStack release to what extent these instructions are applicable. Live Migration has improved a lot in the last two years.

Nova aborts your migration because it is taking too long. Most probably your instance is too busy: Nova has transferred a memory page, the instance modifies that page so that it has to be copied again, and so on until Nova gives up.

Other factors are the sheer size of the instance and the capacity of the network used for migration. Which is, by default, the management network.

Recommendations:

  • Calm your instance down
  • Improve networking
  • Use config parameters to influence Nova's migration behaviour; see the admin guide for instructions. EDIT: A caveat: It depends on your OpenStack release to what extent these instructions are applicable. Live Migration has improved a lot in the last two years.