Hi, AllThere is following issue in latest libvirt-4.5.0-10.el7_6.12 package, which could prevent live VM migrations with web sockets enabled, when libvirtd were restarted prior to migration.Environment:# uname -aLinux inv-cp1-hv3-centos7 3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 21:24:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux# cat /etc/redhat-releaseCentOS Linux release 7.6.1810 (Core)# rpm -qa | grep libvirt-4libvirt-4.5.0-10.el7_6.12.x86_64# rpm -qa | grep qemu-kvmqemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64qemu-kvm-tools-ev-2.12.0-18.el7_6.5.1.x86_64Repro steps:1. start VM with following screen configuration:<graphics type="vnc" listen="0.0.0.0" passwd="vnc_password" port="-1" auto-port="yes" websocket="-1"/>
2. check VM XML (migratable):
#virsh dumpxml 1 > | grep vnc
<graphics type="vnc" listen="0.0.0.0" passwd="vnc_password" port="-1" auto-port="yes" websocket="-1"/>
3. restart libvirtd
# systemctl restart libvirtd.service4. check VM XML config again#virsh dumpxml 1 > | grep vnc
<graphics type="vnc" listen="0.0.0.0" passwd="vnc_password" port="-1" auto-port="yes" websocket="5700"/>
5. try to migrate this VM to hypervisor with already running VM and you will get following errorerror: internal error: Failed to reserve port 5700It happens when on destination hypervisor there is VM running with web socket port 5700.This issue was fixed since libvirt-4.6.0 release.I've retested it with libvirt-4.9.0 and libvirt-5.0.0 from http://mirror.centos.org/centos/7/virt/x86_64/libvirt-latest/ repo. And it actually fixed here.Interesting to know when newer version of libvirt(at least 4.6.0 of 4.5.0 with fix) will be available in official centos updates repo?
_______________________________________________Thanks a lot,Oleksandr
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV