Hello. I just select live migrate from horizon without destination. Instance is on shared storage, I don't use force-complete. It looks like enable_qemu_monitor_announce_self = true cause this problem. It is ok if I change it to false. I use this option on openstack Xena because without it after live migration I cannot ping or access instances. This cloud uses OVS. I test with my current cloud 2025.1 which uses OVN, it seems we don't need this option anymore. Pls correct me if I am wrong. Nguyen Huu Khoi Nguyen Huu Khoi On Wed, Nov 26, 2025 at 6:23 PM Sean Mooney <smooney@redhat.com> wrote:
how did you "complete the migration" was it via the force-comlete action? that can take several minutes to complete at the qemu level as it need to transfer any outstanding memory or block data.
also what are defining as the migration end time? when the vm on the dest starts? (if post copy live migration is used the migration is still in-progress when that happens when the vm on the source is stopped? the vm has not been cleaned up so the migration is not complete in nova at this point as we need to remove any volume attachments, delete local files and update neutron in post-live migrate before the migration is actually completed.
it will not be updated to complete until all cleanup on the source host is also complete what you are reporting is not obviously indicative of a bug or error.
without more information we cant really help you understand if this is normal or not.
On 26/11/2025 01:18, Nguyễn Hữu Khôi wrote:
Hello.
I am working on instance migration. After I complete the migration, when I run *|openstack server migration list|* to check its status, it still shows as /running/. It takes around *12 minutes* before it updates to /completed /status.
My OPS: 2025.1
Thank you.
Nguyen Huu Khoi