From: Jakob Klocker <j.klocker@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: superseded: [PATCH manager/qemu-server v2 0/2] fix #5032: sync guest time after restore from saved state
Date: Thu, 2 Jul 2026 12:35:20 +0200 [thread overview]
Message-ID: <f3bc8692-5eb6-4c32-a5e9-9ed4b36b326a@proxmox.com> (raw)
In-Reply-To: <20260622134711.108611-1-j.klocker@proxmox.com>
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]
prev parent reply other threads:[~2026-07-02 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 13:47 [PATCH manager/qemu-server v2 0/2] fix #5032: sync guest time after restore from saved state Jakob Klocker
2026-06-22 13:47 ` [PATCH qemu-server v2 1/2] fix #5032: qemu: sync guest time on resume and snapshot of " Jakob Klocker
2026-06-24 11:31 ` Fiona Ebner
2026-06-25 7:46 ` Jakob Klocker
2026-06-25 8:10 ` Fiona Ebner
2026-06-22 13:47 ` [PATCH pve-manager v2 2/2] fix #5032: ui: qemu agent: add set-time-on-resume option Jakob Klocker
2026-06-23 14:10 ` [PATCH manager/qemu-server v2 0/2] fix #5032: sync guest time after restore from saved state Michael Köppl
2026-07-02 10:35 ` Jakob Klocker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3bc8692-5eb6-4c32-a5e9-9ed4b36b326a@proxmox.com \
--to=j.klocker@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox