From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 1E4221FF135 for ; Thu, 02 Jul 2026 12:35:57 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 4FC60213E1; Thu, 02 Jul 2026 12:35:56 +0200 (CEST) Message-ID: Date: Thu, 2 Jul 2026 12:35:20 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: superseded: [PATCH manager/qemu-server v2 0/2] fix #5032: sync guest time after restore from saved state To: pve-devel@lists.proxmox.com References: <20260622134711.108611-1-j.klocker@proxmox.com> Content-Language: en-US From: Jakob Klocker In-Reply-To: <20260622134711.108611-1-j.klocker@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1782988514629 X-SPAM-LEVEL: Spam detection results: 1 AWL 1.138 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: XNO2BPIH6QJ5UAAIEWHP73SVJAAPC5YL X-Message-ID-Hash: XNO2BPIH6QJ5UAAIEWHP73SVJAAPC5YL X-MailFrom: j.klocker@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 X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Superseded-by: https://lore.proxmox.com/all/20260702103201.164567-1-j.klocker@proxmox.com/T/#u On 6/22/26 3:47 PM, Jakob Klocker wrote: > 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. [snip]