https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c1 Jiří Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |werner@suse.com Severity|Normal |Critical --- Comment #1 from Jiří Suchomel 2012-07-30 05:54:33 UTC --- Right, we do not have any specific check for virtual hardware at this place. And I although thought that local time should be the virtual hw defaul, but actually in VirtualBox, I have correct time from start when I use UTC. So maybe there's some difference? Werner, what do you think? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c Jiří Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Severity|Critical |Normal -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c4 --- Comment #4 from Dr. Werner Fink 2012-07-30 14:01:00 UTC --- Then this is a bug of vmware! It should not use the user space clock but the kernels system clock which is in UTC by definition. To see from user space which clock the kernel uses simply use: TZ=UTC date -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c6 --- Comment #6 from Dr. Werner Fink 2012-07-30 14:39:16 UTC --- (In reply to comment #5) Not using a hard reference clock but a dynamic clock is a BUG, regardless of the OS. Universal Time Coordinated is the worls wide reference and e.g. the timezone data base below /usr/share/zoneinfo and the network depends on it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c FeiXiang Zhang changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |werner@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c FeiXiang Zhang changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mseben@gmail.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|On installation of 12.2 on |On installation of 13.1 on |vmware it makes wrong |vmware it makes wrong |recomendation about clock. |recomendation about clock. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c13 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|werner@suse.com |carlos.e.r@opensuse.org --- Comment #13 from Dr. Werner Fink 2013-10-01 12:24:36 UTC --- IMHO vmware has a bug as it does not resprect the system default that is if /etc/adjtime shows UTC in its last line vmware has to use that. @Carlos: Why do you think this is an openSUSE installation BUG? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c15 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |carlos.e.r@opensuse.org --- Comment #15 from Dr. Werner Fink 2013-10-01 13:02:22 UTC --- Hmmm ... please explain how ths is solved e.g. on Debian or RedHat? I'm pretty sure that both uses UTC as default in their setups. IMHO VMWare is third party and we have no maintainer for this. Beside this with google search https://www.google.de/search?q=VMWare+UTC+CMOS&ie=utf-8&oe=utf-8&rls=org.mozilla:en-US:official&client=firefox-a&gws_rd=cr&ei=GcZKUpuqKc6f7Aag54GwBg shows the link http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427 which is VMWare documentation with:

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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c17 --- Comment #17 from Carlos Robinson 2013-10-01 13:34:35 UTC --- (In reply to comment #15)

Hmmm ... please explain how ths is solved e.g. on Debian or RedHat? I'm pretty sure that both uses UTC as default in their setups. IMHO VMWare is third party and we have no maintainer for this.

I have no idea how other distributions handle this. Obviously they are Linux, so the clock will be handled similarly (ie, system clock in UTC), I'm sure SUSE is interested that vmware works well with SUSE distros, either as host or as clients. I know they have agreements.

which is VMWare documentation with:

...

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").

Well, vmplayer works wrong with that setting.

therefore I've the question: Do you have configiured you VMWare setup to assume UTC in the CMOS clock of your host system?

It has the default settings, I don't touch them.

rtc.diffFromUTC = 0 sets the clock to UTC at power on, while setting

