Hi, I have a KVM server running on Centos 7.5. [root at kvm2 ~]# cat /etc/redhat-release CentOS Linux release 7.5.1804 (Core) Qemu packages are from Centos repository. [root at kvm2 ~]# rpm -qa|grep qemu libvirt-daemon-driver-qemu-3.9.0-14.el7_5.7.x86_64 qemu-img-1.5.3-156.el7_5.5.x86_64 qemu-kvm-common-1.5.3-156.el7_5.5.x86_64 ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch qemu-guest-agent-2.8.0-2.el7_5.1.x86_64 qemu-kvm-1.5.3-156.el7_5.5.x86_64 But, I want to install a new version of qemu from ovirt repositories. (This because I need live disk snapshots). So I installed ovirt yum repository, run yum update and I see qemu will be updated (as you can see below in red) Resolving Dependencies --> Running transaction check ---> Package glusterfs.x86_64 0:3.8.4-54.15.el7.centos will be updated ---> Package glusterfs.x86_64 0:3.12.14-1.el7 will be an update ---> Package glusterfs-api.x86_64 0:3.8.4-54.15.el7.centos will be updated ---> Package glusterfs-api.x86_64 0:3.12.14-1.el7 will be an update ---> Package glusterfs-cli.x86_64 0:3.8.4-54.15.el7.centos will be updated ---> Package glusterfs-cli.x86_64 0:3.12.14-1.el7 will be an update ---> Package glusterfs-client-xlators.x86_64 0:3.8.4-54.15.el7.centos will be updated ---> Package glusterfs-client-xlators.x86_64 0:3.12.14-1.el7 will be an update ---> Package glusterfs-fuse.x86_64 0:3.8.4-54.15.el7.centos will be updated ---> Package glusterfs-fuse.x86_64 0:3.12.14-1.el7 will be an update ---> Package glusterfs-libs.x86_64 0:3.8.4-54.15.el7.centos will be updated ---> Package glusterfs-libs.x86_64 0:3.12.14-1.el7 will be an update ---> Package google-chrome-stable.x86_64 0:69.0.3497.92-1 will be updated ---> Package google-chrome-stable.x86_64 0:69.0.3497.100-1 will be an update ---> Package kexec-tools.x86_64 0:2.0.15-13.el7 will be updated ---> Package kexec-tools.x86_64 0:2.0.15-13.el7_5.1 will be an update ---> Package libcacard.x86_64 40:2.5.2-2.el7 will be updated ---> Package libcacard.x86_64 40:2.5.2-2.1.el7 will be an update ---> Package pyOpenSSL.x86_64 0:0.13.1-3.el7 will be obsoleted ---> Package python-coverage.x86_64 0:3.6-0.5.b3.el7 will be obsoleted ---> Package python-dateutil.noarch 0:1.5-7.el7 will be updated ---> Package python-dateutil.noarch 1:2.4.2-1.el7 will be an update ---> Package python-netaddr.noarch 0:0.7.5-9.el7 will be updated ---> Package python-netaddr.noarch 0:0.7.18-1.el7 will be an update ---> Package python-six.noarch 0:1.9.0-2.el7 will be obsoleted ---> Package python2-coverage.x86_64 0:4.4.1-1.el7 will be obsoleting ---> Package python2-pyOpenSSL.noarch 0:16.2.0-3.el7 will be obsoleting ---> Package python2-six.noarch 0:1.10.0-9.el7 will be obsoleting ---> Package qemu-img.x86_64 10:1.5.3-156.el7_5.5 will be obsoleted ---> Package qemu-img-ev.x86_64 10:2.10.0-21.el7_5.4.1 will be obsoleting ---> Package qemu-kvm.x86_64 10:1.5.3-156.el7_5.5 will be obsoleted ---> Package qemu-kvm-common.x86_64 10:1.5.3-156.el7_5.5 will be obsoleted ---> Package qemu-kvm-common-ev.x86_64 10:2.10.0-21.el7_5.4.1 will be obsoleting ---> Package qemu-kvm-ev.x86_64 10:2.10.0-21.el7_5.4.1 will be obsoleting --> Finished Dependency Resolution Finally I did not update qemu because this KVM server has multiples VMs running and I was not sure if it could impact VMs working. My question, how can this qemu update can imapct my already running VMs? Appreciate your help. Thanks in advance. Regards Israel.