Hi, Today I solved a similar issue on my machine, or at least something that was manifesting with the same error message.
The original problem is that my VM was referring to a file missing from disk, the XML definition was valid but the VM was not. This made some libvirtd child process die and, for reasons I ignore, failed the AppArmor profile validation. This is from syslog: Jul 21 12:36:55 r9 libvirtd[1129]: internal error: Child process (LIBVIRT_LOG_OUTPUTS=3:stderr /usr/lib/libvirt/virt-aa-helper -c -u libvirt-ae75c26b-557a-4772-afe0-f820cfcdf410) unexpected exit status 1: virt-aa-helper: warning: path does not exist, skipping file type checks#012virt-aa-helper: error: /usr/share/AAVMF/AAVMF_VARS.fd#012virt-aa-helper: error: skipped restricted file#012virt-aa-helper: error: invalid VM definition Jul 21 12:36:55 r9 libvirtd[1129]: internal error: cannot load AppArmor profile 'libvirt-ae75c26b-557a-4772-afe0-f820cfcdf410' Therefore if you get this "cannot load AppArmor profile" error, look for the actual error in /var/log/syslog. I also suggest to close this bug, it's of the kind catch-all and cannot be solved in any way. Dom -- rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
signature.asc
Description: PGP signature
