Score:1

Apparmor and libvirt - warnings and errors

va flag

I have a fresh Debian 12 installed and updated. Along with Cockpit and Cockpit virtual machines.

I am getting the following errors and warning when looking at the log section in Cockpit:

Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied libvirtd

Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied libvirtd

Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied libvirtd

The virtual machines start up and has no issues. However, the errors pop up after every reboot once I click the virtual machines section on Cockpit. These errors only show then, and not when I do not go to virtual machines section in Cockpit. So it seems to only start once you go to that section in Cockpit.

Has anyone else experience this issue? It gives exactly the same warnings / errors on Ubuntu 22.04 as well.

djdomi avatar
za flag
you may edit the profile to add an allow read to the profile. apparmor restrict this.
Jaromanda X avatar
ru flag
@djdomi - *edit the profile to add an allow read to the profile* - I'm sure this is meaningful to you, but it's not
Clicker85 avatar
va flag
Profile /etc/apparmor.d/usr.sbin.libvirtd is giving access to /sys/kernel/apparmor/profiles r,. Yet, error messages still show up in log.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.