From nobody Tue Dec 16 16:56:32 2025 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of lists.libvirt.org designates 8.43.85.245 as permitted sender) client-ip=8.43.85.245; envelope-from=devel-bounces@lists.libvirt.org; helo=lists.libvirt.org; Authentication-Results: mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of lists.libvirt.org designates 8.43.85.245 as permitted sender) smtp.mailfrom=devel-bounces@lists.libvirt.org; dmarc=pass(p=reject dis=none) header.from=lists.libvirt.org ARC-Seal: i=1; a=rsa-sha256; t=1743477747; cv=none; d=zohomail.com; s=zohoarc; b=Dm9/jhF12TMeDwNqQ8PM2a5LXmzUaoNcEEt9gcv0pLih41z2bDuP0VqACEg1xiWsF4O+ac9KK/KZs51PX6JQDq3Y9iHJ/cN1G76lefBH8k0bosxp+UtTAXyLJaRCrldqicls9EVb4fo+bE1alwMcDQ7J77mW8QrPYCgJTWjHlNw= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1743477747; h=Content-Type:Content-Transfer-Encoding:Date:Date:From:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Reply-To:Reply-To:References:Subject:Subject:To:To:Message-Id:Cc; bh=b5IEgBmR+PgmmIKd/rRN+kS/LkcOcXDG37CqTCJ5Ry4=; b=HVFR3F3zWH9E76J0mfPAn+CMTHLujbBmGBp4GME+cW7vUp1wShcKq/3LW3FmN5ljxNOvYMMuuqDIbampZxrtce0eCIVDF8lLUQtSdaW5PesirvehoQ2pKbr6rot3N6TpLEEYLIbVEPTKpw3l5MYE3p3oTiSjKFKiOtUbyboReOA= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of lists.libvirt.org designates 8.43.85.245 as permitted sender) smtp.mailfrom=devel-bounces@lists.libvirt.org; dmarc=pass header.from= (p=reject dis=none) Return-Path: Received: from lists.libvirt.org (lists.libvirt.org [8.43.85.245]) by mx.zohomail.com with SMTPS id 1743477747860189.48103031899552; Mon, 31 Mar 2025 20:22:27 -0700 (PDT) Received: by lists.libvirt.org (Postfix, from userid 996) id 25F401320; Mon, 31 Mar 2025 23:22:27 -0400 (EDT) Received: from lists.libvirt.org (localhost [IPv6:::1]) by lists.libvirt.org (Postfix) with ESMTP id 0D6E7138B; Mon, 31 Mar 2025 23:18:55 -0400 (EDT) Received: by lists.libvirt.org (Postfix, from userid 996) id C82A0136B; Mon, 31 Mar 2025 23:18:51 -0400 (EDT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.libvirt.org (Postfix) with ESMTPS id 4F4D512BE for ; Mon, 31 Mar 2025 23:18:17 -0400 (EDT) Received: from mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-637-oqDE6PcmOpOowzPCXlfqFw-1; Mon, 31 Mar 2025 23:18:14 -0400 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 5F4491800263 for ; Tue, 1 Apr 2025 03:18:12 +0000 (UTC) Received: from hjs.brq.redhat.com (unknown [10.43.3.187]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id A7A9D1955D81 for ; Tue, 1 Apr 2025 03:18:11 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on lists.libvirt.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL,RCVD_IN_VALIDITY_RPBL_BLOCKED, RCVD_IN_VALIDITY_SAFE_BLOCKED,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1743477496; h=from:from: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; bh=AKdNPn4v9ytqwUJZgeNIMeC1NZVpNzebXhWP6MPeGRw=; b=e8jZJ7yH19BsgNDB754qiGBun2XRiVgWbX3Q3Of+JHXdN4RP9XZjF4dmeqTf2lywB9LZKx Lgl0LkjhkUQVKJyfZro8Sq90Y7JqMbz3WRK6ES0zEiKaYFxAyyN/X2HGhIgvZkCPazTyQW XzaCjXlp4FksdXSmKcC9Lfi9bh3OiuA= X-MC-Unique: oqDE6PcmOpOowzPCXlfqFw-1 X-Mimecast-MFC-AGG-ID: oqDE6PcmOpOowzPCXlfqFw_1743477494 To: devel@lists.libvirt.org Subject: [libvirt PATCH 7/7] NEWS: Document the QEMU driver removal Date: Tue, 1 Apr 2025 05:12:42 +0200 Message-ID: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: IwK4vnou3XIo4EP5B7af_jJxMdFdeLN3bbBICwSr3xk_1743477494 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable Message-ID-Hash: UPFSSWQYCY6Q7SOINMUMZJAOTG7H2WWK X-Message-ID-Hash: UPFSSWQYCY6Q7SOINMUMZJAOTG7H2WWK X-MailFrom: jtomko@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; header-match-config-2; header-match-config-3; header-match-devel.lists.libvirt.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.2 Precedence: list List-Id: Development discussions about the libvirt library & tools Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: From: =?utf-8?q?J=C3=A1n_Tomko_via_Devel?= Reply-To: =?UTF-8?q?J=C3=A1n=20Tomko?= X-ZohoMail-DKIM: fail (Header signature does not verify) X-ZM-MESSAGEID: 1743477749198019000 Content-Type: text/plain; charset="utf-8" From: J=C3=A1n Tomko Signed-off-by: J=C3=A1n Tomko --- NEWS.rst | 64 +++++++++++++++++++++++++++++++++++--------------------- 1 file changed, 40 insertions(+), 24 deletions(-) diff --git a/NEWS.rst b/NEWS.rst index 03efead80f..9a8611ccb0 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -8,7 +8,23 @@ the changes introduced by each of them. For a more fine-grained view, use the `git log`_. =20 =20 -v11.2.0 (unreleased) +v11.3.0 (unreleased) + +* **Security** + +* **Removed features** + + * Remove support for the QEMU driver + + As of today, the QEMU driver is no more. + +* **New features** + +* **Improvements** + +* **Bug fixes** + +v11.2.0 (also unreleased) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 * **Security** @@ -350,7 +366,7 @@ v10.10.0 (2024-12-02) =20 * **Improvements** =20 - * qemu: Support UEFI NVRAM images on block storage + * qemu: Support UEFI VRAM images on block storage =20 Libvirt now allows users to use block storage as backend for UEFI NVRAM images and allows them to be in format different than the template. Wh= en @@ -408,7 +424,7 @@ v10.9.0 (2024-11-01) =20 * qemu: internal snapshot improvements =20 - The qemu internal snapshot handling code was updated to use modern com= mands + The qmu internal snapshot handling code was updated to use modern comm= ands which avoid the problems the old ones had, preventing use of internal snapshots on VMs with UEFI NVRAM. Internal snapshots of VMs using UEFI= are now possible provided that the NVRAM is in ``qcow2`` format. @@ -446,7 +462,7 @@ v10.8.0 (2024-10-01) It is now permissable to have a ```` network th= at has no IP address assigned to the host's port of the bridge. This is the only way to create a libvirt network where guests are - unreachable from the host (and vice versa) and also 0 firewall + unreachable from the host (and vice ersa) and also 0 firewall rules are added on the host. =20 It is now also possible for a ```` network to @@ -531,7 +547,7 @@ v10.7.0 (2024-09-02) * CVE-2024-8235: Crash of ``virtinterfaced`` via ``virConnectListInterfa= ces()`` =20 A refactor of the code fetching the list of interfaces for multiple AP= Is - introduced corner case on platforms where allocating 0 bytes of memory + introduced cornr case on platforms where allocating 0 bytes of memory results in a NULL pointer. =20 This corner case would lead to a NULL-pointer dereference and subseque= nt @@ -578,7 +594,7 @@ v10.6.0 (2024-08-05) =20 * qemu: Require QEMU-5.2.0 or newer =20 - The minimal required version of QEMU was bumped to 5.2.0. + The minimal requied version of QEMU was bumped to 5.2.0. =20 * **New features** =20 @@ -652,7 +668,7 @@ v10.5.0 (2024-07-01) * Pass shutoff reason to release hook =20 Sometimes in release hook it is useful to know if the VM shutdown was - graceful or not. This is especially useful to do cleanup based on the = VM + graceful or not. This is especially useful todo cleanup based on the VM shutdown failure reason in release hook. Starting with this release the last argument 'extra' is used to pass VM shutoff reason in the call to release hook. @@ -698,7 +714,7 @@ v10.4.0 (2024-06-03) used in the virNetClientIOEventFD callback while the data pointer's st= ack frame was concurrently being "freed" when returning from virNetClientIOEvent= Loop(). This flaw allows a local, unprivileged user to access virtproxyd witho= ut - authenticating. + authenticatin. =20 * **New features** =20 @@ -799,7 +815,7 @@ v10.3.0 (2024-05-02) =20 Some PCI devices have large non-prefetchable memory. This can be a pro= blem in case when such device needs to be hotplugged as the firmware can't - foresee such situation. The user thus can override the value calculate= d at + foresee such situation. The user thus can verride the value calculated= at start to accomodate for such devices. =20 * **Improvements** @@ -859,7 +875,7 @@ v10.2.0 (2024-04-02) =20 Fix the flaw of the RPC library APIs of libvirt. The RPC server de-serialization code allocates memory for arrays before the non-negati= ve - length check is performed by the C API entry points. Passing a negative= length + length check is performed by the C API entry poits. Passing a negative = length to the g_new0 function results in a crash due to the negative length be= ing treated as a huge positive number. A local unprivileged user could use = this flaw to perform a denial of service attack by causing the libvirt daemo= n to @@ -947,7 +963,7 @@ v10.1.0 (2024-03-01) =20 In **libvirt-5.10** a check for non-NULL arrays has been adjusted to allow for NULL arrays with size 0 instead of rejecting all NULL - arrays. However that made the above issue significantly worse since + arrays. However that made the above issue sigificantly worse since that off-by-one error now did not write beyond an array, but dereferenced said NULL pointer making the crash certain in a specific scenario in which a NULL array of size 0 was passed to the @@ -1080,7 +1096,7 @@ v10.0.0 (2024-01-15) * qemu: Allow automatic resize of block-device-backed disk to full size = of the device =20 The new flag ``VIR_DOMAIN_BLOCK_RESIZE_CAPACITY`` for - ``virDomainBlockResize`` allows resizing a block-device backed ``raw``= disk + ``virDominBlockResize`` allows resizing a block-device backed ``raw`` = disk of a VM without the need to specify the full size of the block device. =20 * qemu: automatic selection/binding of VFIO variant drivers @@ -1097,7 +1113,7 @@ v10.0.0 (2024-01-15) Since the new nbdkit support requires a recent selinux policy that is = not widely available yet, it is now possible to build libvirt with nbdkit support for remote disks but disabled at runtime. This behavior is - controlled via the storage_use_nbdkit option of the qemu driver + controlled viathe storage_use_nbdkit option of the qemu driver configuration file. The option will default to being disabled, but thi= s may change in a future release and can be customized with the nbdkit_config_default build option. @@ -1121,7 +1137,7 @@ v10.0.0 (2024-01-15) The phase of copying storage during migration without shared storage requires that both the source and destination image are identical in s= ize. This may not be possible if the destination is backed by a block device - and the source image size is not a multiple of the block device block = size. + and the source imae size is not a multiple of the block device block s= ize. =20 Libvirt aleviates this by automatically adding a ```` to match = the size of the source image rather than failing the migration. @@ -1139,7 +1155,7 @@ v10.0.0 (2024-01-15) =20 * qemu: Various migration bug fixes and debuggability improvement =20 - This release fixes multiple bugs in virsh and libvirt in handling of + This release fixes multiple bugs in virsh and lbvirt in handling of migration arguments and XMLs and modifies error reporting for better debugging. =20 @@ -1156,7 +1172,7 @@ v10.0.0 (2024-01-15) =20 * qemu: Be less aggressive when dropping channel source paths =20 - Another regression is resolved, (introduced in 9.7.0) when libvirt was= too + Another regression is resoled, (introduced in 9.7.0) when libvirt was = too aggressive when dropping parsed paths for sources =20 * qemuDomainChangeNet: Reflect trustGuestRxFilters change @@ -1183,7 +1199,7 @@ v9.10.0 (2023-12-01) =20 QEMU allows creating images where the 'backing file format' is actuall= y a protocol name such as 'file'/'host_device'/'nbd'/etc.. Adapt libvirt to - properly handle such images and don't assume automatic format probing = is + properly handle such imags and don't assume automatic format probing is necessary, which is in many cases forbidden due to security implicatio= ns. =20 * **Bug fixes** @@ -1417,7 +1433,7 @@ v9.5.0 (2023-07-03) =20 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. + device was removed from the VM butnot the definition. =20 * qemu: Fix NUMA memory allocation logic =20 @@ -1533,14 +1549,14 @@ v9.3.0 (2023-05-02) Recent changes to UEFI firmware handling resulted into breaking support for inactive internal snapshots of VMs with UEFI which historically wo= rked. (Although the intention was to disallow them together with active ones= , but - the check did not work properly.) + the check did not work properl.) =20 Preserve existing functionality by allowing such snapshots explicitly. =20 * qemu: Properly configure locked memory limit for VMs with ``