Re: [Users] Timezone Hypervisor/VM
On Fri, Feb 07, 2014 at 02:54:13PM +0000, Markus Stockhausen wrote:
> Von: Markus Stockhausen
> Gesendet: Freitag, 7. Februar 2014 14:46
> An: Dan Kenigsberg; fromani(a)redhat.com
> Cc: Bob; Martin Polednik; ovirt-users
> Betreff: AW: [Users] Timezone Hypervisor/VM
>
> >
> > A detailed BZ report is worth its weight in gold ;-)
> >
> > Dan.
>
> Opened BZ 1062615 for that.
>
> Markus
Hi Dan,
just saw the bug update with target 3.4.1. Could you
reproduce the bug and do you have some advice how to
handle that setting until then?
No, I did not reproduce the bug myself. I believe that your report is
true and asked Michal to get it fixed by ovirt-3.4.1 (frankly, let's ask
to fix it earlier!)
I have no intermediate remedy, save for manually editing utc_diff.
And what should I expect
when daylight saving takes place in march?
>From my understanding I would:
- pin all VMs to utc_diff=3600 (GMT+1) now
- pin all VMs to utc_diff=7200 (GMT+2) after change of summertime
Yes, assuming that the local admin of the VM do not want to change their
timezone - in Windows it means an update of the rtc, which is not saved
properly in Engine.
Dan.