Because this feature is officially supported, can the importance be
updated ?.
I think it should not be defined as a wishlist, actually it's a feature
that no longer works with 9.10.
--
virt-aa-helper fails to add copy-on-write images on apparmor profile
https://bugs.launchpad.net/bugs/470636
Yo
Here is a script that can exactly reproduce the bug.
First, a traditional VM is created and started without problem. Then a
double copy-on-write vm is defined and (not) started.
When can see in the log :
Nov 3 10:48:36 wasabi kernel: [88903.924234] type=1503
audit(1257241716.474:1888): operati
Ok, thanks for the workaround, it should work (I've added them in an
other files, and it works fine).
This command is not the snapshot feature (i.e: not the "kvm snapshot"
command) which I knew was not supported actually.
Based on http://libvirt.org/news.html, copy-on-write is supported since
0.6
** Description changed:
Binary package hint: libvirt-bin
System : Ubuntu 9.10 (x86_64)
Version of libvirt-bin : 0.7.0-1ubuntu13
- When virt-aa-helper add a profile on apparmor, it does check if the QEMU
- disk image is based on a read-only image.
+ When virt-aa-helper add a profile on
Public bug reported:
Binary package hint: libvirt-bin
System : Ubuntu 9.10 (x86_64)
Version of libvirt-bin : 0.7.0-1ubuntu13
When virt-aa-helper add a profile on apparmor, it does check if the QEMU
disk image is based on a read-only image.
This command create a copy-on-write image system.img ba