From: Daniel P. Berrangé <berrange@redhat.com>
Date: Thu, 16 Feb 2023 15:51:03 +0000 (+0000)
Subject: docs/kbase: fix example for SEV validation
X-Git-Tag: v9.1.0-rc1~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9541ce080a0896411bebb299f47e39112810a648;p=thirdparty%2Flibvirt.git

docs/kbase: fix example for SEV validation

The offline validation example needs to include the firmware path,
and is also missing line continuation markers.

Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---

diff --git a/docs/kbase/launch_security_sev.rst b/docs/kbase/launch_security_sev.rst
index 7f692af748..f3c8695f73 100644
--- a/docs/kbase/launch_security_sev.rst
+++ b/docs/kbase/launch_security_sev.rst
@@ -465,12 +465,13 @@ scope of this document. Fortunately, libvirt provides a tool that can be used
 to perform this validation::
 
   $ virt-qemu-sev-validate \
-      --measurement LMnv8i8N2QejezMPkscShF0cyPYCslgUoCxGWRqQuyt0Q0aUjVkH/T6NcmkwZkWp
-      --api-major 0
-      --api-minor 24
-      --build-id 15
-      --policy 3
-      --tik ${myvmname}_tik.bin
+      --measurement LMnv8i8N2QejezMPkscShF0cyPYCslgUoCxGWRqQuyt0Q0aUjVkH/T6NcmkwZkWp \
+      --api-major 0 \
+      --api-minor 24 \
+      --build-id 15 \
+      --policy 3 \
+      --firmware /path/to/OVMF.sev.fd \
+      --tik ${myvmname}_tik.bin \
       --tek ${myvmname}_tek.bin
   OK: Looks good to me