From nobody Mon Nov 25 23:22:35 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 207.211.31.120 as permitted sender) client-ip=207.211.31.120; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-1.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.120 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=fail(p=none dis=none) header.from=gmail.com ARC-Seal: i=1; a=rsa-sha256; t=1589581535; cv=none; d=zohomail.com; s=zohoarc; b=SQgUn/gLyGLw7cI29KiTffmGq+aTNeXDATNwbt3hqR1iQ5K47glIaXlA1LCN5x2eaATA0Mo3s6WhmX4+GiO/sb20g3TgGi3Zyxhl9TJf0KBh5vF+jfjfKqPoDe/UZsOvVe7WS/yYKlfD88hBC8D9xXM0+P7IxY/gctNsaNkp4cg= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1589581535; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=wyDKJGEN6pEEt0exP7NWGgrjegmIHYfoH/W8uOcNhVw=; b=GD1Uu933fcUzZ3zJOG+ZfPYEU++uFwvB86GAi8/pdQl37BtBQy05M7BB/bpCS3Eng+kmT/kXf0v5LeE0o0ItFIPzxMaecV8W1wVz9md5Qt2TaitIswGNo+2uapuE1R13eq4UT7xux3QUp9yoWhR1unfgri6BNz2VvpTLYa602yA= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.120 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=fail header.from= (p=none dis=none) header.from= Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by mx.zohomail.com with SMTPS id 1589581535590781.0676658544453; Fri, 15 May 2020 15:25:35 -0700 (PDT) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-407-PyQapt_uOauP3SbFRInCzA-1; Fri, 15 May 2020 18:25:32 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 16BA2107ACF4; Fri, 15 May 2020 22:25:26 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E5D151024837; Fri, 15 May 2020 22:25:25 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id B3B5C1806B0A; Fri, 15 May 2020 22:25:25 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 04FMPMg1015339 for ; Fri, 15 May 2020 18:25:22 -0400 Received: by smtp.corp.redhat.com (Postfix) id C405C200A773; Fri, 15 May 2020 22:25:22 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast01.extmail.prod.ext.rdu2.redhat.com [10.11.55.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id BFAAD2028DCC for ; Fri, 15 May 2020 22:25:22 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 9FC188A19B4 for ; Fri, 15 May 2020 22:25:22 +0000 (UTC) Received: from mail-qk1-f194.google.com (mail-qk1-f194.google.com [209.85.222.194]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-478-ICvBghbcNweFoWOuEiiQEw-1; Fri, 15 May 2020 18:25:20 -0400 Received: by mail-qk1-f194.google.com with SMTP id g185so4295338qke.7; Fri, 15 May 2020 15:25:19 -0700 (PDT) Received: from rekt.ibmuc.com ([2804:431:c7c7:fbf2:bc5e:c314:af31:7070]) by smtp.gmail.com with ESMTPSA id o18sm3181386qtb.7.2020.05.15.15.25.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 May 2020 15:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589581534; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=wyDKJGEN6pEEt0exP7NWGgrjegmIHYfoH/W8uOcNhVw=; b=QMvvufujOppJMM4cu4Pd6gF/5JksbEgoIoSLFsh8IuuEpYRBYijAztPTKFQombB6Tnbzrt qcIlC3keEcVacdoccEzRLOb9EJGjf969HXOVjyQDs1FJdyajZdzJhZQE+xSnDNth/D0XFQ GOkMCHEj8NgHoZxiq8o+dHIRFBqVfrM= X-MC-Unique: PyQapt_uOauP3SbFRInCzA-1 X-MC-Unique: ICvBghbcNweFoWOuEiiQEw-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=wyDKJGEN6pEEt0exP7NWGgrjegmIHYfoH/W8uOcNhVw=; b=iu7q7G0aeTOACIBMraf5xBEzmjcEIA9xMai+G3tu6DAWO/BkTDY7PkPKzX/zznoG8Z LAKvirZF4MXzZOQ33BlVHkB+RP99kN2DfrKE1rRU01skgJgcyakCPpk2voGBGVJjBrQ8 4/gyWrDonnfv86O62h74ON0d7D09sPJPgcixEx6LrwSef0STsV5idtia11zdZJJ4Zc7n rdDLXrJ+s852MeipvslemKa8aWYSw/VJ47HmCO7wC1QfRsP2appvUiljwAb5XqbIFjIU B+lPKH9tAxAzKKcaDJyqXLMM1E7qQqlUc9k4eMUKd9Fpf2YHqsJ+NwyhRmm3aI9zKidw 1i6w== X-Gm-Message-State: AOAM531EbLNBTu2vD391LluehttGGFJagcO36Sm5LCF7FaDreBGyIlPr 9fvHEL8BOt+Cs5EzM227aOyRz6Ur X-Google-Smtp-Source: ABdhPJxqUq2DbYdRLjR5ckRcvQuX0Ef8ID90gyuzo4ZjiXJY3NISmFCPTiKx0vJHVrTcSMNf2ksw1w== X-Received: by 2002:a37:634f:: with SMTP id x76mr5755449qkb.194.1589581519334; Fri, 15 May 2020 15:25:19 -0700 (PDT) From: Daniel Henrique Barboza To: libvir-list@redhat.com Subject: [PATCH v4 10/10] docs/news.xml: update for the new TPM Proxy device Date: Fri, 15 May 2020 19:24:13 -0300 Message-Id: <20200515222413.1231605-11-danielhb413@gmail.com> In-Reply-To: <20200515222413.1231605-1-danielhb413@gmail.com> References: <20200515222413.1231605-1-danielhb413@gmail.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-loop: libvir-list@redhat.com Cc: Daniel Henrique Barboza , stefanb@linux.ibm.com, jtomko@redhat.com, david@gibson.dropbear.id.au X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) Content-Type: text/plain; charset="utf-8" Reviewed-by: Stefan Berger Signed-off-by: Daniel Henrique Barboza --- 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 @@
+ + + qemu: add TPM Proxy device support + + + 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 Man= ager + 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 n= ew + 'spapr-tpm-proxy' model of the TPM 'passthrough' backend. + +
--=20 2.26.2