From nobody Mon Apr 29 23:33:02 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 1519909717309570.946309940071; Thu, 1 Mar 2018 05:08:37 -0800 (PST) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id B8D407FEA5; Thu, 1 Mar 2018 13:08:35 +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 86F1B5D9C7; Thu, 1 Mar 2018 13:08:35 +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 4A92A180BAE2; Thu, 1 Mar 2018 13:08:35 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id w21D8Xfg019070 for ; Thu, 1 Mar 2018 08:08:33 -0500 Received: by smtp.corp.redhat.com (Postfix) id A5C192144B26; Thu, 1 Mar 2018 13:08:33 +0000 (UTC) Received: from moe.brq.redhat.com (unknown [10.43.2.192]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2DC672144B24; Thu, 1 Mar 2018 13:08:33 +0000 (UTC) From: --help To: libvir-list@redhat.com Date: Thu, 1 Mar 2018 14:08:29 +0100 Message-Id: <78ba62bb4f9a7359c82e2056595d8e4ce6830969.1519909709.git.mprivozn@redhat.com> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-loop: libvir-list@redhat.com Cc: abologna@redhat.com Subject: [libvirt] [PATCH] news: Update release notes 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: , MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Thu, 01 Mar 2018 13:08:36 +0000 (UTC) X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Type: text/plain; charset="utf-8" Signed-off-by: --help --- docs/news.xml | 102 ++++++++++++++++++++++++++++++++++++++++++++++++++++++= ++++ 1 file changed, 102 insertions(+) diff --git a/docs/news.xml b/docs/news.xml index 86a0c8d18..53bf9a49c 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -44,6 +44,28 @@ using the cachetune element in cputune. + + + Allow opening secondary drivers + + + Up until now it was possible to connect to only hypervisor drive= rs + (e.g. qemu:///system, lxc:///, vbox:///system, and so on). The + internal drivers (like network driver, node device driver, etc.)= were + hidden from users and users could use them only indirectly. Star= ting + with this release new connection URIs are accepted. For instance + network:///system, storage:///system and so on. + + + + + virtlogd, virtlockd: Add support for admin protocol + + + These two daemons now support admin protocol through which some = admin + info can be gathered or some configuration tweaked on the fly. + +
@@ -82,8 +104,88 @@ libxl: add support for setting clock offset and adjustment + + + Make port allocator global + + + Up until now each driver had their own port allocator module. Th= is + meant that info on port usage was not shared. Starting with this + release, the port allocator module is made global and therefore + drivers allocate ports from global pool. + + + + + src: Enable building with GCC 8.0 + + + GCC 8.0 added more warnings which found some genuine problems wi= th our code. + +
+ + + qemu: Check for unsafe migration more thoroughly + + + If a domain disk is stored on local filesystem (e.g. ext4) but is + not being migrated it is very likely that domain is not able to + run on destination. Regardless of share/cache mode. + + + + + qemu: Fix updating device with boot order + + + Starting with 3.7.0 release updating any device with boot order = would + fail with 'boot order X is already used by another device' while= in + fact it was the very same device. + + + + + virlog: determine the hostname on startup CVE-2018-6764 + + + At later point it might not be possible or even safe to use + getaddrinfo(). It can in turn result in a load of NSS module whi= ch + can even be loaded from unsage guest filesystem and thus escape = the + confinment of its container. + + + + + qemu: Rework vCPU statistics fetching + + + Fetching vCPU statistics was very expensive because it lead to w= aking + up vCPU threads in QEMU and thus it degraded performance. The co= de + was reworked so that fetching statistics does not wake up halted + vCPUs. + + + + + qemu: unlink memory backing file on domain shutdown + + + Depending on the filesystem where domain memory is stored, some = files + might have been left behind. This is not a problem on hugetlbfs,= but + it is a problem on regular filesystems like ext4. + + + + + qemu: Fix shutting down domains in parallel + + + If multiple domains were being shut down in parallel, libvirtd m= ight + have deadlocked. + +
--=20 2.16.1 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list