"Actual timezone in guest doesn't match configuration" for Windows VMs since guest agent 4.3
Hi, the oVirt guest agent seems to report DST configuration for the timezone since version 4.3 (of the guest agent). this results in "Actual timezone in guest doesn't match configuration" messages in the UI for windows VMs because the timezone field can't be matched with oVirt configuration anymore (no DST flag). to me this looks like a bug. shall I report it? I know there was a similar thread at the beginning of May, but there was no solution mentioned. Matthias
On 8 Jul 2019, at 16:58, Matthias Leopold <matthias.leopold@meduniwien.ac.at> wrote:
Hi,
the oVirt guest agent seems to report DST configuration for the timezone since version 4.3 (of the guest agent). this results in "Actual timezone in guest doesn't match configuration" messages in the UI for windows VMs because the timezone field can't be matched with oVirt configuration anymore (no DST flag). to me this looks like a bug. shall I report it?
Yes please. With more details if possible:) We started using qemu-ga for these and it’s possible that the report differs in this aspect. Then it needs to be fixed Thanks, michal
I know there was a similar thread at the beginning of May, but there was no solution mentioned.
Matthias _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/F7QBHRUKETL77K...
Am 09.07.19 um 19:27 schrieb Michal Skrivanek:
On 8 Jul 2019, at 16:58, Matthias Leopold <matthias.leopold@meduniwien.ac.at> wrote:
Hi,
the oVirt guest agent seems to report DST configuration for the timezone since version 4.3 (of the guest agent). this results in "Actual timezone in guest doesn't match configuration" messages in the UI for windows VMs because the timezone field can't be matched with oVirt configuration anymore (no DST flag). to me this looks like a bug. shall I report it?
Yes please. With more details if possible:) We started using qemu-ga for these and it’s possible that the report differs in this aspect. Then it needs to be fixed
Thanks, michal
I know there was a similar thread at the beginning of May, but there was no solution mentioned.
Matthias
I live in Vienna. When I configure Windows VM Hardware Clock Time Offset as "Central European Standard Time" the problem goes away. I still don't know what this "W. Europe Standard Time (UTC+01:00)" timezone that Windows uses and reports and that is choosable in oVirt actually is, this causes the error IMHO (since "recently"...). According to Wikipedia there's only "Western European Time" (UTC+00:00) and Vienna has "Central European Time" (UTC+01:00). Timezones and DST are a PITA. Matthias
Am 12.07.19 um 13:26 schrieb Matthias Leopold:
Am 09.07.19 um 19:27 schrieb Michal Skrivanek:
On 8 Jul 2019, at 16:58, Matthias Leopold <matthias.leopold@meduniwien.ac.at> wrote:
Hi,
the oVirt guest agent seems to report DST configuration for the timezone since version 4.3 (of the guest agent). this results in "Actual timezone in guest doesn't match configuration" messages in the UI for windows VMs because the timezone field can't be matched with oVirt configuration anymore (no DST flag). to me this looks like a bug. shall I report it?
Yes please. With more details if possible:) We started using qemu-ga for these and it’s possible that the report differs in this aspect. Then it needs to be fixed
Thanks, michal
I know there was a similar thread at the beginning of May, but there was no solution mentioned.
Matthias
I live in Vienna.
When I configure Windows VM Hardware Clock Time Offset as "Central European Standard Time" the problem goes away. I still don't know what this "W. Europe Standard Time (UTC+01:00)" timezone that Windows uses and reports and that is choosable in oVirt actually is, this causes the error IMHO (since "recently"...).
According to Wikipedia there's only "Western European Time" (UTC+00:00) and Vienna has "Central European Time" (UTC+01:00).
Timezones and DST are a PITA.
I'm sorry, I didn't want to be rude, but I'm a bit desperate with this... Just when I thought I explained it I'm seeing a Windows 10 VM (Hardware Clock Time Offset: CET) that reports "W. Europe Daylight Time (UTC+02:00)" _again_ and the "doesn't match configuration" error is back. I thought I beat the "DST" reporting by setting VM "Hardware Clock Time Offset" correctly because I didn't see any effect of the Windows "Adjust for DST automatically" configuration on the reported timezone. This seemed to be true for Windows Server 2016 and Windows 7... I'm giving up on this for now, I don't control all of the Windows VMs, maybe someone finds the missing part All VMs are using oVirt Guest Tools 4.3-3.el7 (from oVirt 4.3.4) in oVirt engine 4.3.3 thanks Matthias
participants (2)
-
Matthias Leopold -
Michal Skrivanek