From 8e02fa2e257b84d7e546d0b30a86373f27703289 Mon Sep 17 00:00:00 2001
From: Erik Skultety <eskultet@redhat.com>
Date: Fri, 20 Sep 2019 13:47:09 +0200
Subject: [PATCH] docs: kbase: Add a section explaining how to verify SEV from
 the guest
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

Commit 50dfabbb59 forgot to add this important bit on how to check that
all the changes to the XML actually worked.

Signed-off-by: Erik Skultety <eskultet@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
---
 docs/kbase/launch_security_sev.html.in | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/kbase/launch_security_sev.html.in b/docs/kbase/launch_security_sev.html.in
index 923bb52b25..985c11a47b 100644
--- a/docs/kbase/launch_security_sev.html.in
+++ b/docs/kbase/launch_security_sev.html.in
@@ -349,6 +349,18 @@ EOF</pre>
   ...
 &lt;/domain&gt;</pre>
 
+    <h2><a id="Guest">Checking SEV from within the guest</a></h2>
+    <p>
+        After making the necessary adjustments discussed in
+        <a href="#Configuration">Configuration</a>, the VM should now boot
+        successfully with SEV enabled. You can then verify that the guest has
+        SEV enabled by running:
+    </p>
+
+    <pre>
+# dmesg | grep -i sev
+AMD Secure Encrypted Virtualization (SEV) active</pre>
+
     <h2><a id="Limitations">Limitations</a></h2>
     <p>
         Currently, the boot disk cannot be of type virtio-blk, instead, virtio-scsi
-- 
2.47.2