From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 433D01FF165 for ; Sun, 20 Oct 2024 21:08:41 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 561E818E7F; Sun, 20 Oct 2024 21:09:16 +0200 (CEST) References: In-Reply-To: Date: Sun, 20 Oct 2024 21:08:54 +0200 To: Proxmox VE development discussion MIME-Version: 1.0 Message-ID: List-Id: Proxmox VE development discussion List-Post: From: Esi Y via pve-devel Precedence: list Cc: Esi Y X-Mailman-Version: 2.1.29 X-BeenThere: pve-devel@lists.proxmox.com List-Subscribe: , List-Unsubscribe: , List-Archive: Reply-To: Proxmox VE development discussion List-Help: Subject: Re: [pve-devel] [PATCH SERIES v2 pve-storage/qemu-server] add external qcow2 snapshot support Content-Type: multipart/mixed; boundary="===============3520602114968494074==" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" --===============3520602114968494074== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: X-Original-To: pve-devel@lists.proxmox.com Delivered-To: pve-devel@lists.proxmox.com 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 F2387C6E33 for ; Sun, 20 Oct 2024 21:09:14 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D9CF918E4D for ; Sun, 20 Oct 2024 21:09:14 +0200 (CEST) Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 for ; Sun, 20 Oct 2024 21:09:13 +0200 (CEST) Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-e297c8f8c86so3652488276.2 for ; Sun, 20 Oct 2024 12:09:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729451346; x=1730056146; darn=lists.proxmox.com; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=6yuwjVIqg1whwnqU7eQuDsItynIhuYa1r0Cao4S+Ksw=; b=iT4+BTeVDdfSBs2jJkUYMP3OI0f2lIYLRUmPRyl1bHW3y/r6GkirsMcF33/VgKt8YG 8JL4bP2ulU4XakfAidUerXqngNu2RYHg2iGVNh+iq7QfoW21VpclUAfu3UD7UV++7wWY T55pDNWHaa8KN2NWddGnFrIuyflHT33pQ55EYfqRygXpmEEsgTXu5VLCoCdOK+6dMPbG UErhumcqnLMyoAnUvn9vroTr/YneCybYAEvJ8MwUVaihLFjbdsrXktM9jNIcpI8O9Ize pcSKfMuvHDHTbQM6KXoe2LRIEwxvxJm1YHALVSdiYJbOLbog+fDPBbDOF6ijM/kBUOuV fMDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729451346; x=1730056146; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=6yuwjVIqg1whwnqU7eQuDsItynIhuYa1r0Cao4S+Ksw=; b=csiqtFxRpcZjzGIrS8bTPUWSnz2aD/IlNL0AUrrztCFU6b2li7HK3+EicMmsGW4oNm 0tWeiq7fpu10+w02LPFTMB7IgZcOxrzl1bsDbH0oqBHp6n73rZjfLa05w+omakgPvzUZ GzutCoNIgEw7/F9aEC/S7VKeqlvHSCXAbTwTvtd6EtS4ACzy7MlpVGLpL0KezJ1W64z/ z+yGAQtl4BX/QYDdIoW8VC2JGx4NTxSWRDKAPwsyAOFfJyi4mtVzLZBa6JPrOZwywSZa xhK38SBxwjYY/veyHnStZUtInQdxmNM6xwYD0/bQJP6agNF2QDxadPyvVMZs40V/i4oe 1MUg== X-Gm-Message-State: AOJu0Yw53PtwHdNkhXQFnYXsfjgM/dbyoxmlpejVtj0Edo8fnjr9n4QZ c6VrGleIBInepn408WTzh73q1mS54Trn4cA7y/ThNBxg6W1gAnOQ1/+7okQCKUf4ZkPm03GccL4 3AejLE0tO38n/Nl0YL5aIkLQ5hi7adqPO X-Google-Smtp-Source: AGHT+IEgm2qGipfWw1tO3pU6ArMR6a11BqTua9pSC97fvdGR1nZABtzT2YvtnJaA+J4HVZMlkCh559+uCNRHYRXlnAk= X-Received: by 2002:a25:748c:0:b0:e2b:c092:9268 with SMTP id 3f1490d57ef6-e2bc09293e5mr4997740276.56.1729451345911; Sun, 20 Oct 2024 12:09:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Esi Y Date: Sun, 20 Oct 2024 21:08:54 +0200 Message-ID: Subject: Re: [pve-devel] [PATCH SERIES v2 pve-storage/qemu-server] add external qcow2 snapshot support To: Proxmox VE development discussion Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL -0.267 Adjusted score from AWL reputation of From: address 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 DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy FREEMAIL_ENVFROM_END_DIGIT 0.25 Envelope-from freemail username ends in digit FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider KAM_ASCII_DIVIDERS 0.8 Email that uses ascii formatting dividers and possible spam tricks 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 QEMU was not designed to use internal snapshots "by default": https://wiki.qemu.org/Features/Snapshots Discussions on this are discouraged, to say the least: https://forum.proxmox.com/threads/blockdev-snapshot-sync-to-snapshot-a-raw-= file.38188/#post-712825 On Sun, Oct 20, 2024 at 7:39=E2=80=AFPM Roland privat via pve-devel wrote: > > > > > ---------- Forwarded message ---------- > From: Roland privat > To: Proxmox VE development discussion > Cc: > Bcc: > Date: Sun, 20 Oct 2024 19:34:05 +0200 > Subject: Re: [pve-devel] [PATCH SERIES v2 pve-storage/qemu-server] add ex= ternal qcow2 snapshot support > i never understood, why qemu has inline snapshot by default. from an ad= min perspective it simply sucks. for example you won=E2=80=98t know when = something goes wrong on removal, how much orphaned data is being left. fu= rthermore, the freezes on removal are a pita for us and we often avoid liv= e snapshot removal because of this. this is one of the reasons why i think= , proxmox isn=E2=80=98t on the same enterprise level like vmware. > > so, i strongly vote for inclusion of this feature and will happily test = it, when available > > regards > roland > > > Am 20.10.2024 um 15:04 schrieb DERUMIER, Alexandre via pve-devel : > > > > =EF=BB=BF > > > > _______________________________________________ > > pve-devel mailing list > > pve-devel@lists.proxmox.com > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > > > > > > ---------- Forwarded message ---------- > From: Roland privat via pve-devel > To: Proxmox VE development discussion > Cc: Roland privat > Bcc: > Date: Sun, 20 Oct 2024 19:34:05 +0200 > Subject: Re: [pve-devel] [PATCH SERIES v2 pve-storage/qemu-server] add ex= ternal qcow2 snapshot support > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel --===============3520602114968494074== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel --===============3520602114968494074==--