From 82612a29ced090d76e02a0bb944276d8579b9f0a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Reni=C3=A9?= Date: Fri, 13 Mar 2026 12:26:57 +0100 Subject: [PATCH] docs: Drop mention of aes-256-cbc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This is most likely referring to past qemu-img behavior. Defaults are not encoded in libvirt. `qemu-img` behavior is runtime-dependent, with a current preference towards 'aes-256-xts'. Signed-off-by: Bruno Renié --- docs/formatstorageencryption.rst | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/formatstorageencryption.rst b/docs/formatstorageencryption.rst index 066d285090..f5883da1a3 100644 --- a/docs/formatstorageencryption.rst +++ b/docs/formatstorageencryption.rst @@ -64,10 +64,8 @@ expected (except for the case of RBD layered encryption mentioned above). For volume creation, it is possible to specify the encryption algorithm used to encrypt the luks volume. The following two optional elements may be provided for that purpose. It is hypervisor dependent as to which algorithms are supported. -The default algorithm used by the storage driver backend when using qemu-img to -create the volume is 'aes-256-cbc' using 'essiv' for initialization vector -generation and 'sha256' hash algorithm for both the cipher and the -initialization vector generation. +If no cipher elements are provided, the storage driver backend will use +qemu-img's default encryption settings. ``cipher`` This element describes the cipher algorithm to be used to either encrypt or