From nobody Tue Feb 10 02:43:13 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1648469483; cv=none; d=zohomail.com; s=zohoarc; b=MLracTHuaaO/N1De2ATdeorTTWTVDO+2+n6H2i/6s0x/6tVFik8YqWgWjAAeV1z5Vy9V1uHw3I8Gov7N8qmQWoYkDp6cIgWOzbaounpJN9cGww4/p99vC/VlJlet9mFZ3FNu3b9gX7RxSr3s+5QVVAAhA1wgSjin2yWBoasIP8U= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1648469483; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=6dtOTpyz6wdNfJCCvHK9tj+FqycyyMVpNmLSw8C9gvM=; b=Z+Z9qoi7lhooqBoQxl0CXGf60XEenvsxbNYQJ6PhvgKXmGE9EOGjWm3aC/rJKQrKjeuMEqmnzX9e9BdpPH7100AO4sT8Y4V/KUT8QH/RyLY622YWEkt2qVYt7N6B8FtLqUTIvsje4wLXLiLvYnqO0sahsasTZVK+QbgfLHoqnI0= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.zohomail.com with SMTPS id 1648469483564941.8624455861546; Mon, 28 Mar 2022 05:11:23 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-498-SZY7q7wAN_iJv8w-wi1fkQ-1; Mon, 28 Mar 2022 08:11:20 -0400 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 48D04899EC1; Mon, 28 Mar 2022 12:11:17 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2E15B401E90; Mon, 28 Mar 2022 12:11:17 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id BA2361949762; Mon, 28 Mar 2022 12:11:16 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 91EA01940355 for ; Mon, 28 Mar 2022 12:11:10 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 8474A1402648; Mon, 28 Mar 2022 12:11:10 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.35]) by smtp.corp.redhat.com (Postfix) with ESMTP id 069311402427 for ; Mon, 28 Mar 2022 12:11:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1648469482; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=6dtOTpyz6wdNfJCCvHK9tj+FqycyyMVpNmLSw8C9gvM=; b=CubXCpylIgu6e+it8PQuD+v77yl2lI3Il2H7/Oz3zVzsLqPMestocMk+0boJAj8vyD4mtD PtGSYk/sp8a6QGsa4nxtR7r7AbD8M1Zqt+/ef667xJ9jUK8nxoraq1T8H2VeNdklPrDrfO t47zdrHinj8czy6f3fKrGn9cwAfUkRI= X-MC-Unique: SZY7q7wAN_iJv8w-wi1fkQ-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 24/29] docs: formatstorageencryption: Re-style encryption type headers Date: Mon, 28 Mar 2022 14:10:39 +0200 Message-Id: <44252eb4a117562d46335f670a6a097c882c986a.1648469356.git.pkrempa@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1648469484279100001 Content-Type: text/plain; charset="utf-8"; x-default="true" Use backticks to force monospace font instead of double quotes. Signed-off-by: Peter Krempa Reviewed-by: Erik Skultety --- docs/formatstorageencryption.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/formatstorageencryption.rst b/docs/formatstorageencryptio= n.rst index 1c7227040e..11bea53cb8 100644 --- a/docs/formatstorageencryption.rst +++ b/docs/formatstorageencryption.rst @@ -40,8 +40,8 @@ Alternatively, if supported by the particular volume form= at and driver, automatically generate a secret value at the time of volume creation, and = store it using the specified ``uuid``. -"qcow" format -~~~~~~~~~~~~~ +``qcow`` format +~~~~~~~~~~~~~~~ :since:`Since 4.5.0,` encryption formats ``default`` and ``qcow`` may no l= onger be used to create an encrypted volume. Usage of qcow encrypted volumes in = QEMU @@ -49,8 +49,8 @@ began phasing out in QEMU 2.3 and by QEMU 2.9 creation of= a qcow encrypted volume via qemu-img required usage of secret objects, but that support was= not added to libvirt. -"luks" format -~~~~~~~~~~~~~ +``luks`` format +~~~~~~~~~~~~~~~ The ``luks`` format is specific to a luks encrypted volume and the secret = is used in order to either encrypt during volume creation or decrypt the volu= me for @@ -94,8 +94,8 @@ initialization vector generation. An optional hash algorithm such as 'md5', 'sha1', 'sha256', etc. Sup= port of the specific ivgen hash algorithm is hypervisor dependent. -"luks2" format -~~~~~~~~~~~~~~ +``luks2`` format +~~~~~~~~~~~~~~~~ The ``luks2`` format is currently supported only by the ``librbd`` engine,= and can only be applied to RBD network disks (RBD images). Since the ``librbd`` --=20 2.35.1