Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1140624 - error: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory
Summary: error: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No ...
Keywords:
Status: CLOSED DUPLICATE of bug 1138604
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-11 11:12 UTC by Richard W.M. Jones
Modified: 2014-09-12 06:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-12 06:52:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.