Ask Your Question

Revision history [back]

Weird VM migration behavior in Juno

I have a four-node Juno (1 controller, 1 network, and 2 compute nodes) with live migration enabled on it. I can perform block live migration with no problem and in a reasonable time. My management network is also a 1GB network.

The only weird thing I faced is that when a VM migrates for the first time after its creation, the migration time along with the down time are considerably shorter than those in any further migration attempts. For example, for a VM with a "Small" flavor, the migration time and down time for the first migration attempt are 80 ms and 206 ms respectively. However, for the second migration attempt and any attempt beyond that, the migration time and down time range between 120-130 ms and 300-500 ms respectively. This also happens for the other VMs with different flavors.

Please notice that I soft reboot the VM after each migration attempt and there is at least 3 minutes gap between each migration. There is also just one VM in my cluster at a time and the VM is not loaded.

Weird VM migration behavior in Juno

I have a four-node Juno (1 controller, 1 network, and 2 compute nodes) with live migration enabled on it. I can perform block live migration with no problem and in a reasonable time. My management network is also a 1GB network.

The only weird thing I faced is that when a VM migrates for the first time after its creation, the migration time along with the down time are considerably shorter than those in any further migration attempts. For example, for a VM with a "Small" flavor, the migration time and down time for the first migration attempt are 80 ms and 206 ms respectively. However, for the second migration attempt and any attempt beyond that, the migration time and down time range between 120-130 ms and 300-500 ms respectively. This also happens for the other VMs with different flavors.

Please notice that I soft reboot the VM after each migration attempt and there is at least 3 minutes gap between each migration. There is also just one VM in my cluster at a time and the VM is not loaded.