From nobody Fri Apr 26 21:11:23 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=1619531036; cv=none; d=zohomail.com; s=zohoarc; b=ZZesmmfpgI6hx1Ik5JFhpAApSx0feYAMuRxwwH3S6E0f81fEo62k/NwrhQnzinCTEpr5+GlIAz9UNbo2NPo/zhqyyCaFzBZjYAPg4cB0h4WWaD0EaFZWFsHbPEU5i2+bt+0mYvpjo99YiTn0uwKctyzLRPhebNbBew8s0FqachA= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1619531036; 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=ypjfGdr62fIoWikVGXBhbdGNTdVsDfCYGFzjjjoXboY=; b=fg5cCfUSimqexdjYahQApVlFHsQMR+sr7tw4dwlnIqydjBJYMIBEtubd04Pfx/hH8xj7TQV7OkBQDttq4lM/q5NURcRozIwWTVHKfNO66UBl/9xhGK1e8IwfhKt/vDLZD0QZoLRrAKSvSXXMtts67VRtje4kYlR6IvhfYlMzb18= 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) header.from= 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 1619531036359366.55212919600035; Tue, 27 Apr 2021 06:43:56 -0700 (PDT) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-82-poAzpEP3OiuQ2uQwt5B85g-1; Tue, 27 Apr 2021 09:43:51 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E2A0C1008060; Tue, 27 Apr 2021 13:43:46 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 05C6061140; Tue, 27 Apr 2021 13:43:46 +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 09CDE44A58; Tue, 27 Apr 2021 13:43:42 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 13RDbveQ024430 for ; Tue, 27 Apr 2021 09:37:58 -0400 Received: by smtp.corp.redhat.com (Postfix) id EE9EB19CBE; Tue, 27 Apr 2021 13:37:57 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.53]) by smtp.corp.redhat.com (Postfix) with ESMTP id 531346064B for ; Tue, 27 Apr 2021 13:37:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1619531034; 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=ypjfGdr62fIoWikVGXBhbdGNTdVsDfCYGFzjjjoXboY=; b=PLJhtXT24kO5Tm0OMiOfyFxbNYW3N03Dg/ypyeh9CgMfXpsnI8jAYLwtTLscS3f2E+UAnx JZM7sxsTVqkiXQdYMOj9ppgA0EPxNYCuknRrlPjTbP/WTFOrw18cr1T+DU+J7AJM+BPHjT AbxE0okqs3/5i09mSs9Ql6ZoVwayR/Y= X-MC-Unique: poAzpEP3OiuQ2uQwt5B85g-1 From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH] NEWS: Mention notable changes Date: Tue, 27 Apr 2021 15:37:52 +0200 Message-Id: <724f9ea73ccf2e2d3bdaa8b53956e969bbe93344.1619530672.git.pkrempa@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-loop: libvir-list@redhat.com 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: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) Content-Type: text/plain; charset="utf-8" Add entries for deprecation_behavior, improving of errors from virsh's snapshot helpers and other bugfixes. Signed-off-by: Peter Krempa Reviewed-by: Jonathon Jongsma --- NEWS.rst | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 5f8b0ae02d..4a5e2c9fd4 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -18,10 +18,58 @@ v7.3.0 (unreleased) The xen driver now supports domains with more than 4TB of memory with xen >=3D 4.13. + * qemu: Allow use of qemu's ``-compat`` option + + Curious developers or testers now can enable certain ``-compat`` modes= which + allow to notice use of deprecated commands and options as qemu will us= e the + selected method to notify the user. The new behaviour can be requested= using + either the ``deprecation_behavior`` option in ``qemu.conf`` for all VM= s or + using ```` in the VM XML. + * **Improvements** + * virsh: Improve errors with ``virsh snapshot-create-as`` + + The XML constructed by virsh was forced through RNG schema validation = which + yielded unintelligible error messages in cases such as when the path to + the new image was not starting with a slash. XMLs are no longer valida= ted + as the XML parser actually has better error messages which allow users= to + figure the problem out quickly. + + * qemu: Terminate backing store when doing a full-chain block pull + + When pulling everything into the overlay image the chain can be termin= ated + since we know that it won't depend on any backing image and thus can p= revent + attempts to probe the backing chain. + * **Bug fixes** + * qemu: Fix crash of libvirt on full block pull of a disk + + When the persistent definition contains a compatible disk (meaning the + definition of the running and persistent config match) a block pull job + would leave a dangling pointer in the config definition which resulted + in a crash. + + * qemu: Use proper job cancelling command + + Libvirt's API contract for aborting a block copy job in 'ready' state + declares that the destination image of the copy will contain a consist= ent + image of the disk from the time when the block job was aborted. This + requires that libvirt uses the proper cancelling qemu command to ensure + that the data is consistent which was not the case. + + * qemu: Don't attempt storage migration when there are no migratable dis= ks + + Due to a logic bug introduced in the previous release libvirt would at= tempt + to migrate disks in case when no disks are selected/eligible for migra= tion. + + * qemu: Fix very rare race when two block job 'ready' events are deliver= ed + + In certain high-load scenarios, qemu might deliver the 'ready' event t= wice + and if it's delivered when pivoting to the destination during a block = copy + job, libvirt would get confused and execute the code as if the job were + aborted. v7.2.0 (2021-04-01) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 2.30.2