I'm running a Linux server with the time set via an NTP server -- It's fine - BIOS hardware clock is set OK to correct time too.
Now when I boot up Windows VM's or run my Music / radio streamer system the time settings (on the VM's and the music server client) are always +1 hr out ???. Doesn't seem to matter which Linux distro I use.
I've now set the Windows VM's to get the time via the Internet - shouldn't have to do that - but my music server still records the time as + 1 hr. The client gets the time directly from the music server (it's a hardware client so other than display in 12 / 24 hr format there's no "adjust time" settings on it).
If I run the music server on native windows (tested with a Windows to Go installation) the time is 100% correct.
I can't remember this problem before the latest crop of Linux releases. !!
A server needs the CORRECT time or all sorts of discrepancies in the logs can occur.
Any Windows vm running on that host has time +1 hour
All Windows vms are set to get time from the internet
If the above is correct then the most logical reason would be that host is in normal time, virtual machines although same time zone but in daylight saving time (+1).
If I Don't set the VM's to get time from the Internet they are always + 1hr - The host is set via NTP server (seems that it's UTC which is fine)
Where I am we are on standard GMT all year so it's Central European time -2 or BST -1.
The hardware music client gets the time from the music server (Linux). If I run it from a Windows VM (this server works both on Linux and Windows) then it picks up the time from the Windows VM which is + 1hr to what I want it.
So I'm confused as to why WINDOWS should be setting the time +1hr unless it's something to do with "Daylight saving" -- could it be that if I'm using a laptop Windows will adjust the time for daylight saving -- can't seem to find any place to disable that though.
I'm sure it's something with setting for daylight saving -- even on the Linux distros there seems to be no setting to turn that off -- that's the trouble with these "too easy automatic installs".
What I'm trying now is for the Linux Host to set the time via NTP server, then start the music server 30 secs after boot and then bring up the Windows VM's -- could be Windows picked up the time before the NTP server had set it.
What a dogs dinner of a mess for what should be a trivial problem !!!!
Linux server was doing something with it too -- if I was logged on to the internet at boot it would pick up the ISP address of the server and work out if daylight saving operated or not. Since I use several different ISP's at times not all in the same country this caused the problem.