RHBA-2013:1676 - Bug Fix Advisory

Topic

Updated libvirt-cim packages that fix several bugs are now available for Red Hat
Enterprise Linux 6.

Description

The libvirt-cim packages contain a Common Information Model (CIM) provider based
on Common Manageability Programming Interface (CMPI). It supports most libvirt
virtualization features and allows management of multiple libvirt-based
platforms.

This update fixes the following bugs:

• Previously, running the wbemcli utility with the KVM_ComputerSystem class

terminated unexpectedly with a segmentation fault. This was because even when
connecting to the libvirtd daemon read-only, the domain XML with secure
information, that is with the VIR_DOMAIN_XML_SECURE flag, was dumped. However,
this operation is forbidden in libvirt. With this update, the flag is not used
with read-only connections. Running the wbemcli command with KVM_ComputerSystem
now displays the domain information as expected. (BZ#826179)

• When updating certain libvirt-cim or sblim-smis-hba packages, the following

error could have been logged in the /var/log/messages file:

sfcbmof: *** Repository error for
/var/lib/sfcb/registration/repository//root/pg_interop/qualifiers

This problem occurred because libvirt-cim installed the PG_InterOp class
incorrectly in the sblim-sfcb repository, however, this class is specific for
the open-pegasus package. With this update, PG_InterOp is unregistered before
upgrading the package, and no error message is logged in this scenario.
(BZ#833633)

• Previously, libvirt-cim incorrectly installed providers specific for the

open-pegasus package in the sblim-sfcb repository. This could have caused
various problems, for example, failures when compiling the MOF files. Providers
specific for open-pegasus are now installed in the correct repository and the
problems no longer occur. (BZ#859122)

• Previously, if a qemu domain was defined with a bridge network interface,

running the libvirt-cim provider failed with the following error message:

Unable to start domain: unsupported configuration: scripts are are not
supported on interfaces of type bridge

This was because code triggering a script was added in a file used to create the
domain prior to checking the qemu domain type. However, scripts are not allowed
for qemu domains. With this update, a check for the qemu domain type is
performed prior to adding the code triggering the script. As a result, when
using libvirt-cim, it is now possible to create qemu domains with the bridge
network interface. (BZ#908083)

• Previously, a call to query a guest's current VNC address and port number

returned the static configuration of the guest. If the guest was used to enable
the "autoport" selection, the call did not return the allocated port. The
libvirt-cim code has been modified to only return static configuration
information. This allows other interfaces to return information based on the
domain state. As a result, the current and correct port being used by the domain
for VNC is now returned. (BZ#913164)

• Virtual machines managed by a libvirt-cim broker were not aware of the

"dumpCore" flag in the "memory" section nor was there support for the
"shareable" property for "disk" devices. Thus, those properties were dropped
from the virtual machine XML configuration when the configuration was updated by
the broker. As a consequence, customers expecting or setting these properties on
their virtual machines had to adjust the configurations in order to reset them.
With this update, a patch has been added to libvirt-cim and it is now aware of
these properties so that no changes made to the virtual machine XML
configuration will be lost by the broker when it writes the configuration. As a
result, virtual machines managed by the libvirt-cim broker will recognize the
"dumpCore" tag in the "memory" section or the "shareable" tag on a "disk" device
and not remove either when updating the virtual machine XML configuration.
(BZ#1000937)

Users of libvirt-cim are advised to upgrade to these updated packages, which fix
these bugs.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/site/articles/11258

Affected Products

• Red Hat Enterprise Linux Server 6 x86_64
• Red Hat Enterprise Linux Server 6 i386
• Red Hat Enterprise Linux Server - Extended Life Cycle Support 6 i386
• Red Hat Enterprise Linux Workstation 6 x86_64
• Red Hat Enterprise Linux Workstation 6 i386
• Red Hat Enterprise Linux Desktop 6 x86_64
• Red Hat Enterprise Linux Desktop 6 i386
• Red Hat Enterprise Linux for IBM z Systems 6 s390x
• Red Hat Enterprise Linux for Power, big endian 6 ppc64
• Red Hat Enterprise Linux for Scientific Computing 6 x86_64
• Red Hat Enterprise Linux Server from RHUI 6 x86_64
• Red Hat Enterprise Linux Server from RHUI 6 i386
• Red Hat Enterprise Linux Server - Extended Life Cycle Support 6 x86_64
• Red Hat Enterprise Linux Server - Extended Life Cycle Support (for IBM z Systems) 6 s390x
• Red Hat Enterprise Linux Server - Extended Life Cycle Support Extension 6 x86_64
• Red Hat Enterprise Linux Server - Extended Life Cycle Support Extension 6 i386
• Red Hat Enterprise Linux Server - Extended Life Cycle Support Extension (for IBM z Systems) 6 s390x

Fixes

CVEs

(none)

References

(none)