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.
+++ This bug was initially created as a clone of Bug #1290357 +++
Hi,
After provisioning a Beaker machine with a nightly RHEL7.3 and following this[1] guide to deploy an OpenStack allinone setup, I couldn't instantiate a VM. Turned out the issue was a missing virtlogd process which was not started/enabled by packstack or whatever instance is responsible.
Same problem exists for Fedora (bug 1290357), and people seem to be undecided whether libvirt should enable and start virtlogd after installation or qemu.conf should be changed to not require virtlogd. Another alternative seems to be socket activation, so virtlogd starts when it's needed.
I haven't found a ticket for RHEL7, therefore I'm cloning the Fedora one here. Also I'm not sure which is the best solution and which component is ultimately responsible, so filing for libvirt is merely a wild guess (sorry if I'm wrong). But I'm quite sure that just having a customer portal entry[2] suggesting to start and enable virtlogd to fix things up is not ideal when it comes to user experience - especially since the guide in [1] does not mention it.
Thanks, Phil
[1] https://access.redhat.com/products/red-hat-enterprise-linux-openstack-platform/get-started
[2] https://access.redhat.com/solutions/1443193
Hi Jan
My guest still can't start up due to error "Failed to connect socket to '/var/run/libvirt/virtlogd-sock'" after this fix.
Could you help to have a look? Thank you!
The steps are:
1. Install libvirt packages on host freshly
# yum install libvirt-*
2. # systemctl start libvirtd
3. # virsh start rhel7.3-0817
error: Failed to start domain rhel7.3-0817
error: Failed to connect socket to '/var/run/libvirt/virtlogd-sock': No such file or directory
4. I checked 90-default.preset file:
# tail -4 /usr/lib/systemd/system-preset/90-default.preset
# virtlog.service is sometimes used by VMs started by libvirt.service
# Enable virtlog.socket to have it socket activated
# https://bugzilla.redhat.com/show_bug.cgi?id=1325503
enable virtlogd.socket
5. virtlogd.socket is inactive:
# systemctl status virtlogd.socket
● virtlogd.socket - Virtual machine log manager socket
Loaded: loaded (/usr/lib/systemd/system/virtlogd.socket; enabled; vendor preset: enabled)
Active: inactive (dead)
Listen: /var/run/libvirt/virtlogd-sock (Stream)
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.
https://rhn.redhat.com/errata/RHEA-2016-2143.html