It's an important limitation that can be tuned in firmware settings on
most machines.

While there, provide update dmesg output that includes SEV-SNP.

Signed-off-by: Christian Ludwig <christian_ludwig@genua.de>
---
 qm.adoc | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/qm.adoc b/qm.adoc
index 5b46cdc..37950fc 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -842,14 +842,20 @@ the SEV kernel parameter of kvm_amd:
 
 ----
 # dmesg | grep -i sev
+[...] SEV-SNP: RMP table physical range [<range>]
 [...] ccp 0000:45:00.1: sev enabled
+[...] ccp 0000:45:00.1: SEV-SNP API: <buildversion>
 [...] ccp 0000:45:00.1: SEV API: <buildversion>
-[...] SEV supported: <number> ASIDs
-[...] SEV-ES supported: <number> ASIDs
+[...] SEV enabled (ASIDs ...)
+[...] SEV-ES enabled (ASIDs ...)
+[...] SEV-SNP enabled (ASIDs ...)
 # cat /sys/module/kvm_amd/parameters/sev
 Y
 ----
 
+The number of ASIDs gives the maximum number of confidential guests for each
+type that can run in parallel.
+
 *Guest Requirements:*
 
 * edk2-OVMF
-- 
2.34.1