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 8904F1FF14C for ; Fri, 12 Jun 2026 14:30:27 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D7EFE1295D; Fri, 12 Jun 2026 14:30:23 +0200 (CEST) From: Jakob Klocker To: pve-devel@lists.proxmox.com Subject: [PATCH manager/qemu-server 0/2] fix #5032: sync guest time after restore from saved state Date: Fri, 12 Jun 2026 14:29:40 +0200 Message-ID: <20260612122942.181958-1-j.klocker@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.030 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS 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 Message-ID-Hash: E74MBG6ZNON2TOOF7UCKX2Y5EB7AICAV X-Message-ID-Hash: E74MBG6ZNON2TOOF7UCKX2Y5EB7AICAV X-MailFrom: root@dev.proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Jakob Klocker X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: This series adds a new agent option set-time-on-resume to automatically synchronize the guest clock via the QEMU Guest Agent after operations that can leave the guest time stale. The option is enabled by default when the QEMU Guest Agent is configured. When a VM is restored from a saved state (hibernation or snapshot with RAM), the guest clock continues from the point the state was saved and no longer matches wall-clock time. The same skew can appear after creating a snapshot of a running VM. For guests whose OS does not correct this on its own, the drift persists until the next NTP sync (if any), which can cause problems for time-sensitive workloads. This series introduces the set-time-on-resume agent option and triggers a guest-set-time call: * after restoring a VM from a saved state or snapshot with RAM * after taking a snapshot The option is exposed in the VM configuration GUI so it can be toggled per guest. This series depends on [0] being applied first. [0] https://lore.proxmox.com/pve-devel/20260612100758.116697-1-j.klocker@proxmox.com/T/#u Link: https://bugzilla.proxmox.com/show_bug.cgi?id=5032 qemu-server: Jakob Klocker (1): fix #5032: qemu: sync guest time on resume and snapshot of saved state src/PVE/QemuConfig.pm | 7 ++++++ src/PVE/QemuServer.pm | 10 ++++++++ src/PVE/QemuServer/Agent.pm | 47 +++++++++++++++++++++++++++++++++++++ 3 files changed, 64 insertions(+) pve-manager: Jakob Klocker (1): fix #5032: ui: qemu agent: add set-time-on-resume option www/manager6/Utils.js | 2 ++ www/manager6/form/AgentFeatureSelector.js | 18 ++++++++++++++++++ 2 files changed, 20 insertions(+) Summary over all repositories: 5 files changed, 84 insertions(+), 0 deletions(-) -- Generated by murpp 0.12.0