Check you can ping the destination host using the host name - compute1-VirtualBox - as this is what Nova passes to libvirt when doing live migration.
On Thu, Jul 30, 2015 at 2:20 PM, Abhishek Talwar <[email protected]> wrote: > Hi, > > I have a multinode OpenStack kilo setup with 2 compute nodes, a controller > and a network node. I am trying to migrate a Vm from host to the other, but > there is a migration failure and the VM stays on the same host. > > I can ping between the compute nodes, and I have set libvirt to listen mode. > Using the following steps: > > Modify /etc/libvirt/libvirtd.conf. before : #listen_tls = 0 after : > listen_tls = 0 > > before : #listen_tcp = 1 after : listen_tcp = 1 > > add: auth_tcp = "none" > > Modify /etc/init/libvirt-bin.conf. before : exec /usr/sbin/libvirtd -d after > : exec /usr/sbin/libvirtd -d -l -l is short for –listen > > Modify /etc/default/libvirt-bin. before :libvirtd_opts=" -d" after > :libvirtd_opts=" -d -l" > > Restart libvirt. After executing the command, ensure that libvirt is > successfully restarted. $ stop libvirt-bin && start libvirt-bin $ ps -ef | > grep libvirt > > Nova compute(Compute) logs: > > 2015-07-30 10:05:56.928 2101 ERROR nova.virt.libvirt.driver [-] [instance: > e8a310e6-3682-44fd-93b2-4e2564de047d] Live Migration failure: operation > failed: Failed to connect to remote libvirt URI > qemu+tcp://compute1-VirtualBox/system: Unable to resolve address > 'compute1-VirtualBox' service '16509': Name or service not known 2015-07-30 > 10:05:57.029 2101 ERROR nova.virt.libvirt.driver [-] [instance: > e8a310e6-3682-44fd-93b2-4e2564de047d] Migration operation has aborted > > > =====-----=====-----===== > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
