Skip to content

Commit

Permalink
confidential guest support: Update documentation
Browse files Browse the repository at this point in the history
Now that we've implemented a generic machine option for configuring various
confidential guest support mechanisms:
  1. Update docs/amd-memory-encryption.txt to reference this rather than
     the earlier SEV specific option
  2. Add a docs/confidential-guest-support.txt to cover the generalities of
     the confidential guest support scheme

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
  • Loading branch information
dgibson committed Feb 8, 2021
1 parent ec78e2c commit 64d19f3
Show file tree
Hide file tree
Showing 2 changed files with 44 additions and 1 deletion.
2 changes: 1 addition & 1 deletion docs/amd-memory-encryption.txt
Expand Up @@ -73,7 +73,7 @@ complete flow chart.
To launch a SEV guest

# ${QEMU} \
-machine ...,memory-encryption=sev0 \
-machine ...,confidential-guest-support=sev0 \
-object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1

Debugging
Expand Down
43 changes: 43 additions & 0 deletions docs/confidential-guest-support.txt
@@ -0,0 +1,43 @@
Confidential Guest Support
==========================

Traditionally, hypervisors such as QEMU have complete access to a
guest's memory and other state, meaning that a compromised hypervisor
can compromise any of its guests. A number of platforms have added
mechanisms in hardware and/or firmware which give guests at least some
protection from a compromised hypervisor. This is obviously
especially desirable for public cloud environments.

These mechanisms have different names and different modes of
operation, but are often referred to as Secure Guests or Confidential
Guests. We use the term "Confidential Guest Support" to distinguish
this from other aspects of guest security (such as security against
attacks from other guests, or from network sources).

Running a Confidential Guest
----------------------------

To run a confidential guest you need to add two command line parameters:

1. Use "-object" to create a "confidential guest support" object. The
type and parameters will vary with the specific mechanism to be
used
2. Set the "confidential-guest-support" machine parameter to the ID of
the object from (1).

Example (for AMD SEV)::

qemu-system-x86_64 \
<other parameters> \
-machine ...,confidential-guest-support=sev0 \
-object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1

Supported mechanisms
--------------------

Currently supported confidential guest mechanisms are:

AMD Secure Encrypted Virtualization (SEV)
docs/amd-memory-encryption.txt

Other mechanisms may be supported in future.

0 comments on commit 64d19f3

Please sign in to comment.