I have proxmox 8.3.0 recently installed, and things have been great.
Recently I deployed 7 vms to be used by a kubernetes cluster. Everything has been working great until ...
I deployed a database which spanned across a few of the vms, because of time sync issues.
I installed qemu-guest-agent on each of the vms which initially synced up time on each of the vms.
Given that proxmox uses chrony (in this case all 3 servers with a default installation) and the vms have a qemu agent installed on them, which I would think would sync them to the proxmox host, why would the time of the vms be getting out of sync?
Recently I deployed 7 vms to be used by a kubernetes cluster. Everything has been working great until ...
I deployed a database which spanned across a few of the vms, because of time sync issues.
I installed qemu-guest-agent on each of the vms which initially synced up time on each of the vms.
Given that proxmox uses chrony (in this case all 3 servers with a default installation) and the vms have a qemu agent installed on them, which I would think would sync them to the proxmox host, why would the time of the vms be getting out of sync?
Code:
F0303 18:41:30.014338 117 hybrid_clock.cc:181] Too big clock skew is detected: 0.731s, while max allowed is: 0.500s; clock_skew_force_crash_bound_usec=60000000
Last edited: