Description of problem: When discussing the use of 'auto-read-only' property for use with -blockdev so that libvirt is able to use block jobs I forgot that sVirt labelling of the backing chain images actually forbids the write permission. [1] This means that the 'auto-read-only' property works as expected and opens the images as read-only in this case. This unfortunately means that when libvirt attempts a block-commit which needs to write into the backing chain we relabel the image to allow write, but qemu will not reopen it any more. This means that we unfortunately still need a way to control reopening of the images of the backing chain: 1) automatically by block-commit doing the right thing 2) manually by providing an interface to achieve that Libvirt is relabeling the files anyways so 2) is also acceptable. [1] Unfortunately it's very unpleasant to run a development git image of libvirt under full enforcing selinux, thus I neglected todo when testing 'auto-read-only'. I'm sorry for that.