A number of hardware platforms are implementing mechanisms whereby the
hypervisor does not have unfettered access to guest memory, in order
to mitigate the security impact of a compromised hypervisor.
AMD's SEV implements this with in-cpu memory encryption, and Intel has
its own memory encryption mechanism. POWER has an upcoming mechanism
to accomplish this in a different way, using a new memory protection
level plus a small trusted ultravisor. s390 also has a protected
execution environment.
The current code (committed or draft) for these features has each
platform's version configured entirely differently. That doesn't seem
ideal for users, or particularly for management layers.
AMD SEV introduces a notionally generic machine option
"machine-encryption", but it doesn't actually cover any cases other
than SEV.
This series is a proposal to at least partially unify configuration
for these mechanisms, by renaming and generalizing AMD's
"memory-encryption" property. It is replaced by a
"securable-guest-memory" property pointing to a platform specific
object which configures and manages the specific details.
Changes since v4:
* Renamed from "host trust limitation" to "securable guest memory",
which I think is marginally more descriptive
* Re-organized initialization, because the previous model called at
kvm_init didn't work for s390
* Assorted fixes to the s390 implementation; rudimentary testing
(gitlab CI) only
Changes since v3:
* Rebased
* Added first cut at handling of s390 protected virtualization
Changes since RFCv2:
* Rebased
* Removed preliminary SEV cleanups (they've been merged)
* Changed name to "host trust limitation"
* Added migration blocker to the PEF code (based on SEV's version)
Changes since RFCv1:
* Rebased
* Fixed some errors pointed out by Dave Gilbert
David Gibson (12):
securable guest memory: Introduce new securable guest memory base
class
securable guest memory: Handle memory encryption via interface
securable guest memory: Move side effect out of
machine_set_memory_encryption()
securable guest memory: Rework the "memory-encryption" property
securable guest memory: Decouple kvm_memcrypt_*() helpers from KVM
sev: Add Error ** to sev_kvm_init()
securable guest memory: Introduce sgm "ready" flag
securable guest memory: Move SEV initialization into arch specific
code
spapr: Add PEF based securable guest memory
spapr: PEF: prevent migration
securable guest memory: Alter virtio default properties for protected
guests
s390: Recognize securable-guest-memory option
Greg Kurz (1):
qom: Allow optional sugar props
accel/kvm/kvm-all.c | 39 +------
accel/kvm/sev-stub.c | 10 +-
accel/stubs/kvm-stub.c | 10 --
backends/meson.build | 1 +
backends/securable-guest-memory.c | 30 +++++
hw/core/machine.c | 71 ++++++++++--
hw/i386/pc_sysfw.c | 6 +-
hw/ppc/meson.build | 1 +
hw/ppc/pef.c | 124 +++++++++++++++++++++
hw/ppc/spapr.c | 10 ++
hw/s390x/pv.c | 58 ++++++++++
include/exec/securable-guest-memory.h | 86 +++++++++++++++
include/hw/boards.h | 2 +-
include/hw/ppc/pef.h | 26 +++++
include/hw/s390x/pv.h | 1 +
include/qemu/typedefs.h | 1 +
include/qom/object.h | 3 +-
include/sysemu/kvm.h | 17 ---
include/sysemu/sev.h | 5 +-
qom/object.c | 4 +-
softmmu/vl.c | 16 ++-
target/i386/kvm.c | 12 ++
target/i386/monitor.c | 1 -
target/i386/sev.c | 153 ++++++++++++--------------
target/ppc/kvm.c | 18 ---
target/ppc/kvm_ppc.h | 6 -
target/s390x/kvm.c | 3 +
27 files changed, 510 insertions(+), 204 deletions(-)
create mode 100644 backends/securable-guest-memory.c
create mode 100644 hw/ppc/pef.c
create mode 100644 include/exec/securable-guest-memory.h
create mode 100644 include/hw/ppc/pef.h
--
2.28.0
