Both qemu-kvm and libvirt have created subpackages to provide for smaller installations and faster startup. This BZ is for OpenStack to track this work and make whatever adjustments you deem necessary to your own packaging and dependencies on libvirt and qemu-kvm. +++ This bug was initially created as a clone of Bug #1425820 +++ We now have modularization of the block layer in QEMU (bug #1378536) and libvirt (bug #1378540), but the QEMU packaging layout in RHEL might need changes for us to fully benefit from the changes. For example, it should be possible to install QEMU without Gluster or Ceph block drivers (each brings a large number of dependencies). BTW, I have not investigated this, but I have a report from Peter Krempa (libvirt) that "QEMU still can't be installed without gluster". I'm opening this BZ to request further investigation on what can be improved or changed in our packaging layout. +++ This bug was initially created as a clone of Bug #1378536 +++ The reason to modularize the block layer in QEMU is to allow smaller/minimal installations of QEMU, with two primary use-cases: 1. Allow the split of the QEMU package, bringing less dependencies to a minimal installation. This is particularly important for the case of remote storage drivers, such as Ceph and Gluster, which usually link to and require external libraries and tools. 2. Faster startup of QEMU, with less drivers to load. [...]
oVirt doesn't use qemu-kvm This should be either closed in favor of 1478479 covering oVirt on RHEL and CentOS, or a different bug should be opened for upstream vdsm on Fedora
(In reply to Michal Skrivanek from comment #3) > oVirt doesn't use qemu-kvm NB Although Jeff wrote "qemu-kvm" in the initial description, he actually meant "qemu-kvm-rhev", per the linked BZ
qemu-kvm is correct because BZ 1425820 has been targeted for a later release. That being said, this does appear to be a duplicate of BZ 1478479.
closing per comment #5 *** This bug has been marked as a duplicate of bug 1478479 ***
Re-targeting to 4.4.0 being marked as duplicate of bug #1478479 which is closed in 4.4.0.