No such variable in the entire /etc/vmware tree, or the OpenSUSE 12.3.vmx file. I'll try creating it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c19 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|carlos.e.r@opensuse.org | --- Comment #19 from Carlos Robinson 2013-10-01 14:46:56 UTC --- No such luck :-( I created that variable, set to zero, and booted that virtual machine. The output of date matched the host date, which should not be the case after the change. eleanor3:~ # hwclock --debug hwclock from util-linux 2.21.2 Using /dev interface to clock. Last drift adjustment done at 0 seconds after 1969 Last calibration done at 0 seconds after 1969 Hardware clock is on local time Assuming hardware clock is kept in local time. Waiting for clock tick... ..got clock tick Time read from Hardware Clock: 2013/10/01 14:45:27 Hw clock time : 2013/10/01 14:45:27 = 1380631527 seconds since 1969 2013-10-01T14:45:27 CEST -0.070763 seconds eleanor3:~ # date Tue Oct 1 16:45:28 CEST 2013 eleanor3:~ # It is also interesting that when the local clock changes from summer to winter, the guest has the correct time. If the clock had a fixed time difference (as per rtc.diffFromUTC), the guest clock would not match. Notice that, AFAIK, the guest clock is kept in sync by the guest tools, which probably means that it depends on the host user (not system) time. It is not recommended to run NTP on the guest (so says their documentation). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c21 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|carlos.e.r@opensuse.org | --- Comment #21 from Carlos Robinson 2013-10-01 19:47:30 UTC --- It is ignored :-( It might be taken from the init.d service. Curious... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c23 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|carlos.e.r@opensuse.org | --- Comment #23 from Carlos Robinson 2014-01-08 16:36:30 UTC --- Oops. sorry, I forgot about this. I'm testing with vmware® player, 5.0.2, which is not the latest version (I believe there is a version 6.x). I edited "/etc/init.d/vmware" in the 12.3 host system. At about line 75, I now have: # # Are we running in a VM? # vmwareInVM() { "$BINDIR"/checkvm >/dev/null 2>&1 } #CER - https://bugzilla.novell.com/show_bug.cgi?id=773323#c22 TZ=UTC export TZ I booted a virtual machine from the 13.1 64 iso image. I reach the clock and time screen. With the hardware clock set to UTC ticked, the clock shows "19:18", and without 18:18. None is the correct time for Spain. as displayed by the host: cer@Telcontar:~> date --iso=seconds ; date --universal --iso=seconds 2014-01-08T17:21:02+0100 2014-01-08T16:21:02+0000 <-- UTC So it is not working. I restart vmware service, remove that addition, and repeat test for comparison. With the tick box ticked, the window displays 19:24. Without, it shows 18:24 - ie, the same thing as before editing the service file. There is a new problem in 13.1 install disk, as no combination displays the correct wall time. However, unticking the box and really installing results on the correct time in the running system. Going to a terminal (install live system) also says that UTC is 18:30 (which is wrong, current UTC is 16:30) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c25 --- Comment #25 from Carlos Robinson 2014-01-13 15:39:27 UTC --- When you install the virtual machine, and in YaST I select "local time", YaST pops up a big warning against this action. But this action is the correct one in this case, ie, the one that works. The only thing I'm requesting is that YaST do not tell the user to change to UTC. Only that. Abstain from popping up that (wrong) warning. The point of this report is not whether Vmware does things one way or the other. They do things as they do, and we know that. When YaST detects it is running in a virtual vmware machine (and it does, as it automatically installs the correct guest tools and the appropriate video drivers automatically), it could, should, also raise a flag or whatever you do so that clock source is automatically selected to local time, and the warning disabled. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c27 Jiří Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsuchome@suse.com |lslezak@suse.com Target Milestone|13.1 Beta 1 |13.2 Milestone 0 --- Comment #27 from Jiří Suchomel 2014-01-13 16:02:09 UTC --- (In reply to comment #25)

The only thing I'm requesting is that YaST do not tell the user to change to UTC. Only that. Abstain from popping up that (wrong) warning.

Well, we could probably do that - for vmware. AFAIS, for other vertialization methods (like VirtualBox) the situation is different. Ladislav, could you add the appopriate check to the place where the popup in question is raised? In current code, there's check for !Timezone.windows_partition && hwclock_s == :hwclock_localtime in include/timezone/dialogs.rb, line 904 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=773323 https://bugzilla.novell.com/show_bug.cgi?id=773323#c29 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |snwint@suse.com InfoProvider|snwint@suse.com | --- Comment #29 from Steffen Winterfeldt 2014-01-14 10:09:45 CET --- Yes, it can detect vmware. There is an internal flag hd_data->flags.vmware that gets set when you probe the system type. 'hwinfo --sys' shows it. Not sure if the yast hardware agent read the flag, though. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=773323 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:212:low | -- You are receiving this mail because: You are on the CC list for the bug.