Issue with Live and Cold Migration

Community Support
1

Hello,

I am currently running an OpenNebula 6.10.0 infrastructure with four hypervisors, and everything is working correctly overall.

However, I feel like there is a role reversal between the “Migrate live” and “Migrate” buttons. When I use “Migrate” to perform a cold migration of a VM, I see in the “Info” section that the VM goes through the states “save_migrate,” “boot_migrate,” and then “running.” On the other hand, when I use “Migrate live,” the VM goes through the states “migrate” and then “running.” This seems logical so far.

However, in practice, when I do a continuous ping or connect to the VM via Putty, I do not lose connectivity if I use “Migrate” (cold migration), but I do lose connectivity if I use “Migrate live” (live migration). I feel like it should be the other way around, or am I mistaken?

Is this a known bug? Has anyone encountered this issue before, or could I have missed something during configuration?

Thank you in advance for your help.

2

While doing the migration process, have two terminals open and check the status of the VM in both the source and target host with virsh list to make sure they are going through the proper state transitions.