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.
Are you sure nothing is missing in the reproducer? I've got an almost identical environment (slightly more recent qemu build), but I'm not able to reproduce this issue, I've got a VM running, virtlogd running and it reloads without any issues.
So I tried on my 7.5 machine with selinux-policy-3.13.1-192 and I can't reproduce with upstream. At the same time, with selinux-policy-3.13.1-207 onwards, I'm hitting permission denied on virtlogd reload on older releases of libvirt too. Therefore, moving this to selinux-policy component.
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://access.redhat.com/errata/RHBA-2018:3111
Description of problem: virtlogd.service entered failed state with "Permission denied" error after reload Version-Release number of selected component (if applicable): libvirt-4.5.0-1.el7.x86_64 qemu-kvm-rhev-2.12.0-7.el7.x86_64 selinux-policy-3.13.1-207.el7.noarch How reproducible: 100% Steps to Reproduce: 1.Check virtlogd.service is running # systemctl status virtlogd -l ● virtlogd.service - Virtual machine log manager Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect; vendor preset: disabled) Active: active (running) since Thu 2018-07-05 05:45:26 EDT; 11s ago Docs: man:virtlogd(8) https://libvirt.org Main PID: 11946 (virtlogd) Tasks: 1 CGroup: /system.slice/virtlogd.service └─11946 /usr/sbin/virtlogd 2.# systemctl reload virtlogd 3.# systemctl status virtlogd -l ● virtlogd.service - Virtual machine log manager Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2018-07-05 05:46:01 EDT; 1s ago Docs: man:virtlogd(8) https://libvirt.org Process: 11990 ExecReload=/bin/kill -USR1 $MAINPID (code=exited, status=0/SUCCESS) Process: 11946 ExecStart=/usr/sbin/virtlogd $VIRTLOGD_ARGS (code=exited, status=9) Main PID: 11946 (code=exited, status=9) Jul 05 05:45:26 hp-***.redhat.com systemd[1]: Started Virtual machine log manager. Jul 05 05:46:01 hp-***.redhat.com systemd[1]: Reloading Virtual machine log manager. Jul 05 05:46:01 hp-***redhat.com systemd[1]: Reloaded Virtual machine log manager. Jul 05 05:46:01 hp-***.redhat.com virtlogd[11946]: 2018-07-05 09:46:01.383+0000: 11946: info : libvirt version: 4.5.0, package: 1.el7 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2018-07-03-10:54:58, x86-039.build.eng.bos.redhat.com) Jul 05 05:46:01 hp-***.redhat.com virtlogd[11946]: 2018-07-05 09:46:01.383+0000: 11946: info : hostname: hp-***.redhat.com Jul 05 05:46:01 hp-***.redhat.com virtlogd[11946]: 2018-07-05 09:46:01.383+0000: 11946: error : virLogDaemonPreExecRestart:865 : Unable to restart self: Permission denied Jul 05 05:46:01 hp-***redhat.com systemd[1]: virtlogd.service: main process exited, code=exited, status=9/n/a Jul 05 05:46:01 hp-***.redhat.com systemd[1]: Unit virtlogd.service entered failed state. Jul 05 05:46:01 hp-***.redhat.com systemd[1]: virtlogd.service failed. 4.start the virtlogd.service and check the status again: ● virtlogd.service - Virtual machine log manager Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect; vendor preset: disabled) Active: active (running) since Thu 2018-07-05 05:50:34 EDT; 2s ago Docs: man:virtlogd(8) https://libvirt.org Process: 11990 ExecReload=/bin/kill -USR1 $MAINPID (code=exited, status=0/SUCCESS) Main PID: 12161 (virtlogd) Tasks: 1 CGroup: /system.slice/virtlogd.service └─12161 /usr/sbin/virtlogd ... Jul 05 05:50:34 hp-***.redhat.com virtlogd[12161]: 2018-07-05 09:50:34.239+0000: 12161: warning : virLogDaemonPostExecRestart:782 : Found restart exec file with old magic 11946 vs wanted 12161 ... Actual results: As in step 3, virtlogd.service entered failed state with "Permission denied" error after reload. And in step4, still a warning after start the service. Expected results: virtlogd.service should be reloaded successfully without error. Additional info: