From nobody Sat May 4 22:41:38 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 207.211.31.81 as permitted sender) client-ip=207.211.31.81; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-1.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.81 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=1584106029; cv=none; d=zohomail.com; s=zohoarc; b=adk5TdsJHgYkST34oTKY0Ktd4YRzZvAwcbWZX6gjgYG3bh/7ojPWy3RsKW8fCYXVX61yLlzwjbQOgCjobYsxSebX6vwXRmi6qeLhx7x1BwqriUEEqNV4Bhl35rSvcm6QuQTzOQQDf8UMBczqNbOqn0UQ8tPGYFp3lH59Zj8jQdc= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1584106029; 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=FQUVDZvzL5LjlA3xsmvTWDZQUQAjJqxcxtfTLSQ4bKA=; b=Q5KwQ/3LCgYPSK0YtrJLQeU9NQLZ4iX0XRscvURiCENdl/QSftZ9U9N8wzXndTNGLPy+1i3wZg0aKNuDHccvdkH/BaD1eS4yOy+brjfUrHJyCmBim0xzMp1GUWJV3Q+iLA/cVo3E4YK/n/mYJG4Kmukx/lC4uGHrxD8ru7HkRy4= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.81 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-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) by mx.zohomail.com with SMTPS id 1584106029372238.4523418794589; Fri, 13 Mar 2020 06:27:09 -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-435-PqXMVyZiPya4i85PmmYE4A-1; Fri, 13 Mar 2020 09:27:06 -0400 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 mimecast-mx01.redhat.com (Postfix) with ESMTPS id DCA901137846; Fri, 13 Mar 2020 13:26:59 +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 0872A5DA60; Fri, 13 Mar 2020 13:26:59 +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 7469518089C8; Fri, 13 Mar 2020 13:26:56 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 02DDQsUX004071 for ; Fri, 13 Mar 2020 09:26:54 -0400 Received: by smtp.corp.redhat.com (Postfix) id E1AA860F89; Fri, 13 Mar 2020 13:26:54 +0000 (UTC) Received: from angien.redhat.com (unknown [10.43.2.48]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2D7EE67154; Fri, 13 Mar 2020 13:26:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1584106028; 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=FQUVDZvzL5LjlA3xsmvTWDZQUQAjJqxcxtfTLSQ4bKA=; b=Wc88VFgOtg8ycbkfg7vpdEfJmXm520lpH1+P8BGi5r1ogKaZbVnaOhrvwsybOhIyWwVMZM Yv05mjp9aWcWOwGn6NkQf5y5ytYilCyZW/zFHIcg6A6cynYVRwGSDuJ/tmPptYRVkluLOL pgjimaIOmi5aFovUQrywTCylllzBqBA= X-MC-Unique: PqXMVyZiPya4i85PmmYE4A-1 From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH] news: Mention regression in virDomainBlockCopy with shallow/reuse flags Date: Fri, 13 Mar 2020 14:26:49 +0100 Message-Id: <941a60d004140cf082e1fc1cce2d75e04773cd1a.1584106009.git.pkrempa@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 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.14 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" Signed-off-by: Peter Krempa Reviewed-by: Kashyap Chamarthy --- docs/news.xml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/news.xml b/docs/news.xml index 7fd88f9998..92103ec308 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -48,6 +48,23 @@
+ + + qemu: Open backing chain late for shallow block copy reusing ext= ernal images + + + With introduction of -blockdev specification of storage for qemu= VMs + in libvirt-5.10 we've started opening the backing chain of the + destination/mirror of a virDomainBlockcopy started with + VIR_DOMAIN_BLOCK_COPY_REUSE_EXT | VIR_DOMAIN_BLOCK_COPY_SHALLOW = flags + when starting the job rather than when virDomainBlockJobAbort wi= th + VIR_DOMAIN_BLOCK_JOB_ABORT_PIVOT is issued. For users depending = on + this undocumented quirk this caused a regression in behaviour as + the backing chain could not be modified while the copy of the top + image was progressing. Note that this fix also requires qemu-5.0= while + -blockdev is used starting from qemu-4.2. + +
--=20 2.24.1