From nobody Sun May 5 01:20:36 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1664535207; cv=none; d=zohomail.com; s=zohoarc; b=V/1Sb3PznNKRThhhOedHIZGL2FUc/ulVjWQJ3q0XV22VBZOthzG0seP4kBmgkY5CrRtRKP/qWkHG0IxpJORqmV7KWpplGw5kVJ1mcnK4wsGxgQKUS6Q4Ep3J/vY2gMq7F5b/0GMYTndXjNFCvslZaYvjfVGfRk3UD49On+caFKk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1664535207; h=Content-Type:Content-Transfer-Encoding:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=9gt0odJ2ChcDF7E9bEMgaTNLpWFznP1xzjDgqDsxr50=; b=kFEttPOex7z1cWXRTpxTEYRnpM40CPKsPlHztwMp/OEUlKqg0ztrf3wnDScGPesGi8ficNlwZlnbRSY0ZqmDAiJ4tslHXeNYNECcZE6lMpquv0bCBhuhzbS1fsZJCfTeo/01YaNupsrwd5fsEM6O4Sny/PBScoMBcDbxN+Sc3VA= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com with SMTPS id 1664535207984478.4473874840527; Fri, 30 Sep 2022 03:53:27 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-263-VK7svcfqMCOJDUKF6AVPtQ-1; Fri, 30 Sep 2022 06:53:18 -0400 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 247D31C06EE6; Fri, 30 Sep 2022 10:53:16 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 787D5475061; Fri, 30 Sep 2022 10:53:14 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 534201946A54; Fri, 30 Sep 2022 10:53:14 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 51B1F1946A52 for ; Fri, 30 Sep 2022 10:53:13 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 41DE52166B2A; Fri, 30 Sep 2022 10:53:13 +0000 (UTC) Received: from maggie.redhat.com (unknown [10.43.2.39]) by smtp.corp.redhat.com (Postfix) with ESMTP id DF0512166B26 for ; Fri, 30 Sep 2022 10:53:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664535206; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=9gt0odJ2ChcDF7E9bEMgaTNLpWFznP1xzjDgqDsxr50=; b=NHLEqTWYJ+uB8jr7uY0AT5C88+pYC5y0D1bsB7wooJiNDpKRz4eBrKEbxnEnQ8slZLyvGn +IAKVCI6Wbb4bDWfZMMPIiPaRUTnYg4jnCXaCfOqPddhCahqIZ2ZpypYyJJsS8qYFGE3jF 6xaksSldCdL6m79UmPUvQCF+2PEPH60= X-MC-Unique: VK7svcfqMCOJDUKF6AVPtQ-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Michal Privoznik To: libvir-list@redhat.com Subject: [PATCH] NEWS: Document my contributions for upcoming release Date: Fri, 30 Sep 2022 12:53:09 +0200 Message-Id: <4fac3fb8af76f3c3772972a9b297b8df1090f839.1664535189.git.mprivozn@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1664535208932100001 Content-Type: text/plain; charset="utf-8"; x-default="true" Signed-off-by: Michal Privoznik Reviewed-by: Jiri Denemark --- NEWS.rst | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 69c5b70c2f..81c95859ff 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -25,6 +25,11 @@ v8.8.0 (unreleased) =20 * **Improvements** =20 + * qemu: Implement VIR_DOMAIN_STATS_CPU_TOTAL for qemu:///session + + Users can now query VIR_DOMAIN_STATS_CPU_TOTAL (also known as cpu.tim= e) + statistics for session domains. + * **Bug fixes** =20 * qemu: Fix non-shared storage migration setup @@ -33,6 +38,26 @@ v8.8.0 (unreleased) ( ``virsh migrate --copy-storage-all``) which was broken by a refactor= of the code in libvirt-8.7. =20 + * selinux: Don't ignore NVMe disks when setting image label + + Libvirt did not set any SELinux label on NVMe disks and relied only on= the + default SELinux policy. This turned out to cause problem when using + namespace or altered policy and thus is fixed now. + + * qemu: Fix a deadlock when setting up namespace + + When starting a domain, libvirt creates a mount namespace and manages + private /dev with only a handful nodes exposed. But when creating thos= e a + deadlock inside glib might have occurred. The code was changed so that + libvirt does not tickle the glib bug. + + * qemu: Don't build memory paths on daemon restart + + When the daemon is restarted it tried to create domain private paths f= or + each mounted hugetlbfs. When this failed, the corresponding domain was + killed. This operation is now performed during domain startup and memo= ry + hotplug and no longer leads to sudden kill of the domain. + =20 v8.7.0 (2022-09-01) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 2.35.1