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.
Description of problem:
virtlogd does not start while staring virtqemud service.
Version-Release number of selected component (if applicable):
libvirt-6.0.0-7.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Disable libvirtd and enable virtqemud service:
#systemctl stop libvirtd.service
#systemctl disable libvirtd{,-ro,-admin,-tcp,-tls}.socket
#systemctl unmask virtqemud.service
#systemctl unmask virtqemud{,-ro,-admin}.socket
#systemctl enable virtqemud.service
#systemctl enable virtqemud{,-ro,-admin}.socket
2.Reboot host
3.Start a guest:
#virsh -c qemu:///system start vm
error: Failed to start domain vm
error: can't connect to virtlogd: Failed to connect socket to '/run/libvirt/virtlogd-sock': No such file or directory
4.Check virtlogd status:
# systemctl status virtlogd
● virtlogd.service - Virtual machine log manager
Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect; vendor preset: disabled)
Active: inactive (dead)
Docs: man:virtlogd(8)
https://libvirt.org
Actual results:
virtlogd should start while starting vritqemud service
Expected results:
vIrtlogd does not start while staring virtqemud service.
Additional info:
The /run/libvirt/virtlogd-sock should be provided by the "virtlogd.socket" system unit.
That should be enabled by default on all RHEL systems. Can you check whether that socket path actually exists on disk current.
If it does exist, then possibly something like SELinux denies access.
There was a SELinux policy update for the daemons required so check that is installed too https://bugzilla.redhat.com/show_bug.cgi?id=1745076
(In reply to Daniel Berrangé from comment #1)
> The /run/libvirt/virtlogd-sock should be provided by the "virtlogd.socket"
> system unit.
>
> That should be enabled by default on all RHEL systems. Can you check
> whether that socket path actually exists on disk current.
>
> If it does exist, then possibly something like SELinux denies access.
>
> There was a SELinux policy update for the daemons required so check that is
> installed too https://bugzilla.redhat.com/show_bug.cgi?id=1745076
I reproduce the issue with the following steps and did not find /run/libvirt/virtlogd-sock.
#systemctl stop libvirtd.service
#systemctl stop libvirtd{,-ro,-admin,-tcp,-tls}.socket
#systemctl disable libvirtd.service
#systemctl disable libvirtd{,-ro,-admin,-tcp,-tls}.socket
#for drv in qemu interface network nodedev nwfilter secret storage proxy; do systemctl unmask virt${drv}d.service; systemctl unmask virt${drv}d{,-ro,-admin}.socket; systemctl enable virt${drv}d.service; systemctl enable virt${drv}d{,-ro,-admin}.socket; done
#reboot
After host boot, check the socket file under /run/libvirt/
#ll /run/libvirt/ | grep -i virtlog
no output
Comment 5RHEL Program Management
2021-09-06 07:27:07 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Fixed upstream in
commit 88c5b9f827779ae6fe5a6f08100a4b6184492a1c
Author: Daniel P. Berrangé <berrange>
Date: Tue Aug 31 10:59:39 2021 +0100
qemu, xen: add missing deps on virtlockd/virtlogd sockets
The QEMU driver uses both virtlogd and virtlockd, while the Xen driver
uses virtlockd. The libvirtd.service unit contains deps on the socket
units for these services, but these deps were missed in the modular
daemons. As a result the virtlockd/virtlogd sockets are not started
when the virtqemud/virtxend daemons are started.
Reviewed-by: Jiri Denemark <jdenemar>
Signed-off-by: Daniel P. Berrangé <berrange>
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 (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2022:1759
Description of problem: virtlogd does not start while staring virtqemud service. Version-Release number of selected component (if applicable): libvirt-6.0.0-7.el8.x86_64 How reproducible: 100% Steps to Reproduce: 1.Disable libvirtd and enable virtqemud service: #systemctl stop libvirtd.service #systemctl disable libvirtd{,-ro,-admin,-tcp,-tls}.socket #systemctl unmask virtqemud.service #systemctl unmask virtqemud{,-ro,-admin}.socket #systemctl enable virtqemud.service #systemctl enable virtqemud{,-ro,-admin}.socket 2.Reboot host 3.Start a guest: #virsh -c qemu:///system start vm error: Failed to start domain vm error: can't connect to virtlogd: Failed to connect socket to '/run/libvirt/virtlogd-sock': No such file or directory 4.Check virtlogd status: # systemctl status virtlogd ● virtlogd.service - Virtual machine log manager Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect; vendor preset: disabled) Active: inactive (dead) Docs: man:virtlogd(8) https://libvirt.org Actual results: virtlogd should start while starting vritqemud service Expected results: vIrtlogd does not start while staring virtqemud service. Additional info: