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): operation="open" pid=12022 parent=12021 profile="libvirt-9b026ac6-0e31-816c-580f-3af18fe5d375" requested_mask="::r" denied_mask="::r" fsuid=0 ouid=1000 name="/tmp/test-ro2.img" Nov 3 10:49:06 wasabi kernel: [88934.163494] type=1505 audit(1257241746.714:1889): operation="profile_remove" pid=12038 name=libvirt-9b026ac6-0e31-816c-580f-3af18fe5d375 namespace=default
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(125724171 6.474:1888) : operation="open" pid=12022 parent=12021 profile= "libvirt- 9b026ac6- 0e31-816c- 580f-3af18fe5d3 75" requested_ mask=": :r" denied_mask="::r" fsuid=0 ouid=1000 name="/ tmp/test- ro2.img" 6.714:1889) : operation= "profile_ remove" pid=12038 name=libvirt- 9b026ac6- 0e31-816c- 580f-3af18fe5d3 75 namespace=default
Nov 3 10:49:06 wasabi kernel: [88934.163494] type=1505 audit(125724174