From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id DB68274755 for ; Wed, 2 Jun 2021 08:40:33 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C58592F6D4 for ; Wed, 2 Jun 2021 08:40:03 +0200 (CEST) Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 023F92F6C7 for ; Wed, 2 Jun 2021 08:40:01 +0200 (CEST) Received: by mail-wm1-x332.google.com with SMTP id b145-20020a1c80970000b029019c8c824054so3007386wmd.5 for ; Tue, 01 Jun 2021 23:40:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=odiso-com.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:user-agent:mime-version :content-transfer-encoding; bh=Z2UIMxv/mkfxAwyPCrDI6Rwr7Fk5fwaZ/1vjGfFtafs=; b=fqAG8rL3N8Ie5aOtQRG2wvdraujGxRSbSXBkkhetYn2Ie/MmWLOV6Hskkx8HhKOXjj hZwY/4Js4ul2F5fjIz/DgYG/5OcHjAMD7BRNyOEDNCcFIz55EmuCzwrxHDIT/mQ6rKhv 9t28ncXnGALrEpi8rObD+TDITXTeepe+GDVKVC41fmvBw6BvkKOsH3TfKX3orzHawQAM J/T91qsMJNWomEccOIP4mWme782KcBX6nOy3atBPcgJ+t+D396hWpjd0dzFKGaims/Gi KB7mY9TuUBt5646Ox6Rirdh/W9/Xzbx4e8GUNk2MU3+/8eaYIvYJSjJ9AxMlfDKHquQH CaTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:user-agent :mime-version:content-transfer-encoding; bh=Z2UIMxv/mkfxAwyPCrDI6Rwr7Fk5fwaZ/1vjGfFtafs=; b=bUTiGiVrBTRgOFo8y5BKNTtmuJZsEqKuYlBehZB4wJZ0pf7Owxs45PFHj/BrfyPr1s gczsmiP6Nj4/09sj/RwHh9gTP5P0u76l++c/zxi1hiCe1SPADMT1xHkk1JI+mdfekHFv /Qf2Tqw4cQ15foQqOUIqOSejtaiJE/Fcilq8Pg53dPSutHLFpQ9TF9w7KHPgg+0rj2ti nDI7iUV63p+IqaIU5TTBTy65ROx8/R5/v+Uq6aj5G2oVTJYfR6qrPl2G9bcjQUVUfe6R dwsGPSIfEKMOnM4PAIGFMBEs0L+u8vkI+nG6ctFAO1tYaCTWHcaHpGLuu0NIgGlPyw4E 66qQ== X-Gm-Message-State: AOAM530N41gBDT66ycaCLIyfGfdWo2yEvE6VrHpIsJsgdYNrxqu/YWmS m9cctC7TPq7nksKQ8d7NZ6HRdGAQ0wVJuPKf X-Google-Smtp-Source: ABdhPJxKZzb8UxQp1r16mLhtBZ2vduC55c8osjytLST62UUcVVtJaUTx5/lH3LOGd1tw3cJ5lvDE9Q== X-Received: by 2002:a1c:1dd5:: with SMTP id d204mr3480037wmd.140.1622615994346; Tue, 01 Jun 2021 23:39:54 -0700 (PDT) Received: from ?IPv6:2a0a:1580:0:1::100c? (ovpn1.odiso.net. [2a0a:1580:2000::3f]) by smtp.gmail.com with ESMTPSA id v10sm6116703wre.33.2021.06.01.23.39.53 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 01 Jun 2021 23:39:54 -0700 (PDT) Message-ID: <30b3e3feb72fa3c4c209d1ab64e07512676910a2.camel@odiso.com> From: aderumier@odiso.com To: pve-devel Date: Wed, 02 Jun 2021 08:39:52 +0200 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.071 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] qemu 6 : does proxmox backup handle parallel async chunck backup like the new backup code from qemu 6.0 ? X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2021 06:40:33 -0000 Hi, I was looking for qemu 6.0 new features, and it seem that they have implement parallel async chunks backup (and I think for other block operations, through a new block-copy feature) https://github.com/qemu/qemu/commit/71eed4cebed487a4f3c9f97aba83c611bbe22f8d https://github.com/qemu/qemu/commit/de4641b46b020c5b332175f80e8bfe3d352888e8#diff-b33323044f2699244c126c6eae6c4083c3c99a16f4840030ac13238b1f569dc0 https://github.com/qemu/qemu/commit/26be9d62dd5f5268b814da24fd8e8b5c5b999ebe Is it alrealy implemented or on the roadmap for the proxmox backup code ? (To be honest, I didn't follow proxmox backup patches since a long time, so I really don't known how much they are sharing with qemu backup code) Regards, Alexandre