Created attachment 1093726 [details]
screenshot

Description of problem:

Actual timezone in the guest differs from the configuration tooltip [!] / Rename 'Time Zone' in VM -> System -> General dialog to 'RTC time'.

The title ('Time Zone', location described above) is not a timezone but the time which will be passed to qemu-kvm.

* qemu-kvm option for RHEL based VM

~~~
# ps aux | grep 'qemu-kvm.*jb-test' | grep -oE '\-rtc base[^ ]*'
-rtc base=2015-11-13T15:51:34,driftfix=slew
~~~

* info from GA

~~~
        guestTimezone = {'zone': 'Europe/Prague', 'offset': 60}
~~~

For the above VM the "Time Zone" (RTC) is:

'(GMT+00:00) GMT Standard Time'

Inside guest OS (RHEL) I have timezone set to Europe/Prague but hwclock is GMT.

The confusion between RTC and timezone causes odd tooltip (screenshot) informing that there's timezone difference between configuration in engine (db) and guest OS.

Usually UNIX/Linux OS have hwclock set to UTC and then userland uses TZ to define timezone. There's nothing wrong to have hwclock and TZ differ.

This issue is related to Windows only which used (now there's registry option) to expect hwclock is equal timezone of OS, thus it is called localtime.

Thus:

- this check is odd for non-Windows VM
- title of option in UI should not be 'Time Zone'

Version-Release number of selected component (if applicable):
rhevm-backend-3.6.0.3-0.1.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. install rhel 6 vm with guest agent
2. check admin portal if there is timezone tooltip (see screenshot) info
3.

Actual results:
- useless warning about hwclock/guest os TZ difference for Linux VMs
- confusing option name ('Time Zone') in VM configuration dialog

Expected results:
- no warning about difference between 'rtc base' time set for Linux VM when started and guest OS TZ
- (if you want to compare anything for Linux VMs then it should be rtc base for qemu-kvm + uptime vs. hwclock inside guest OS)
- more clear option name instead of 'Time Zone'

Additional info:

‘-rtc [base=utc|localtime|date][,clock=host|vm][,driftfix=none|slew]’

    Specify ‘base’ as utc or localtime to let the RTC start at the current UTC or local time, respectively. localtime is required for correct date in MS-DOS or Windows. To start at a specific point in time, provide date in the format 2006-06-17T16:01:21 or 2006-06-17. The default base is UTC.

    By default the RTC is driven by the host system time. This allows to use the RTC as accurate reference clock inside the guest, specifically if the host time is smoothly following an accurate external reference clock, e.g. via NTP. If you want to isolate the guest time from the host, even prevent it from progressing during suspension, you can set ‘clock’ to vm instead.

    Enable ‘driftfix’ (i386 targets only) if you experience time drift problems, specifically with Windows’ ACPI HAL. This option will try to figure out how many timer interrupts were not processed by the Windows guest and will re-inject them.