From nobody Mon Jun 17 18:42:50 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.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.133.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=1688127418; cv=none; d=zohomail.com; s=zohoarc; b=fsQJEq9eMDjVWpCdEUpfjElUm7s46yxeAO8YByWy8FEeP/dyomHlFgOpZx0pxKo6bnD18fyWrB7WD2OMxWy1UZl6GU44yE5U+/ZUcS2x2HpAVlAo5xSf/y931kDe0BjP+6n+SsYyu/NCJFPQw/RdC/FIa/d9nI9Sa6TXBbQacbA= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1688127418; h=Content-Type:Content-Transfer-Encoding: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=jBjIT4x1A0sOLHNiOgXv4xbt/P8vWyVd5eoMcYHWoq8=; b=IldVHlSIeO2ONBc6gQa2qpOQQBEFqCbPaeAjHBoc/Mm/wbaQyQJ+G70oOBNi9e2SHaCGXdyVbOTIubzu1ZbO9RsWx4XCSqz8f223dC0BJrmfDnLeA3JN6K0GJH1TSMxWxGurhw2a7P+Je85iPpjuaomiEpI41xWY6HfvH+y9VoY= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.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.133.124]) by mx.zohomail.com with SMTPS id 1688127418387314.6646540057453; Fri, 30 Jun 2023 05:16:58 -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-656-JNBuJh9kMJCrdmye-WgFLw-1; Fri, 30 Jun 2023 08:16:54 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 4EC7D3C11A25; Fri, 30 Jun 2023 12:16:52 +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 3D02A1121314; Fri, 30 Jun 2023 12:16:52 +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 557F019452C1; Fri, 30 Jun 2023 12:16:51 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id A8DAF1946595 for ; Fri, 30 Jun 2023 12:09:47 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 7C14340C206F; Fri, 30 Jun 2023 12:09:47 +0000 (UTC) Received: from speedmetal.redhat.com (unknown [10.45.242.9]) by smtp.corp.redhat.com (Postfix) with ESMTP id 05A7340C2063 for ; Fri, 30 Jun 2023 12:09:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1688127417; 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: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=jBjIT4x1A0sOLHNiOgXv4xbt/P8vWyVd5eoMcYHWoq8=; b=QxEwRXtMkiXn4IgenCSX3Wx2Luz7+RH+Uz0LgMTaWnxJXsrGSny+qv3sQcqFGp2DwIWBpl 2Z7qxXExo8KaCT6HumouPDRe+VPRMta+/dq1yW9HF7X5Gs/9JgXOpGT1ze7g+BA0icS7rB URCcVFqxkb5c2X8vrBbTVnU+C7NwEoU= X-MC-Unique: JNBuJh9kMJCrdmye-WgFLw-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 1/2] NEWS: Move section about 'discard_no_unref' to features Date: Fri, 30 Jun 2023 14:09:44 +0200 Message-ID: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 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.3 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: 1688127418697100001 Content-Type: text/plain; charset="utf-8" Signed-off-by: Peter Krempa Reviewed-by: J=C3=A1n Tomko --- NEWS.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/NEWS.rst b/NEWS.rst index 950b188a8b..857fef0f6d 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -17,6 +17,13 @@ v9.5.0 (unreleased) * **New features** + * qemu: Allow configuring the ``discard-no-unref`` feature of ``qcow2`` = driver + + The new ``discard_no_unref`` attribute of the ``disk`` ``driver`` elem= ent + controls whether the ``qcow2`` driver in qemu unrefs clusters inside t= he + image on discard requests. Disabling cluster unrefing decreases fragme= ntation + of the image. + * **Improvements** * qemu: Include maximum physical address size in baseline CPU @@ -26,13 +33,6 @@ v9.5.0 (unreleased) compatible with all hosts even if their supported physical address siz= es differ. - * qemu: Allow configuring the ``discard-no-unref`` feature of ``qcow2`` = driver - - The new ``discard_no_unref`` attribute of the ``disk`` ``driver`` elem= ent - controls whether the ``qcow2`` driver in qemu unrefs clusters inside t= he - image on discard requests. Disabling cluster unrefing decreases fragme= ntation - of the image. - * **Bug fixes** --=20 2.41.0 From nobody Mon Jun 17 18:42:50 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.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.133.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=1688127423; cv=none; d=zohomail.com; s=zohoarc; b=MnYPLwVkpQg3Y794Dmm3nGf/ANJUSGz3xpCFnBdf2ELmDKqx4X/OkdJKMh7fjH74vrDs/0thYy2X4OWGZC2gznILaAp0DXPKJHppszF0YESCYAnFK5jLWJbgSDPJ+hQjdR21WjB6YC3rK4/aTQPu8LtDhy9Lz5SDFKS3iKP4zrI= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1688127423; h=Content-Type:Content-Transfer-Encoding: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=NQRyUc9synh5mfL0aisdibAiP4T/z0yAMpp0o2QzuUY=; b=e7dd36vc5QpF+TUpo/t8omiIVBEINIbhwwfjVCqDLrAWm4YXitwcUdfMqMNgLuVbkThM4Bgt1qJuDUnCHTErXgU8EADFxRikaBmtEZw+4ZxAjclmG2KypP4UhM/jGBW7oSAkHq52Mv3JkNhDtSBnXX8Cel5VglMrcdFAzmxQjmE= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.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.133.124]) by mx.zohomail.com with SMTPS id 16881274231151022.6406636052056; Fri, 30 Jun 2023 05:17:03 -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-626-cPTICqutNkmODmYvqb5B3g-1; Fri, 30 Jun 2023 08:16:55 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D3F6D1C08DBE; Fri, 30 Jun 2023 12:16:51 +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 67A5D1121314; Fri, 30 Jun 2023 12:16:51 +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 323391946A41; Fri, 30 Jun 2023 12:16:51 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 650AF1946595 for ; Fri, 30 Jun 2023 12:09:48 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 53F1340C206F; Fri, 30 Jun 2023 12:09:48 +0000 (UTC) Received: from speedmetal.redhat.com (unknown [10.45.242.9]) by smtp.corp.redhat.com (Postfix) with ESMTP id CFB1340C2063 for ; Fri, 30 Jun 2023 12:09:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1688127422; 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: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=NQRyUc9synh5mfL0aisdibAiP4T/z0yAMpp0o2QzuUY=; b=EyvDnm6FT98BAddwsZuXSVQ6ELTxFy06bYX8tjAGAmCT0pgJqyNK/z8qd4T1Vn6d/QKm41 lGs4VichlcRHhZhGLOfIgavxPQlD5xxbsUCm5ratwLFJr2GJMAq7K8UpOLdxLnfaVgcVwL 8R4bkg43Hjr+J/dYcW81ELfzjDpn/ls= X-MC-Unique: cPTICqutNkmODmYvqb5B3g-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 2/2] NEWS: Document changes for the release Date: Fri, 30 Jun 2023 14:09:45 +0200 Message-ID: <85ee0063ce672ed4d496738b5ee772d526897c98.1688126953.git.pkrempa@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 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.3 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: 1688127424941100001 Content-Type: text/plain; charset="utf-8" Signed-off-by: Peter Krempa Reviewed-by: J=C3=A1n Tomko --- NEWS.rst | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 857fef0f6d..f3e8f9bf8b 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -33,8 +33,47 @@ v9.5.0 (unreleased) compatible with all hosts even if their supported physical address siz= es differ. + * conf: Properly handle slots for non-DIMM ```` devices + + Memory devices such as ``virtio-mem`` don't need a memory slot as they= are + PCI devices. ``libvirt`` now properly accounts the memory slots for su= ch + devices as well as specifying the ``slots`` attribute of the ```` + element is no longer needed unless DIMM-like devices are to be used. + + * ``passt`` log and port forwarding improvements + + Libvirt now ensures that the ``passt`` helper process can access the + configured log file even when it's placed in a directory without permi= ssions. + + The ```` element of a passt-backed interface can now omit= the + ``address`` attribute as it's enough to specify a ``dev``. + * **Bug fixes** + * lxc: Allow seeking in ``/proc/meminfo`` to resove failure with new ``p= rocps`` package + + New version of the ``free`` command from ``procps`` package seeks into= the + ``/proc/meminfo`` file, which was not supported by the instance of the= file + exposed via LXC causing a failure. + + * qemu: Fix rare race-condition when detaching a device + + The device removal handler callback function didn't re-check the state= of + the unplug operation after a timeout, which could rarely cause that the + device was removed from the VM but not the definition. + + * qemu: Fix NUMA memory allocation logic + + qemu allocates memory via the emulator thread thus that has to be allo= wed + to access all configured NUMA nodes of the VM rather than just the one= where + it's supposed to be pinned. + + + * qemu: Fix setup of ``hostdev`` backed ```` + + The proper steps to initialize the host device were skipped for interf= aces + due to a logic bug preventing start of VM which used them. + v9.4.0 (2023-06-01) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 2.41.0