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:
After configuration qemu-lockd.conf , libvirtd will fail to restart because error
Failed to connect socket to '/var/run/libvirt/virtlockd-sock': No such file or directory
,but the socket file is named virtlockd.sock and located at
/var/run/libvirt/virtlockd/virtlockd.sock 

Version-Release number of selected component (if applicable):
libvirt-1.0.5-2.el7.x86_64
qemu-kvm-1.5.0-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
#systemctl start virtlockd.service

2.
#tail -1 /etc/libvirt/qemu.conf
lock_manager = "lockd"

#tail -3 /etc/libvirt/qemu-lockd.conf
auto_disk_leases = 1
require_lease_for_disks = 1
file_lockspace_dir = "/var/lib/libvirt/lockd/files"

3.
#systemctl restart libvirtd.service
libvirtd wil report error below and can't start
Failed to connect socket to '/var/run/libvirt/virtlockd-sock': No such file or directory

Actual results:
the function doesn't work

Expected results:
can use

I proposed a patch changing the socket path in the systemd config file:
https://www.redhat.com/archives/libvir-list/2013-June/msg00085.html

The socket path fix is now pushed upstream:

commit 70fe129546545f9683ce57e6946dd80a08b54d2b
Author:     Ján Tomko <jtomko>
AuthorDate: 2013-06-04 13:36:56 +0200
Commit:     Ján Tomko <jtomko>
CommitDate: 2013-06-05 10:17:28 +0200

    virtlockd: fix socket path
    
    Change the socket path to match the one used by lockd driver.

But it still fails with selinux enabled:
Jun  5 07:41:51 456rhel setroubleshoot: SELinux is preventing /usr/sbin/libvirtd from connectto access on the unix_stream_socket /run/libvirt/virtl
ockd-sock. For complete SELinux messages. run sealert -l 8ab78190-8e08-45f5-8d2e-02862d493dea

Now , the virtlockd can start and no selinux's issue with packages
selinux-policy-3.12.1-56.el7.noarch
libvirt-1.1.0-1.el7.x86_64 , 

But when generate lease file , the virtlockd's daemon will show
End of file while reading data: Input/output error , 

and no related file or directory created. I will file another bug for it later, 
and set this one Verify first.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.