note: this is actually about applying defaults set in engine-config. By default new VMs will be created with GMT(UTC) initial timezone setting which is what most people want for Linux OSes
ok, rhevm-3.2.1-0.31.el6ev.noarch. engine=> select * from vdc_options where option_name like '%TimeZone%'; option_id | option_name | option_value | version -----------+------------------------+-------------------+--------- 372 | DefaultWindowsTimeZone | GMT Standard Time | general 373 | DefaultGeneralTimeZone | Etc/GMT | general (2 rows) * related issues: 1) engine-config part is not done yet, but this can be solved by adding option_name(s) into /etc/ovirt-engine/engine-config/engine-config.properties, restarting ovirt-engine. then one can use rhevm-config to define its own TZ. (BZ974982) 2) if one would put "incorrect" TZ, the value in UI dialog does not show original default fallback but it does show - default: null (BZ974985) # rhevm-config -g DefaultWindowsTimeZone DefaultWindowsTimeZone: Europe/Prague version: general this shows mentioned - default:null
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1048.html