On 5/13/20 3:30 PM, Daniel Henrique Barboza wrote:
> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
> ---
> docs/news.xml | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/docs/news.xml b/docs/news.xml
> index 4cef804aac..c22a0f0a18 100644
> --- a/docs/news.xml
> +++ b/docs/news.xml
> @@ -44,6 +44,23 @@
> <libvirt>
> <release version="v6.4.0" date="unreleased">
> <section title="New features">
> + <change>
> + <summary>
> + qemu: add TPM Proxy device support
> + </summary>
> + <description>
> + libvirt can now create guests using a new device type called
> + "TPM Proxy". The TPM Proxy connects to a TPM Resource Manager
> + present in the host, enabling the guest to run in secure virtual
> + machine mode with the help of an Ultravisor. Adding a TPM Proxy to
> + a pSeries guest brings no security benefits unless the guest is
> + running on a PPC64 host that has Ultravisor and TPM Resource Manager
> + support. Only one TPM Proxy is allowed per guest. A guest using
> + a TPM Proxy device can instantiate another TPM device at the same
> + time. This device is supported only for pSeries guests via the new
> + 'spapr-tpm-proxy' model of the TPM 'passthrough' backend.
> + </description>
> + </change>
> </section>
> <section title="Improvements">
> </section>