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 556016E6CE for ; Tue, 24 Aug 2021 12:59:00 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 42BA82C445 for ; Tue, 24 Aug 2021 12:58:30 +0200 (CEST) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 AD4B62C431 for ; Tue, 24 Aug 2021 12:58:29 +0200 (CEST) Received: by mail-lj1-x231.google.com with SMTP id c12so36910454ljr.5 for ; Tue, 24 Aug 2021 03:58:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=korzeniewski-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ks5OsH63CclxUtFtPM7wnT6q03SA0bv941KH6quC4+E=; b=y8YPqY4B1RWxgE9W1P7pXjwiIBPOLcnL8OmT4dXOryEkLrSu8owlCHTTo4y6JaX3Ul zYi0aGi/SIm4fjHoyVfHINPr/6QxFF+oVAQ/oFfk2/85366o4DkzmY/jCFIn41Wng0Kp 3Q+fkEVsfZWyGHyljyeKohiIIKZl90hgArNS88XS/3AQWQ3AnF0GcGx9xDk+EkdxzjER pqwBXrCYxIKZrGS5XcFyPedazf/ls3suiz3n+lXOl4Z3NYH7zxU2BMDzss5r/wzkdDO2 Ksl947xH847rj1NyK095cZhhboYCRncAg/1L2ZzoRVbBKTuLEKVJnXSpuUNxY8D2cU+W qqcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ks5OsH63CclxUtFtPM7wnT6q03SA0bv941KH6quC4+E=; b=P5sLmKL3R/xr32dvVySvWxnjL4huBrEvV3XQEEQj8NonGEW3H4Rw9YilvOURid358/ vsK7UT2gk1fSGqu0OUjlLwkFGaxo+YKVtUltqhV/tIFHy7wmY7BN5xGnHFRNMmMx38mW LFZKhDcUp2X1AttrjqsN3hecnnz7O96Khi+oAizjEfK0708dbtR5Q3kt83h/HmEUe9EB 4mdL41oqlH1p+FA+ygC8/Nfdt4SiTJXI+nN1Nv5T9wmKV/WvHWuCkteWCSqoYliqipBb 6q69dldqM6w/Y5fDmQ3tSPwe5sArI6h5K9ql/lZslzP22kJFNBXwkC+YbebXsjLzeTrm ci/g== X-Gm-Message-State: AOAM533mOvfhpCFKoPT+631Xf1tv4rl31ybwRKtXYzjNxbdzG2R8FwPg ugRpcQYiinUxuhNC43vyecBXuLsRxrioVJq3WWstkyS3rWi5udRn X-Google-Smtp-Source: ABdhPJx4cHdK4QhA/zn5yn1dnT1CTmUKk9dUGuPSakNEiZN1pc8EZWrWha0ST/01jZZZB7iBWBMkWm9tUKgJfQ+p9Ic= X-Received: by 2002:a2e:bd09:: with SMTP id n9mr31768614ljq.76.1629802702959; Tue, 24 Aug 2021 03:58:22 -0700 (PDT) MIME-Version: 1.0 References: <6bd6cbed-5519-cb7e-628c-13e934639652@proxmox.com> In-Reply-To: <6bd6cbed-5519-cb7e-628c-13e934639652@proxmox.com> From: =?UTF-8?Q?Rados=C5=82aw_Korzeniewski?= Date: Tue, 24 Aug 2021 12:58:12 +0200 Message-ID: To: Stefan Reiter Cc: Proxmox VE development discussion X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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 HTML_MESSAGE 0.001 HTML included in message 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_NONE 0.001 SPF: sender does not publish an SPF Record Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [pve-devel] VM Incremental backup for 3-party solution (Qemu) 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: Tue, 24 Aug 2021 10:59:00 -0000 Hello, czw., 19 sie 2021 o 16:22 Stefan Reiter napisa=C5=82= (a): > But more importantly, 'drive-backup' and the bitmap support around that > are not based on our code, they are from upstream QEMU. We implement the > 'backup' and 'query-backup' QMP calls. > So, did you "change" the upstream feature when implementing your own? > There's nothing against using the native calls if they fit your use case, > but for support it would make more sense to contact upstream and read > through their documentation :) > Thanks for the tips. I already read the Qemu documentation and I'm able to make a successful full + incr backup using a "stock" Qemu with my procedure. So I assume the procedure is fine. Then I decided to ask a question here as it is not working with Proxmox, so I suspect that something changed between upstream and Proxmox distributions= . I'm not a Proxmox developer, so finding what is not working on Qemu hypervisor is hard. Back to my main question: Do you have any idea why the job fell into a paused state and how I should proceed? --=20 Rados=C5=82aw Korzeniewski radoslaw@korzeniewski.net