651615d92d
At least some s390 cpu models support "Protected Virtualization" (PV),
a mechanism to protect guests from eavesdropping by a compromised
hypervisor.
This is similar in function to other mechanisms like AMD's SEV and
POWER's PEF, which are controlled by the "confidential-guest-support"
machine option. s390 is a slightly special case, because we already
supported PV, simply by using a CPU model with the required feature
(S390_FEAT_UNPACK).
To integrate this with the option used by other platforms, we
implement the following compromise:
- When the confidential-guest-support option is set, s390 will
recognize it, verify that the CPU can support PV (failing if not)
and set virtio default options necessary for encrypted or protected
guests, as on other platforms. i.e. if confidential-guest-support
is set, we will either create a guest capable of entering PV mode,
or fail outright.
- If confidential-guest-support is not set, guests might still be
able to enter PV mode, if the CPU has the right model. This may be
a little surprising, but shouldn't actually be harmful.
To start a guest supporting Protected Virtualization using the new
option use the command line arguments:
-object s390-pv-guest,id=pv0 -machine confidential-guest-support=pv0
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
50 lines
1.7 KiB
Plaintext
50 lines
1.7 KiB
Plaintext
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
|
|
|
|
POWER Protected Execution Facility (PEF)
|
|
docs/papr-pef.txt
|
|
|
|
s390x Protected Virtualization (PV)
|
|
docs/system/s390x/protvirt.rst
|
|
|
|
Other mechanisms may be supported in future.
|