diff options
| author | Peter Krempa <pkrempa@redhat.com> | 2022-05-13 10:31:38 +0200 |
|---|---|---|
| committer | Peter Krempa <pkrempa@redhat.com> | 2022-06-01 12:27:10 +0200 |
| commit | a781f7980c450916f39fc3b50a3325fe9297c464 (patch) | |
| tree | 4d3f06b9fef5b19c44bd2c3fcb3b61ff85e21751 /docs/kbase | |
| parent | e8cdf37ebf4d00e38b428251d631ccd64a97a572 (diff) | |
| download | libvirt-a781f7980c450916f39fc3b50a3325fe9297c464.tar.gz | |
docs: formatdomain: Remove 'launchSecurity' anchor
Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Diffstat (limited to 'docs/kbase')
| -rw-r--r-- | docs/kbase/launch_security_sev.rst | 2 | ||||
| -rw-r--r-- | docs/kbase/s390_protected_virt.rst | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/kbase/launch_security_sev.rst b/docs/kbase/launch_security_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 ================ SEV is enabled in the XML by specifying the -`<launchSecurity> <https://libvirt.org/formatdomain.html#launchSecurity>`__ +`<launchSecurity> <https://libvirt.org/formatdomain.html#launch-security>`__ 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 -`<launchSecurity> <https://libvirt.org/formatdomain.html#launchSecurity>`__ +`<launchSecurity> <https://libvirt.org/formatdomain.html#launch-security>`__ element with type ``s390-pv`` should be used on protected virtualization guests. Without ``launchSecurity`` you must enable all virtio devices to use shared buffers by configuring them with platform_iommu enabled. |