On Mon, Mar 26, 2018 at 16:43:03 +0200, Michal Privoznik wrote:
> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
> ---
> docs/news.xml | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/docs/news.xml b/docs/news.xml
> index 1088895746..6f1ceb6389 100644
> --- a/docs/news.xml
> +++ b/docs/news.xml
> @@ -94,6 +94,16 @@
> </change>
> </section>
> <section title="Bug fixes">
> + <change>
> + <summary>
> + Improve handling of device mapper targets
> + </summary>
> + <description>
> + When starting a domain with a disk hidden behind
> + devmapper libvirt needs to allow them both in devices
> + CGroup: the devmapper target and the disk.
This does not read very well how about:
When starting a domain with a disk backed by a device-mapper volume
libvirt also needs to allow the storage backing the device mapper in
cgroups.
But that acutally brings me to yet another question: You described the
problem with multipath devices. But given that LVM or dm-crypt would
basically suffer from the same problems it would be great if you also
could figure out the root of the problem. Also it might be interresting
to know if it's similarly happening with multiple layers of
device-mapper volumes since 'dmsetup deps' (and the equivalent algorithm
added in this series) does not resolve the device nodes recursively.
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list