mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-22 21:55:25 +00:00
docs: kbase: Add a section explaining how to verify SEV from the guest
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>
This commit is contained in:
parent
e1d5390224
commit
8e02fa2e25
@ -349,6 +349,18 @@ EOF</pre>
|
|||||||
...
|
...
|
||||||
</domain></pre>
|
</domain></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>
|
<h2><a id="Limitations">Limitations</a></h2>
|
||||||
<p>
|
<p>
|
||||||
Currently, the boot disk cannot be of type virtio-blk, instead, virtio-scsi
|
Currently, the boot disk cannot be of type virtio-blk, instead, virtio-scsi
|
||||||
|
Loading…
Reference in New Issue
Block a user