|Summary:||Rebase libvirt to current upstream release|
|Product:||Red Hat Enterprise Linux 7||Reporter:||Jaroslav Suchanek <jsuchane>|
|Component:||libvirt||Assignee:||Jiri Denemark <jdenemar>|
|Status:||CLOSED ERRATA||QA Contact:||Xuesong Zhang <xuzhang>|
|Severity:||unspecified||Docs Contact:||Jiri Herrmann <jherrman>|
|Version:||7.5||CC:||dyuan, jdenemar, jen, pasik, rbalakri, xuzhang|
|Fixed In Version:||libvirt-3.9.0-1.el7||Doc Type:||Rebase: Bug Fixes and Enhancements|
_libvirt_ rebased to 3.9.0 The _libvirt_ packages have been upgraded to version 3.9.0, which provides a number of bug fixes and enhancements over the previous version. Notable changes include: * Sparse files are now preserved after moving them to or from another host. * Response limits for remote procedure calls (RPCs) have been increased. * Virtualized IBM POWER9 CPUs are now supported. * Attaching devices to running guest virtual machines, also known as device hot plug, now supports more device types, such as input devices. * The libvirt library has been secured against the CVE-2017-1000256 and CVE-2017-5715 security issues. * VFIO-mediated devices now function more reliably.
|:||1472265 1472268 (view as bug list)||Environment:|
|Last Closed:||2018-04-10 10:52:40 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
|Bug Blocks:||1469590, 1472265, 1472268|
Description Jaroslav Suchanek 2017-07-18 10:22:48 UTC
Both RHEV and OpenStack will like to use new features and APIs provided by libvirt, which are impossible to deliver without rebasing libvirt (there are specific BZs for each of them). Version-Release number of selected component (if applicable): libvirt >= 3.0.0 (the exact version depends on rebase deadlines)
Comment 3 Jaroslav Suchanek 2017-12-11 13:12:21 UTC
Jirka, can you please share text for release notes?
Comment 4 Xuesong Zhang 2018-02-08 03:24:03 UTC
Set the bug to verified since the rebase is done.
Comment 8 errata-xmlrpc 2018-04-10 10:52:40 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0704