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