Le 18/08/2022 à 14:48, Peter Krempa a écrit :
Hi,
I'm fairly certain that the above is because of Apparmor. Specifically
the apparmor labelling code does not translate the pool/volume name to
the path to the image, while for other security drivers we use the
existing definition and thus do trans
On Tue, Aug 16, 2022 at 13:51:20 +0200, Frédéric Lespez wrote:
> Hi,
>
> I have progressed in my research.
>
> I created a minimal test case in order to reproduce the problem (see below).
>
> I made tests on 3 (physical) machines under Debian 11.4: the problem is
> present on 2 machines but ther
Hi,
I have progressed in my research.
I created a minimal test case in order to reproduce the problem (see below).
I made tests on 3 (physical) machines under Debian 11.4: the problem is
present on 2 machines but there is no problem on the third.
I booted a machine where the problem is prese
Hi,
I need some help to debug a problem with libvirt and a disk device of
type 'volume'.
I have a VM failing to start with the following error :
$ virsh -c qemu:///system start server
error :Failed to start domain 'server'
error :internal error: process exited while connecting to monitor:
202
