From nobody Mon Feb 9 11:07:21 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.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.129.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=1654009815; cv=none; d=zohomail.com; s=zohoarc; b=Wzfmpo6amR8uMeTKYiI4b67ADeKzkBtNBb7E78uTh0T7wt57s9wSUtiDybWIbXWm9qg32uk+ED/6w8RdJd71pv2m7ma40XWEitBc6cHK7L5XJRuKrIkGPyLVYp0/tUDklR8sdz3md3HT4VerpwS3X0lhnKFEqoxC2jYFZFYAqns= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1654009815; 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=DWBfmXk3hyr4Y3J+YgycgbzHjLzD5ZY/b7OMpnEG0Xg=; b=A14wDJE6mrh/b45KzXr6BdQPbM5P34CevcXmk6HYfJtFe6oUhB+5fjsKxR1sB5bBXNKXuwnuBb9Fqh+wF00hHoO3hAEQCrYqinLZNrZDxYJkOOufC8pAbimZ02cGDrV3BEpktSHCf5Aq1DD4ilcAl7vlKdENJVl+NQoGhHqIuOE= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.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.129.124]) by mx.zohomail.com with SMTPS id 1654009815294658.3668160488908; Tue, 31 May 2022 08:10:15 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-441-XYyKyE8RPzKNT7sDDDrrnQ-1; Tue, 31 May 2022 11:08:46 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 664FF3979692; Tue, 31 May 2022 15:07:29 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 52D9CC27E92; Tue, 31 May 2022 15:07:29 +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 1B15F1947071; Tue, 31 May 2022 15:07:29 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 4CDA3194705C for ; Tue, 31 May 2022 15:07:25 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 2EB961731B; Tue, 31 May 2022 15:07:25 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.21]) by smtp.corp.redhat.com (Postfix) with ESMTP id A537610725 for ; Tue, 31 May 2022 15:07:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654009814; 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=DWBfmXk3hyr4Y3J+YgycgbzHjLzD5ZY/b7OMpnEG0Xg=; b=bR2ZEbcZiXLMobF35cxryc9/0VW2incuHG7iEM9RdcOZf5wBdXa8K82RY9vvx2xRfInxNE 7I+zmJUJGRo6BUo/cnDc+g0b7I8F7VfcYb4ToCfAmpCuICqljAprxmdeLjWwJhoGo5ysUC FMfP4afl2bXaXkt0lg0Z9X9NQBE2kUU= X-MC-Unique: XYyKyE8RPzKNT7sDDDrrnQ-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 49/67] docs: formatdomain: Remove 'launchSecurity' anchor Date: Tue, 31 May 2022 17:06:24 +0200 Message-Id: <2449c2538d08759a54b562ed8a3939e0a0011e23.1654008136.git.pkrempa@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 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.8 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: 1654009815899100005 Content-Type: text/plain; charset="utf-8" Signed-off-by: Peter Krempa --- docs/formatdomain.rst | 1 - docs/formatdomaincaps.rst | 4 ++-- docs/kbase/launch_security_sev.rst | 2 +- docs/kbase/s390_protected_virt.rst | 2 +- 4 files changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index 97c23f6aa6..4868d3c397 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -8177,7 +8177,6 @@ At least one ``cipher`` element must be nested within= the ``keywrap`` element. Note: DEA/TDEA is synonymous with DES/TDES. -:anchor:`` Launch Security --------------- diff --git a/docs/formatdomaincaps.rst b/docs/formatdomaincaps.rst index 7aead08d69..1ff45da6f0 100644 --- a/docs/formatdomaincaps.rst +++ b/docs/formatdomaincaps.rst @@ -568,7 +568,7 @@ s390-pv capability Reports whether the hypervisor supports the Protected Virtualization. In o= rder to use Protected Virtualization with libvirt have a look at the `launchSec= urity -element in the domain XML `__. For more +element in the domain XML `__. For more details on the Protected Virtualization feature please see `Protected Virtualization on s390 `__. @@ -583,7 +583,7 @@ transparently encrypted with a key unique to that VM. For more details on the SEV feature, please follow resources in the AMD developer's document store. In order to use SEV with libvirt have a look a= t `SEV -in domain XML `__ +in domain XML `__ ``cbitpos`` When memory encryption is enabled, one of the physical address bits (ak= a the diff --git a/docs/kbase/launch_security_sev.rst b/docs/kbase/launch_securit= y_sev.rst index 06d1f2dad0..3ebb01ad80 100644 --- a/docs/kbase/launch_security_sev.rst +++ b/docs/kbase/launch_security_sev.rst @@ -154,7 +154,7 @@ VM Configuration =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D SEV is enabled in the XML by specifying the -` `__ +` `= __ element. However, specifying ``launchSecurity`` isn't enough to boot an SEV VM. Further configuration requirements are discussed below. diff --git a/docs/kbase/s390_protected_virt.rst b/docs/kbase/s390_protected= _virt.rst index 4cbdeea7ed..a8c627931b 100644 --- a/docs/kbase/s390_protected_virt.rst +++ b/docs/kbase/s390_protected_virt.rst @@ -128,7 +128,7 @@ As the virtio data structures of secure guests are not = accessible by the host, it is necessary to use shared memory ('bounce buffers'). Since libvirt 7.6.0 the -` `__ +` `= __ element with type ``s390-pv`` should be used on protected virtualization g= uests. Without ``launchSecurity`` you must enable all virtio devices to use shared buffers by configuring them with platform_iommu enabled. --=20 2.35.3