In use version is Proxmox 5.2. After a kvm VM is migrated online (a.k.a. live) between proxmox nodes, a larget time offset is visible inside guest. Sometimes even up to 5 minutes. The VM is CentOS 6 or 7.
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
kvm-clock
ntpd is running on host and the vm but the difference is too big and it gets correct in long time. Does proxmox provide anything to synchronize time after the VM starts running on the target node ?
I see kvm provides 'guest-set-time' command when qemu-guest-agent is running inside the guest but proxmox doesn't issue this command and the 'qm agent' doesn't support it.
Maybe some other method exists to sync the time just after live migration ?
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
kvm-clock
ntpd is running on host and the vm but the difference is too big and it gets correct in long time. Does proxmox provide anything to synchronize time after the VM starts running on the target node ?
I see kvm provides 'guest-set-time' command when qemu-guest-agent is running inside the guest but proxmox doesn't issue this command and the 'qm agent' doesn't support it.
Maybe some other method exists to sync the time just after live migration ?