3 ms·
Especially because as of a year ago, Hyper V still had terrible, terrible, time support. Kernel logs are filled with spam about the clock being jumped. Time syn
by MichaelGG 9y ago
Especially because as of a year ago, Hyper V still had terrible, terrible, time support. Kernel logs are filled with spam about the clock being jumped. Time sync constantly drifts seconds all over.
Compared to our Linux VMs on GCP, which get millisecond sync and stay that way because NTP actually works on whatever platform they use.
It's shocking that Windows still has no proper NTP support and people are OK with their clocks being so off. Makes logging and debugging certain issues a bigger pain.
- kyberias 9y agoI'm not so sure Azure is running Hyper-V, like the same that comes as part of Windows. So any Windows Hyper-V limitations might not apply to Azure and vice versa.