From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <c.heiss@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))
(No client certificate requested)
by lists.proxmox.com (Postfix) with ESMTPS id 5782394417
for <pve-devel@lists.proxmox.com>; Thu, 23 Feb 2023 15:18:42 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 391AB256B3
for <pve-devel@lists.proxmox.com>; Thu, 23 Feb 2023 15:18:12 +0100 (CET)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
[94.136.29.106])
(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 firstgate.proxmox.com (Proxmox) with ESMTPS
for <pve-devel@lists.proxmox.com>; Thu, 23 Feb 2023 15:18:11 +0100 (CET)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 2AF6A482B0
for <pve-devel@lists.proxmox.com>; Thu, 23 Feb 2023 15:18:11 +0100 (CET)
From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Thu, 23 Feb 2023 15:18:02 +0100
Message-Id: <20230223141805.446192-1-c.heiss@proxmox.com>
X-Mailer: git-send-email 2.39.1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-SPAM-LEVEL: Spam detection results: 0
AWL -0.089 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more
information. [qemuserver.pm, proxmox.com]
Subject: [pve-devel] [PATCH v2 qemu-server/manager/docs 0/3] fix #4140: Add
option to disable QGA fs-freeze/-thaw on backup
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2023 14:18:42 -0000
TL;DR: On Windows guests, the QEMU guest agent calls into the VSS
(Volume Shadow Copy Service) subsystem, which has potential to mess up
applications which hook into this themselves like SQL Server, as
described in the bug report [0].
Building upon the proposal in that report, add an (default-enabled)
option to the QGA configuration to disable the behavior manually if
really needed. Due to its potential to wreak havoc, show the user a
warning when disabled.
[0] https://bugzilla.proxmox.com/show_bug.cgi?id=4140
v1: https://lists.proxmox.com/pipermail/pve-devel/2023-February/055656.html
Christoph Heiss (1):
vzdump: Add VM QGA option to skip fs-freeze/-thaw on backup
PVE/QemuServer.pm | 8 +++++++-
PVE/VZDump/QemuServer.pm | 6 ++++++
2 files changed, 13 insertions(+), 1 deletion(-)
Christoph Heiss (1):
ui: qga: Add option to turn off QGA fs-freeze/-thaw on backup
www/manager6/Utils.js | 2 ++
www/manager6/form/AgentFeatureSelector.js | 31 ++++++++++++++++++++++++++++++-
2 files changed, 32 insertions(+), 1 deletion(-)
Christoph Heiss (1):
qm: Add section explaining fs-freeze/-thaw QGA option
qm.adoc | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
--
2.39.1