No, I didn't found any apparmor denials - the same is before and the same is after failing guest:
dmesg | grep -i apparmor [ 0.012143] AppArmor: AppArmor initialized [ 0.380003] AppArmor: AppArmor Filesystem Enabled [ 1.234176] AppArmor: AppArmor sha1 policy hashing enabled [ 10.461303] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
I even switched it off by:
systemctl stop apparmor.service
but nothing is changed. Guest is still fails to start.
No, I didn't found any apparmor denials - the same is before and the same is after failing guest:
dmesg | grep -i apparmor
[ 0.012143] AppArmor: AppArmor initialized
[ 0.380003] AppArmor: AppArmor Filesystem Enabled
[ 1.234176] AppArmor: AppArmor sha1 policy hashing enabled
[ 10.461303] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
I even switched it off by:
systemctl stop apparmor.service
but nothing is changed. Guest is still fails to start.