[PATCH 0/6] Add Security Guest doc and check for capabilities cache validation

Boris Fiuczynski posted 6 patches 3 years, 11 months ago
Test syntax-check failed
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/20200511164201.7954-1-fiuczy@linux.ibm.com
There is a newer version of this series
docs/kbase.html.in                 |   3 +
docs/kbase/launch_security_sev.rst |   9 +-
docs/kbase/s390_protected_virt.rst | 189 +++++++++++++++++++++++++++++
src/libvirt_private.syms           |   2 +
src/qemu/qemu_capabilities.c       |  83 +++++++++++++
src/util/virutil.c                 | 173 ++++++++++++++++++++++++++
src/util/virutil.h                 |  18 +++
tests/utiltest.c                   | 130 ++++++++++++++++++++
tools/virt-host-validate-common.c  |  90 +++++++++++++-
tools/virt-host-validate-common.h  |   5 +
tools/virt-host-validate-qemu.c    |   4 +
11 files changed, 701 insertions(+), 5 deletions(-)
create mode 100644 docs/kbase/s390_protected_virt.rst
[PATCH 0/6] Add Security Guest doc and check for capabilities cache validation
Posted by Boris Fiuczynski 3 years, 11 months ago
This series introduces the concept of a 'Secure Guest' feature
which covers on s390 IBM Secure Execution and on x86 AMD Secure
Encrypted Virtualization.

Besides adding documentation for IBM Secure Execution it also adds
checks during validation of the qemu capabilities cache.
These checks per architecture can be performed for IBM Secure
Execution on s390 and AMD Secure Encrypted Virtualization on AMD x86
CPUs (both checks implemented in this series).

For s390 the verification consists of:
- checking if /sys/firmware/uv is available: meaning the HW
facility is available and the host OS supports it;
- checking if the kernel cmdline contains 'prot_virt=1': meaning
the host OS wants to use the feature.

For AMD Secure Encrypted Virtualization the verification consists of:
- checking if /sys/module/kvm_amd/parameters/sev contains the
value '1': meaning SEV is enabled in the host kernel;
- checking if the kernel cmdline contains 'mem_encrypt=on': meaning
SME memory encryption feature on the host is enabled

Whenever the availability of the feature does not match the secure
guest flag in the cache then libvirt will re-build it in order to
pick up the new set of capabilities available.

Additionally, this series adds the same aforementioned checks to the
virt-host-validate tool to facilitate the manual verification
process for users.

Boris Fiuczynski (2):
  tools: secure guest check on s390 in virt-host-validate
  tools: secure guest check for AMD in virt-host-validate

Paulo de Rezende Pinatti (3):
  util: introduce a parser for kernel cmdline arguments
  qemu: check if s390 secure guest support is enabled
  qemu: check if AMD secure guest support is enabled

Viktor Mihajlovski (1):
  docs: Describe protected virtualization guest setup

 docs/kbase.html.in                 |   3 +
 docs/kbase/launch_security_sev.rst |   9 +-
 docs/kbase/s390_protected_virt.rst | 189 +++++++++++++++++++++++++++++
 src/libvirt_private.syms           |   2 +
 src/qemu/qemu_capabilities.c       |  83 +++++++++++++
 src/util/virutil.c                 | 173 ++++++++++++++++++++++++++
 src/util/virutil.h                 |  18 +++
 tests/utiltest.c                   | 130 ++++++++++++++++++++
 tools/virt-host-validate-common.c  |  90 +++++++++++++-
 tools/virt-host-validate-common.h  |   5 +
 tools/virt-host-validate-qemu.c    |   4 +
 11 files changed, 701 insertions(+), 5 deletions(-)
 create mode 100644 docs/kbase/s390_protected_virt.rst

-- 
2.25.1