Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1140624

Summary: error: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory
Product: Red Hat Enterprise Linux 7 Reporter: Richard W.M. Jones <rjones>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: jdenemar, rbalakri
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-12 06:52:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Richard W.M. Jones 2014-09-11 11:12:51 UTC 
Description of problem:

After installing libvirt 1.2.8-2.el7 *and rebooting*, qemu:///system
sockets are no longer being created.

After login as me:

$ virsh list
error: failed to connect to the hypervisor
error: no valid connection
error: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory

Version-Release number of selected component (if applicable):

libvirt-1.2.8-2.el7.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Update to 1.2.8-2.el7
2. Reboot and log in
3. Try a command (NON-root) such as 'virsh list'

Actual results:

See above.
Comment 1 Richard W.M. Jones 2014-09-11 11:13:52 UTC 
Complete list of packages installed:

libvirt-1.2.8-2.el7.x86_64
libvirt-client-1.2.8-2.el7.x86_64
libvirt-daemon-1.2.8-2.el7.x86_64
libvirt-daemon-config-network-1.2.8-2.el7.x86_64
libvirt-daemon-config-nwfilter-1.2.8-2.el7.x86_64
libvirt-daemon-driver-interface-1.2.8-2.el7.x86_64
libvirt-daemon-driver-lxc-1.2.8-2.el7.x86_64
libvirt-daemon-driver-network-1.2.8-2.el7.x86_64
libvirt-daemon-driver-nodedev-1.2.8-2.el7.x86_64
libvirt-daemon-driver-nwfilter-1.2.8-2.el7.x86_64
libvirt-daemon-driver-qemu-1.2.8-2.el7.x86_64
libvirt-daemon-driver-secret-1.2.8-2.el7.x86_64
libvirt-daemon-driver-storage-1.2.8-2.el7.x86_64
libvirt-daemon-kvm-1.2.8-2.el7.x86_64
libvirt-devel-1.2.8-2.el7.x86_64
libvirt-docs-1.2.8-2.el7.x86_64
ocaml-libvirt-0.6.1.2-10.el7.x86_64
ocaml-libvirt-devel-0.6.1.2-10.el7.x86_64
Comment 2 Richard W.M. Jones 2014-09-11 11:14:52 UTC 
If I start libvirtd by hand, the socket is created, ie.

$ libvirtd &
$ ll /run/user/1000/libvirt/
total 4
drwx------. 2 rjones rjones 40 Sep 11 12:14 hostdevmgr
-rw-r--r--. 1 rjones rjones  4 Sep 11 12:14 libvirtd.pid
srwx------. 1 rjones rjones  0 Sep 11 12:14 libvirt-sock
drwxrwxr-x. 3 rjones rjones 60 Sep 11 12:14 network
drwxrwxr-x. 3 rjones rjones 60 Sep 11 12:14 qemu

and virsh etc works.
Comment 4 Jiri Denemark 2014-09-12 06:52:39 UTC 
That's just the same problem as is already described in bug 1138604. The code that is support to autostart libvirtd in session mode does not create the directory in which the socket is supposed to be created.

*** This bug has been marked as a duplicate of bug 1138604 ***