https://bugzilla.novell.com/show_bug.cgi?id=773323
https://bugzilla.novell.com/show_bug.cgi?id=773323#c15
Dr. Werner Fink
Virtual Hardware clock configuration When configuring the Linux guest operating system, if you are given a choice between keeping the “hardware” clock (that is, the virtual CMOS time of day clock) in UTC or local time, choose UTC. This avoids any confusion when your local time changes between standard and daylight saving time (in England, "summer time").
For additional information, see <Timekeeping in VMware Virtual Machines.>
and AFAICS from the link http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf below <Timekeeping in VMware Virtual Machines.>
Specifically, the CMOS TOD clock shows UTC as kept by the host operating system software, plus an offset. The offset from UTC is stored in the virtual machine’s nvram file along with the rest of the contents of the virtual machine’s CMOS nonvolatile memory. The offset is needed because many guest operating systems require the CMOS TOD clock to show the time in the current local time zone, not in UTC. When a new virtual machine is created (or the nvram file of an existing virtual machine is deleted) and it is powered on, the offset is initialized, by default, to the difference of the host operating system’s local time zone from UTC. If software running in the virtual machine writes a new time to the CMOS TOD clock, the offset is updated.
therefore I've the question: Do you have configiured you VMWare setup to assume UTC in the CMOS clock of your host system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.