I'm running kvm with the -rtc option to try and test a bug related to the start of daylight savings time. Anyway when the VM boots up it gets the acutal time rather than the hwclock time: root@stretch:/etc# hwclock 2018-10-05 10:39:30.993531+1000 root@stretch:/etc# date Sun 14 Oct 13:17:23 AEDT 2018 root@stretch:/etc# cat /etc/systemd/timesyncd.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See timesyncd.conf(5) for details. [Time] #NTP= #FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org root@stretch:/etc# dpkg -l "*ntp*"|grep ^ii Any ideas for where this might be set? It's a fairly standard Debian/Stretch system with systemd. When I boot with "init=/bin/bash" it has the correct time, so something after going multi-user sets the time via NTP (presumably). -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On Sun, Oct 14, 2018 at 01:21:05PM +1100, Russell Coker via luv-main wrote:
Anyway when the VM boots up it gets the acutal time rather than the hwclock time: ... Any ideas for where this might be set? It's a fairly standard Debian/Stretch system with systemd. When I boot with "init=/bin/bash" it has the correct time, so something after going multi-user sets the time via NTP (presumably).
does output from timedatectl help you? it's what I use first these days if time goes awry. cheers, robin
On Sunday, 14 October 2018 1:29:41 PM AEDT Robin Humble via luv-main wrote:
On Sun, Oct 14, 2018 at 01:21:05PM +1100, Russell Coker via luv-main wrote:
Anyway when the VM boots up it gets the acutal time rather than the hwclock time: ... Any ideas for where this might be set? It's a fairly standard Debian/Stretch system with systemd. When I boot with "init=/bin/bash" it has the correct time, so something after going multi-user sets the time via NTP (presumably). does output from timedatectl help you? it's what I use first these days if time goes awry.
root@stretch:/etc# timedatectl Failed to create bus connection: No such file or directory There's something broken in that regard. But as no NTP servers are set I would hope that it doesn't just go and do stuff. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
participants (2)
-
Robin Humble -
Russell Coker