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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id A8F6D6DE32 for ; Thu, 19 Aug 2021 15:25:40 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 92D7C26E41 for ; Thu, 19 Aug 2021 15:25:10 +0200 (CEST) Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 DE29727BD9 for ; Thu, 19 Aug 2021 15:21:32 +0200 (CEST) Received: by mail-lj1-x22d.google.com with SMTP id q21so11539285ljj.6 for ; Thu, 19 Aug 2021 06:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=korzeniewski-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=6dPqg0U4HHeCmC3DWeIowHH32GBiHWS14iTZzZP9+y8=; b=LPiA8qZoYAmceNfAlB/WYXwO2zzferUL0yGjaE/yTMN/wEczhG2kuRqWsbC8c0aj2I INbuIzh6eq0H8KtPBunA3RdYgQLT9aIv5E1AXHIGXdq7EDSv+q6tBVU68bKw/7w0Cq5+ LjC46XjwppCJQlIAbU/uXtl0fvc39Sv4yScI/hGvNMkc+aDIW3adXSFoI7K1XaZKtuea myZFmB874IIwLwH8/Gw80EjmIQ6hg4Z9jLahlRF2smSe9aqIpDL9g7ujeSSphbym60bE ekUkz7jPmA4TBeaU+on4Ja8EE5LoBxtIRVxsPu70ZDQteWXMz/CfhK2IPQi9cYoB+7Pe jzcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6dPqg0U4HHeCmC3DWeIowHH32GBiHWS14iTZzZP9+y8=; b=JwseBgpZmtSVqNUDCvwDDT9a+4mWMmEDEw+vx1mHNFzrhDs59nUGaOHsBbr6fh1FXe fH9fJGMQjHEDaycYAg6611Zow4Jmm1VucDTnO+1ndaOFot2qiffU1maKa0//DsOL+Cz8 a2bDvDQpBgzuh5qECxmo6EZgqLv06RhM5NwTB7Y8UWaDCiQXkrE3pKsHydVCzekno1Qu bzrp+PtrjJSL9UWjupSdPes4cn+gJEMtvRrTVnio3311E1ec2ikPDQql3djnGnQQAKzJ tT6++P+O+pMjEQjRIRQ3zhC+rpHdIP69E3qt9+pD73bS2JzAkNo6bde+uvnvEvI3JDtc jE8A== X-Gm-Message-State: AOAM532Vqe07WjSNGs5VDYbbcWkwQR7j+O8nl1I6jBPJlXNy0g+wvwo1 zkgVBdAPF6EsISb3VJhiWr4z8CF1OeLAWm3Bfsr7TEKE5Z33RwWP X-Google-Smtp-Source: ABdhPJw1xoO4iDUB8mS0l5l9JFnxS/ebwaDNjJsAyjtRPpyFE6/eq5yCen/5dAlklSKDu0CNxV3G31+61Ipm3Jl6Dfw= X-Received: by 2002:a2e:98d1:: with SMTP id s17mr7217290ljj.138.1629379284821; Thu, 19 Aug 2021 06:21:24 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?Q?Rados=C5=82aw_Korzeniewski?= Date: Thu, 19 Aug 2021 15:21:14 +0200 Message-ID: To: pve-devel@lists.proxmox.com 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: [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: Thu, 19 Aug 2021 13:25:40 -0000 Hello, I'm working on implementing VM incremental backup for a 3-party solution based on Qemu dirty bitmap which is available in Proxmox. Unfortunately I'm unable to make it working, so I decided to ask for some help. First I'm adding a dirty bitmap using the `block-dirty-bitmap-add` command and making a full backup with `drive-backup` command. Both are executed in transactions. The bitmap is successfully added. But the external backup file is populated with ~193K of data and hung. The backup job is added and QMP returns 3 events: `"status": "created"`, `"status": "running"`, `"status": "paused"`. I'm not sure why. As finally the job is "paused", I try to resume it with `block-job-resume` command the `query-block-jobs` returns `"status": "paused"` i `"paused": true`. All I can do is to cancel the job with the `block-job-cancel` command. No commands return any error. 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