@@ -71,7 +71,7 @@ There are some basic commands for checking your time synchronization configurati
71
71
Check to see if the integration service (hv_utils) is loaded.
72
72
73
73
``` bash
74
- lsmod | grep hv_utils
74
+ $ sudo lsmod | grep hv_utils
75
75
```
76
76
You should see something similar to this:
77
77
@@ -89,13 +89,13 @@ install the updated driver. When the PTP clock source is available, the Linux de
89
89
See which PTP clock sources are available.
90
90
91
91
``` bash
92
- ls /sys/class/ptp
92
+ $ ls /sys/class/ptp
93
93
```
94
94
95
95
In this example, the value returned is * ptp0* , so we use that to check the clock name. To verify the device, check the clock name.
96
96
97
97
``` bash
98
- cat /sys/class/ptp/ptp0/clock_name
98
+ $ sudo cat /sys/class/ptp/ptp0/clock_name
99
99
```
100
100
101
101
This should return ` hyperv ` , meaning the Azure host.
@@ -141,7 +141,7 @@ makestep 1.0 -1
141
141
Here, chrony will force a time update if the drift is greater than 1 second. To apply the changes restart the chronyd service:
142
142
143
143
``` bash
144
- systemctl restart chronyd && systemctl restart chrony
144
+ $ sudo systemctl restart chronyd && sudo systemctl restart chrony
145
145
```
146
146
147
147
### Time sync messages related to systemd-timesyncd
@@ -160,7 +160,7 @@ Aug 1 12:59:45 vm-name systemd-timesyncd[945]: Synchronized to time server 185.
160
160
You can disable it by using:
161
161
162
162
```bash
163
- systemctl disable systemd-timesyncd
163
+ $ sudo systemctl disable systemd-timesyncd
164
164
````
165
165
In most cases, systemd-timesyncd will try during boot but once chrony starts up it will overwrite and become the default time sync source.
166
166
193
193
driftfile /var/lib/chrony/chrony.drift
194
194
logdir /var/log/chrony
195
195
maxupdateskew 100.0
196
- refclock PHC /dev/ptp_hyperv poll 3 dpoll -2
196
+ refclock PHC /dev/ptp_hyperv poll 3 dpoll -2 offset 0 stratum 2
197
197
makestep 1.0 -1
198
198
` ` `
199
199
0 commit comments