There are other reasons this could trigger, but one is e.g. adding e.g. a disk
with:
<source file='/var/lib/libvirt/images/break,^*[]", foo"me.qcow'/>
You need to create the file or libvirt will detect and exit before that.
$ sudo qemu-img create -f qcow2 '/var/lib/libvirt/images/break,^*[]",
foo"me.qcow' 10M
Error (on most recent libvirt) is like:
error: Failed to start domain c
error: internal error: cannot load AppArmor profile
'libvirt-8763795d-f056-4373-9d57-3d3bad391e5a'
The same used as hotplug device will trigger:
error: Failed to attach device from disk.xml
error: internal error: cannot update AppArmor profile
'libvirt-8763795d-f056-4373-9d57-3d3bad391e5a'
I have found no way with recent versions to get the misleading pointer to the
"qemu-... does not exists".
Setting incomplete.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Incomplete
** Tags removed: libvirt-18.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767934
Title:
breaking the apparmor profile leads to misleading error messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767934/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
