virt July 2019

virt@lists.centos.org

2 participants
2 discussions

live migration issues after libvirtd restart
by Oleksandr Panchuk 23 Aug '19

23 Aug '19

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: <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.service 4. 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 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

2 1

Are XSA-289, XSA-274/CVE-2018-14678 fixed ?
by Yuriy Kohut 01 Jul '19

01 Jul '19

Hello, Are XSA-289 and XSA-274/CVE-2018-14678 fixed with Xen recent 4.8, 4.10 and kernel 4.9.177 packages ? Thank you

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt July 2019