The offline validation example needs to include the firmware path, and is also missing line continuation markers.
Signed-off-by: Daniel P. Berrangé <[email protected]> --- docs/kbase/launch_security_sev.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) 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 -- 2.39.2
