upvote
I don't recall the details but one of the historical problems with VPSes is that people were trying to use things like openvz VPSes which are more like a glorified chroot/jail, rather than something like a QEMU/KVM VPS (or Xen PVH, or Xen HVM with virtualization extensions).

I still personally wouldn't try to run an NTP server on a VM unless I also owned/controlled the bare metal hardware the hypervisor is running on.

reply
KVM allows chrony to adjust the clock, which give much better stability. With other VMs you can have a very jumpy clock and poor time service.

Some decent discussion on this topic (though with broken links to a separate NTP Pool discussion) here: https://a.osmarks.net/content/serverfault.com_en_all_2022-11...

reply
I'm not sure if I would call answers from 2016 'recent' as KVM linux-on-linux has advanced significantly in the years since then, particularly with improvements focused on performance in something like a 6.1.x kernel in a theoretical scenario like a debian trixie host (proxmox 9.2 or whatever) and a trixie or fedora 44/45 guest.
reply
Touche, but the main point is KVM is fine for NTP timing. I don't think I'd try to virtualize a PTP server, that still needs to be closer to the physical hardware.
reply