Comment 10 for bug 1874647

------- Comment From <email address hidden> 2020-06-17 12:27 EDT-------
(In reply to comment #14)
> Note: the referred path set didn't land yet.

Please not that the patch series has been accepted upstream.
It will be released as part of libvirt v6.5.0.

Here is the list of the commit ids:
c5fffb959d util: Introduce a parser for kernel cmdline arguments
b611b620ce qemu: Check if s390 secure guest support is enabled
657365e74f qemu: Check if AMD secure guest support is enabled
0254ceab82 tools: Secure guest check on s390 in virt-host-validate
4b561d49ad tools: Secure guest check for AMD in virt-host-validate
2c3ffa3728 docs: Update AMD launch secure description
f0d0cd6179 docs: Describe protected virtualization guest setup

The issue described in this bugzilla (stale capability cache) should be resolved already by the first two patches of the series. Patch 4 extends virt-host-validate with checks of the hosts readiness to support IBM Secure Execution and patch 6 provides documentation how to setup and use IBM Secure Execution with libvirt on linux on Z.

Please also not that there is another series that might come in handy for some other stale capability cache scenarios. This might e.g. occur if the KVM host system itself is being moved/migrated/upgraded.
Here is the list of commit ids:
8cb9d2495c util: Define g_autoptr callback for FILE
a551dd5fdf hostcpu: Introduce virHostCPUGetSignature
44f826e4a0 hostcpu: Implement virHostCPUGetSignature for x86
2a68ceaa6e hostcpu: Implement virHostCPUGetSignature for ppc64
d3d87e0cef hostcpu: Implement virHostCPUGetSignature for s390
004804a7d7 qemu: Invalidate capabilities when host CPU changes