mirror of
https://github.com/linuxkit/linuxkit.git
synced 2025-07-19 01:06:27 +00:00
76b519705b
* Update linuxkit/alpine Signed-off-by: Avi Deitcher <avi@deitcher.net> * tools/alpine: Update to latest Signed-off-by: Avi Deitcher <avi@deitcher.net> * tools: Update to the latest linuxkit/alpine Signed-off-by: Avi Deitcher <avi@deitcher.net> * Update use of tools to latest Signed-off-by: Avi Deitcher <avi@deitcher.net> * tests: Update packages to the latest linuxkit/alpine Signed-off-by: Avi Deitcher <avi@deitcher.net> * Update use of test packages to latest Signed-off-by: Avi Deitcher <avi@deitcher.net> * pkgs: Update packages to the latest linuxkit/alpine Signed-off-by: Avi Deitcher <avi@deitcher.net> * Update package tags Signed-off-by: Avi Deitcher <avi@deitcher.net> --------- Signed-off-by: Avi Deitcher <avi@deitcher.net> |
||
|---|---|---|
| .. | ||
| vendor | ||
| build.yml | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
| README.md | ||
host-timesync-daemon
Some hypervisors (e.g. hyperkit / xhyve) don't provide a good way to keep the VM's clock in sync with the Host's clock. NTP will usually keep the clocks together, but after the host or VM is suspended and resumed the clocks can be suddenly too far apart for NTP to work properly.
This simple daemon listens on an AF_VSOCK port. When a connection is received, the daemon
- reads the (hypervisor's virtual) hardware clock via
RTC_RD_TIMEon/dev/rtc0 - calls
settimeofdayto set the time in the VM - closes the connection
Note the hardware clock has only second granularity so you will still need NTP (or some other process) to keep the clocks closely synchronised.
To use this, simply connect to the AF_VSOCK port when you want the clock
to be resynchronised. If you want to wait for completion then read from
the socket -- EOF means the resychronisation is complete.