Re: [CentOS-virt] live migration issues after libvirtd restart

2019-08-23 Thread Sandro Bonazzola
Il giorno lun 1 lug 2019 alle ore 13:37 Oleksandr Panchuk <
oleksandr.panc...@onapp.com> ha scritto:

> Hi, All
>
> There 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 -a
> Linux 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-release
> CentOS Linux release 7.6.1810 (Core)
>
> # rpm -qa | grep libvirt-4
> libvirt-4.5.0-10.el7_6.12.x86_64
>
> # rpm -qa | grep qemu-kvm
> qemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64
> qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64
> qemu-kvm-tools-ev-2.12.0-18.el7_6.5.1.x86_64
>
>
> Repro steps:
> 1. start VM with following screen configuration:
>
>  auto-port="yes" websocket="-1"/>
>
>
> 2. check VM XML (migratable):
>
> #virsh dumpxml 1 > | grep vnc
>
>  auto-port="yes" websocket="-1"/>
>
>
> 3. restart libvirtd
>
> # systemctl restart libvirtd.service
>
>
> 4. check VM XML config again
>
> #virsh dumpxml 1 > | grep vnc
>
>  auto-port="yes" websocket="5700"/>
>
>
> 5. try to migrate this VM to hypervisor with already running VM and you will 
> get following error
>
> error: internal error: Failed to reserve port 5700
>
>
> It 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?
>
>
Official centos updates repo are rebuilt from RHEL and latest released
version in RHEL is libvirt-4.5.0-23.el7 which will be in CentOS 7.7.1908.
You can give it a run from
https://buildlogs.centos.org/c7.1908.00.x86_64/libvirt/20190809003358/4.5.0-23.el7.x86_64/
If it's not working there, you'll need to file a bug on RHEL for being
considered for backport or stick to CentOS Virtualization SIG version you
are already consuming from libivrt-latest repository.


> 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 RHV

Red Hat EMEA 

sbona...@redhat.com
*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.*
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt


[CentOS-virt] live migration issues after libvirtd restart

2019-07-01 Thread Oleksandr Panchuk
Hi, All

There 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 -a
Linux 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-release
CentOS Linux release 7.6.1810 (Core)

# rpm -qa | grep libvirt-4
libvirt-4.5.0-10.el7_6.12.x86_64

# rpm -qa | grep qemu-kvm
qemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64
qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64
qemu-kvm-tools-ev-2.12.0-18.el7_6.5.1.x86_64


Repro steps:
1. start VM with following screen configuration:




2. check VM XML (migratable):

#virsh dumpxml 1 > | grep vnc




3. restart libvirtd

# systemctl restart libvirtd.service


4. check VM XML config again

#virsh dumpxml 1 > | grep vnc




5. try to migrate this VM to hypervisor with already running VM and
you will get following error

error: internal error: Failed to reserve port 5700


It 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