From nobody Sat Apr 27 03:07:57 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of redhat.com designates 209.132.183.28 as permitted sender) client-ip=209.132.183.28; envelope-from=libvir-list-bounces@redhat.com; helo=mx1.redhat.com; Authentication-Results: mx.zohomail.com; spf=pass (zoho.com: domain of redhat.com designates 209.132.183.28 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx.zohomail.com with SMTPS id 1538387344406606.2948875025618; Mon, 1 Oct 2018 02:49:04 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 4FDE5307D850; Mon, 1 Oct 2018 09:49:02 +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 574533091392; Mon, 1 Oct 2018 09:49:01 +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 E94D2181A12F; Mon, 1 Oct 2018 09:48:58 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id w919mvWB026834 for ; Mon, 1 Oct 2018 05:48:57 -0400 Received: by smtp.corp.redhat.com (Postfix) id 17B962010D04; Mon, 1 Oct 2018 09:48:57 +0000 (UTC) Received: from dahmer.brq.redhat.com (unknown [10.43.2.94]) by smtp.corp.redhat.com (Postfix) with ESMTP id 359D72010D0A; Mon, 1 Oct 2018 09:48:52 +0000 (UTC) From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= To: libvir-list@redhat.com Date: Mon, 1 Oct 2018 11:48:50 +0200 Message-Id: <20181001094850.10640-1-fidencio@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.25 X-loop: libvir-list@redhat.com Cc: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Subject: [libvirt] [libvirt PATCH] news: Update for 4.8.0 release 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: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.84 on 10.5.11.26 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.48]); Mon, 01 Oct 2018 09:49:03 +0000 (UTC) X-ZohoMail: RDMRC_0 RSF_0 Z_629925259 SPT_0 Signed-off-by: Fabiano Fid=C3=AAncio --- I went through the commits since last release and added a few notes which seem to be relevant for the news. In case you notice there's something missing, please, either send me the text to add it (and I'll re-sping this patch) and add the text before merging this one. --- docs/news.xml | 88 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 88 insertions(+) diff --git a/docs/news.xml b/docs/news.xml index 3ed6ff8aeb..29b12cb04d 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -44,6 +44,50 @@ and virDomainPMWakeup APIs. + + utils: Introduce monitor capability interface + + + The resource monitor has been introduced and it creates the interf= ace + for getting the host capability of the resource monitor from the s= ystem + resource control. + The resource monitor takes the role of RDT monitoring groups and c= ould + be used to monitor the resource consumption information. + + + conf: Introduce RDT monitor host capability + + + Introduce cache monitor (CMT) and memory bandwidth monitor (MBM). + For the former (CMT), the host capability is shown like: + <host> + ... + <cache> + <bank id=3D'0' level=3D'3' type=3D'both' size=3D'15' unit= =3D'MiB' cpus=3D'0-5'> + <control granularity=3D'768' min=3D'1536' unit=3D'KiB' = type=3D'both' maxAllocs=3D'4'/> + </bank> + <monitor level=3D'3' 'reuseThreshold'=3D'270336' maxMonit= ors=3D'176'> + <feature name=3D'llc_occupancy'/> + </monitor> + </cache> + ... + </host> + + For the latter (MBM), the capability is shown like this: + <host> + ... + <memory_bandwidth> + <node id=3D'1' cpus=3D'6-11'> + <control granularity=3D'10' min =3D'10' maxAllocs=3D'4'= /> + </node> + <monitor maxMonitors=3D'176'> + <feature name=3D'mbm_total_bytes'/> + <feature name=3D'mbm_local_bytes'/> + </monitor> + </memory_bandwidth> + ... + </host> +
@@ -55,6 +99,15 @@ Drop support for these older versions and require Xen >=3D 4.6. + + + nwfilter: Disallow binding creation in session mode + + + Ensure that a filter binding creation is not attempted in session + mode and generate the proper error message. + +
@@ -68,8 +121,43 @@ Guest Agent. + + storage: Allow to use any format as input volume for encryption + + + Since v4.5.0 libvirt has support to use a 'raw' input volume for + encryption. From now on, let's not limit this to 'raw' only. + + + libxl: Add support to set shadow memory for any guest type, not on= ly + HVM + + + PVH guests now can take advantage of using shadow memory. +
+ + + virsh: Require explicit --domain for domxml-to-native + + + The domxml-to-native virsh command accepts either --xml or --dom= ain + option followed by a file or domain name respectively, The --dom= ain + option is documented as required, which means an argument with no + option is treated as --xml. Commit v4.3.0-127-gd86531daf2 broke = this + by making --domain optional and thus an argument with no option = was + treated as --domain. + + + + lxc_monitor: Avoid AB / BA lock race + + + A dealock situation could occur when autostarting a LXC domain 'gu= est' + due to two threads attempting to take opposing locks while holding + opposing locks (AB BA problem). +
--=20 2.19.0 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list