<p dir="ltr">Marcus, </p>
<p dir="ltr">Are all your VMs Windows? Because I have a mix and only Windows VMs are affected. Seems like changing utc_diff should only be done for Windows VMs (Linux happy to work with a hardware clock of GMT).</p>
<p dir="ltr">-Bob</p>
<div class="gmail_quote">On Feb 7, 2014 9:54 AM, "Markus Stockhausen" <<a href="mailto:stockhausen@collogia.de">stockhausen@collogia.de</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> Von: Markus Stockhausen<br>
> Gesendet: Freitag, 7. Februar 2014 14:46<br>
> An: Dan Kenigsberg; <a href="mailto:fromani@redhat.com">fromani@redhat.com</a><br>
> Cc: Bob; Martin Polednik; ovirt-users<br>
> Betreff: AW: [Users] Timezone Hypervisor/VM<br>
><br>
> ><br>
> > A detailed BZ report is worth its weight in gold ;-)<br>
> ><br>
> > Dan.<br>
><br>
> Opened BZ 1062615 for that.<br>
><br>
> Markus<br>
<br>
Hi Dan,<br>
<br>
just saw the bug update with target 3.4.1. Could you<br>
reproduce the bug and do you have some advice how to<br>
handle that setting until then? And what should I expect<br>
when daylight saving takes place in march?<br>
<br>
>From my understanding I would:<br>
<br>
- pin all VMs to utc_diff=3600 (GMT+1) now<br>
- pin all VMs to utc_diff=7200 (GMT+2) after change of summertime<br>
<br>
Markus<br>
<br>
</blockquote></div>