The issue was in the starting order of the service. To fix the issue stop the Libvirt service and start the service by issuing the command: systemctl start libvirtd-tcp.socket On Mon, Oct 18, 2021 at 12:12 PM Swogat Pradhan <swogatpradhan22@gmail.com> wrote:
Hi, I am using openstack victoria and i am facing an issue when using the live-migration feature. After choosing the live-migration of an instance from Compute1 to compute2 i am getting an error in nova-compute.log (of compute 1) stating:
*ERROR nova.virt.libvirt.driver [-] [instance: 59c95d46-2cbc-4787-89f7-8b36b826ffad] Live Migration failure: operation failed: Failed to connect to remote libvirt URI qemu+tcp://compute2/system: unable to connect to server at 'compute2:16509': Connection refused: libvirt.libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tcp://compute2/system: unable to connect to server at 'compute2:16509': Connection refused*
Which states that the libvirtd.tcp socket is not running (libvirtd should run on 16509 port inorder for live-migration to succeed).
Journalctl -xe output
*Oct 18 06:32:52 compute2 systemd[1]: libvirtd-tcp.socket: Socket service libvirtd.service already active, refusing.Oct 18 06:32:52 compute2 systemd[1]: Failed to listen on Libvirt non-TLS IP socket.*
I am trying to solve the above issue by adding --listen in the libvirtd_opts parameter in the service file and also in the /etc/default/libvirtd file. But after doing that the libvirtd service doesn't start.
Can someone suggest a way forward for this?
Thank you With regards, Swogat Pradhan