Hyper-V event log: Logged Time and SystemTime.

in event detail tab section xml view timecreated attribute systemtime value different logged time value in general tab value.
our application reading xml view value. please explain 1 correct read? explain detail 2 different time.

hi prashant

by default, time service has “phase adjustment” process slows down or speeds system clock rate match reliable time source. tsc counter on physical cpu clocked system quartz (if still this). “normal” drift of kind of component not important, , may related external factors temperature of room. time service can deal kind of slow drift.

but default configuration not seem fit time source drifts , rather unpredictable. need shorten process of phase adjustment.

fixing drift rather simple, time service needs correct clock rate more frequently, cope load of virtual machines slow down clock of host.

a few parameters need adjusted in registry clock stay synchronized :

• set specialinterval value 0x1 force use of specialpollinterval.
• set specialpollinterval 10, force source ntp polled every 10 seconds.
• set maxallowedphaseoffset 1, force maximum drift 1 second before clock set directly, if adjusting clock rate failed.

using these parameters not mean clock stay stable, @ least correct quickly.

note:

best practices microsoft recommend never use virtualization services (regardless of hypervisor provider) time source domain-joined computer; instead, should depend on typical active directory synchronization methods.

 

---

if post helpful, please mark such
________________________________________
alessandro cardoso
mvp | microsoft heroes | mct
blog: http://virtualisationandmanagement.wordpress.com
http://virtualizacaoegerenciamento.wordpress.com

Windows Server  >  Hyper-V