Hello Abhishek,

Did you check on the source node whether the instance is still running or even 
defined (virsh list -all). This is because nova notices that the migration is 
completed when the VM in the source is gone and then triggers the 
post-migration.

IIRC, there's a bug in 0.x libvirt where the destination qemu disconnection is 
not picked up by the source libvirt, causing nova migration thread to wait. I 
don't know if libvirt 1.x works with nova properly yet.

Cheers
~parthi


From: abhishek jain [mailto:ashujain9...@gmail.com]
Sent: 02 April 2014 12:28
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Nova Live Migration issue

Thanks Nikolay and Parthipan

I have confirmed that the instance is running on the newer compute node by 
using sudo virsh list command.
I'm using below libvirt version ..

libvirtd (libvirt) 0.9.8
Actually I will not be able to present  the libvirt logs due to setup 
problem.I'll send logs as soon as possible.
Please let me know if any thing needs to be taken care in libvirt during the 
configuration


On Wed, Apr 2, 2014 at 3:00 PM, Parthipan, Loganathan 
<parthi...@hp.com<mailto:parthi...@hp.com>> wrote:
Can you confirm that it's no longer running on the source node and only running 
on the destination node?

What's your libvirt version?

Possibly the libvirt monitor lost connection and didn't complete the 
post-migration which would update the db. As Nikolay suggested, the libvirt.log 
would tell more, good if it also had debug turned on.

From: Nikolay Starodubtsev 
[mailto:nstarodubt...@mirantis.com<mailto:nstarodubt...@mirantis.com>]
Sent: 02 April 2014 09:01
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Nova Live Migration issue

Hi!
Can you show libvirt logs?




Nikolay Starodubtsev

Software Engineer

Mirantis Inc.



Skype: dark_harlequine1

2014-04-02 11:55 GMT+04:00 abhishek jain 
<ashujain9...@gmail.com<mailto:ashujain9...@gmail.com>>:
Hi all
I'm following the below link for VM migration from one compute node to the 
another from the controller node using devstack ..

http://www.mirantis.com/blog/tutorial-openstack-live-migration-with-kvm-hypervisor-and-nfs-shared-storage/
I'm able to migrate the instance from one compute node to the other compute 
node using the below command.

nova live-migration b33b23f8-4510-4ed3-8cd1-2d68c8186e40 salaria1
The instance is able to migrate properly and that i have confirmed using the 
sudo virsh list command over the newer compute node.

However the problem is when i type nova list at the same time.The status of 
instance is stuck at migrating and does not changes even after some time.
Moreover when i type nova show <instance -id> command,the old host of the 
instance is reflected instead of the new one.
Please help regarding this.
Thanks
Abhishek Jain

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to