Bug 1352263

Summary: qemu:///session connections don't get virtlogd started by user's libvirtd
Product: [Fedora] Fedora Reporter: Dimitris <dimitris.on.linux>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: agedosier, berrange, clalancette, itamar, laine, libvirt-maint, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-04 08:41: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 Dimitris 2016-07-03 05:09:53 UTC 
Description of problem:

Just updated F23 to F24, so libvirt upgraded from 1.2 to 1.3.  I have been using a couple of work VMs on this system, both under the qemu:///session connection.

When I try to start a guest, I get this error:

error: Failed to start domain <name>
error: Failed to connect socket to '/run/user/1000/libvirt/virtlogd-sock': Connection refused

I can work around this by manually running virtlogd (will probably write a user unit file, if I can figure that out, so I don't have to remember to do that every time)

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

1.3.3.1-4.fc24

How reproducible:

every time

Steps to Reproduce:
1. Start a qemu:///session guest
2. Guests fail to start with the error above

Actual results:

Requires workaround: manually run virtlogd

Expected results:

This is a regression, previously (under 1.2, so presumably no virtlogd dependency) no such workaround was necessary.

Additional info:

There is actually one more stumbling block (an apparent capabilities problem) which I have to work around before the guest can start.  Once I have that bug entered I'll cross-reference both of them.
Comment 1 Dimitris 2016-07-03 05:17:53 UTC 
For completeness, the other regression I mentioned in the description is in bug 1352265.
Comment 2 Daniel Berrangé 2016-07-04 08:41:39 UTC 
Failure to start virtlogd is caused by broken audit-libs - you must have 2.6.2 or 2.6, but *not* 2.6.1 which is fubar

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