qcow2 snapshot should specify backing_fmt=qcow2 for apparmor to work properly
|Assignee:||Javi Fontan||% Done:|
|Category:||Drivers - VM|
|Target version:||Release 5.4|
|Affected Versions:||OpenNebula 4.14, OpenNebula 5.0, OpenNebula 5.2|
When using apparmor with kvm libvirt traverse all backing files with known format to create dynamic apparmor profile.
But in case it doesn't know format it stops traversing and doesn't add them.
Look https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/696318 for more details.
To reproduce we can create a VM from qcow2 datastore, then poweroff, then create disk snapshot, then start again - it fails.
We added -o backing_fmt=qcow2 to qcow2/clone, qcow2/snap_create and qcow2/snap_revert and it works properly.
#4 Updated by Vlastimil Holer about 3 years ago
- Status changed from New to Closed
- Resolution set to fixed
We have fixed everything we could in the code.
There can be still problem with hot-attach of the nonpersistent disk due to the wrong AppArmor profile (https://bugzilla.redhat.com/show_bug.cgi?id=1361592).