DRS migrated Guest changes local time

[gorto]

Has anyone seen this behaviour/feature?

VI3 , version 3.0.2 DRS cluster set to auto migrate (aggressive).

VC (auto-) migrates Guest1 from HostA to HostB

Guest1 has VMTools installed but does not get its time from ESX host (uses NTP)

On migration Guest1 uses new HostB time with event recorded in Guest1 Event Log

Anyone?

[AWo]

Here are some parameters which prevent the VMware Tools from synchronizing the time:

tools.syncTime = "FALSE"

time.synchronize.continue = "FALSE"

time.synchronize.restore = "FALSE"

time.synchronize.resume.disk = "FALSE"

time.synchronize.shrink = "FALSE"

time.synchronize.tools.startup = "0"

or

time.synchronize.tools.startup = "FALSE"

where

• tools.syncTime If set to TRUE, the clock syncs periodically.

• time.synchronize.continue If set to TRUE, the clock syncs after taking a snapshot.

• time.synchronize.restore If set to TRUE, the clock syncs after reverting to a snapshot.

• time.synchronize.resume.disk If set to TRUE, the clock syncs after resuming from suspend and after migrating to a new host using the VMware VMotion feature.

• time.synchronize.shrink If set to TRUE, the clock syncs after defragmenting a virtual disk.

• time.synchronize.tools.startup If set to TRUE, the clock syncs when the tools daemon starts up,

• normally while the guest is booting.

Message was edited by: AWo

[aleph0]

Why you do not sync your machines with ESX hosts using vmtools checkbox? if ESX are in sync with an NTP server why not sychronizing?

what kind of VMs got the problem (DC, file server) Linux or windows?

\aleph0

____________________________

(in italian)

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[gorto]

Guest1 is a Windows 2000 Server Domain Controller configured for NTP and hence does not need local VMTools sync to host

On automated DRS migration, though not set to VMTools time sync its clock moved +20hours ahead since the two hosts where 20 apart (don't ask)

Being a DC - this had consequences ..............

[gorto]

Whoa ! - does this imply a time-sync occurs on migration irrespective of setting of VMWare Tools Properties, Options tab, Miscellaneous Options, Time Synchronisation tick-box setting?

[AWo · Accepted solution]

Yes, this also the case if you want to set the time to a different value. You set in in the BIOS, the server boots, the tools synchronize (once) and when shutting down the server the BIOS is updated with the (unwanted) host time again. You need this switches to completely shut the synchronization off.

[aleph0]

You can try disabling Windows sync with NTP and using vmtools sync with ESX hosts.

The important thing is that you do not do both at the same time.

cheers

[AWo]

You can try disabling Windows sync with NTP and using vmtools sync with ESX hosts.

The important thing is that you do not do both at the same time.

cheers

Whereas disabling sync with (S)NTP doesn't mean disabling W32Time (on a DC) as the DC (especially the FSMO PDC Emulator) is a time source for other hosts in the domain. Set the timesync option to "NoSync", leave W32Time running and use the VMware Tools time synchronization. You may also have to mark the DC as a reliable time source. On member servers which use VMware Tools to synchronize the time, W32Time can be disabled.

Of course, your ESX host needs to be synchronized with an NTP source.

[aleph0]

Hope this help

cheers

\aleph0

____________________________

(in italian)

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[gorto]

Never realised time was sooo complex - many thanks Guys

[AWo]

Some more: http://www.vmware.com/pdf/vmware_timekeeping.pdf

As far as I have seen this is a new version. There is an older one which covers the things more in detail. If you want to have this one let me know, I can send it to you.

[aleph0]

did you resolve your issue?

\aleph0

____________________________

(in italian)

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[gorto]

You guys answered my question, yes - many thanks

Resolving the issue revolves around getting NTP, System time and hwclock in sync in line with the correct timezone file.