Clock and Uptime Discrepancy Between Proxmox VE Host and Virtual Machine

powersupport

powersupport

Well-Known Member
Jan 18, 2020
319
6
58
30
Hi,


I’m encountering a time synchronization issue between one of our Proxmox VE hosts and its virtual machine.



Environment:


  • Proxmox VE Host: PVE-SGTNAPAPP02
  • Virtual Machine: SGTNAPAPP02.tina.gebgd.org
  • Date Observed: 10 October 2025


Issue Details:


  1. There is a 2-hour clock difference between the Proxmox VE host and the VM.
    • VM local time: Fri 2025-10-10 08:54:37 +08 (Synchronized=yes, NTP=yes)
    • PVE shows a different time reading.
  2. Uptime is inconsistent:
    • Host uptime: 42 days
    • VM uptime: 14 days
    • Both systems report NTP synchronization as active.
  3. The discrepancy may indicate an issue with time synchronization or clock source configuration between the host and guest VM.
  4. I’ve attached a screenshot (PVE-SGTNAPAPP02_Uptime_SS_10102025.png) and a document (624935 - PVE and VM uptime not synchronize.docx) showing the mismatch.


Checks Performed:


  • Verified NTP and timezone configuration on both host and VM.
  • Collected outputs:
    • timedatectl
    • cat /etc/timezone
    • pveversion -v | grep pve-manager
  • Confirmed VM is Linux-based.
  • Ensured both show Synchronized=yes and NTP=yes.

Despite these checks, the time and uptime mismatch remains.




Could you please anyone advise on the possible causes of the following issues:


  • A 2-hour clock drift between the Proxmox host and the guest VM.
  • An uptime discrepancy, where the host shows 42 days and the VM shows 14 days.

Anyone Kindly provide guidance on how to permanently resolve these issues.


Thank you.
 

Attachments

  • PVE-SGTNAPAPP02_Uptime_SS_10102025.png
    PVE-SGTNAPAPP02_Uptime_SS_10102025.png
    21.7 KB · Views: 9
How are you reading "VM local time"? Do you log in to a shell, do you send a command to the agent, something else? About 99% of the time when there is a time discrepancy of an exact number of hours or half-hours and NTP is synchronized, it is a time zone problem.

The uptime can obviously be different since the VM can be rebooted/restarted independently of the host. So that means nothing.
 
Hi,

BobhWasatch said:
The uptime can obviously be different since the VM can be rebooted/restarted independently of the host. So that means nothing.
Click to expand...
The uptime from the GUI/Host and from inside the VM can be different, since when the VM is just rebooted the qemu process doesn't restart (unless you lunch the restart from the Gui (or qm command).

Best regards.
 
You must log in or register to reply here.
Top Bottom