RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
For consistency with the upstream format it might be preferable to backport the vdsm configuration for libvirt.

Version-Release number of selected component (if applicable):
vdsm-4.9.6-34.0.el6_3

Upstream patches:
7065d0c BZ#821867: Do not append comments to config values
706f8d9 Configure libvirt to use sanlock

With the new patches the libvirt config files (/etc/libvirt/libvirtd.conf, /etc/libvirt/qemu.conf, /etc/libvirt/qemu-sanlock.conf) will contain a section for the vdsm configuration as:

## beginning of configuration section by vdsm-4.9.10
...
## end of configuration section by vdsm-4.9.10

Instead of the previous "# by vdsm" comments appended at the end of each line.

libvird.conf:

## beginning of configuration section by vdsm-4.9.6.1
listen_addr="0.0.0.0"
unix_sock_group="kvm"
unix_sock_rw_perms="0770"
auth_unix_rw="sasl"
host_uuid="526bcc25-e834-4004-8d2b-eafc3eff1f1d"
save_image_format="lzop"
log_outputs="1:file:/var/log/libvirtd.log"
log_filters="1:libvirt 3:event 3:json 1:util 1:qemu"
ca_file="/etc/pki/vdsm/certs/cacert.pem"
cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
## end of configuration section by vdsm-4.9.6.1

qemu-sanlock.conf:

## beginning of configuration section by vdsm-4.9.6.1
auto_disk_leases=0
require_lease_for_disks=0
## end of configuration section by vdsm-4.9.6.1

qemu.conf:

## beginning of configuration section by vdsm-4.9.6.1
dynamic_ownership=0
spice_tls=1
spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice"
## end of configuration section by vdsm-4.9.6.1

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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html