[Bug 1187219] New: virtlogd cannot read token due to SElinux
http://bugzilla.opensuse.org/show_bug.cgi?id=1187219 Bug ID: 1187219 Summary: virtlogd cannot read token due to SElinux Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: gm.venekamp@quicknet.nl QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This bug is might be related to: https://bugzilla.redhat.com/show_bug.cgi?id=1964317 virsh start <vm> gives a permission error on: /run/libvirt/common/system.token This is confirmed by: # systemctl status virtlogd.service ��� virtlogd.service - Virtual machine log manager Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect; vendor preset: disabled) Active: active (running) since Wed 2021-06-09 03:31:21 CEST; 2 days ago TriggeredBy: ��� virtlogd-admin.socket ��� virtlogd.socket Docs: man:virtlogd(8) https://libvirt.org Main PID: 1968 (virtlogd) Tasks: 1 (limit: 19660) CPU: 16ms CGroup: /system.slice/virtlogd.service ������1968 /usr/sbin/virtlogd Jun 09 03:31:21 galadriel systemd[1]: Started Virtual machine log manager. Jun 09 03:31:21 galadriel virtlogd[1968]: libvirt version: 7.4.0 Jun 09 03:31:21 galadriel virtlogd[1968]: hostname: xxxxxxxx Jun 09 03:31:21 galadriel virtlogd[1968]: Unable to open system token /run/libvirt/common/system.token: Permission denied Disabling SElinux solves the error and virtlogd is started correctly. After which virsh is able to start VMs successfully. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187219 http://bugzilla.opensuse.org/show_bug.cgi?id=1187219#c1 --- Comment #1 from G.M. Venekamp <gm.venekamp@quicknet.nl> --- Any update on how libvirt can be used used together with SELinux? For the last month after each transactional update If have been logging into the server where the VMs are hosted in order to: disable SELinux and restart virtlogd. At this point I am able to restart the stopped VMs that should have been running. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com