On Tue, Sep 13, Alex Ng (LIS) wrote:
> > On Thu, Sep 08, k...@exchange.microsoft.com wrote:
> > Perhaps a better approach would be to list the known existing hosts and use
> > the new protocol for upcoming, unknown hosts via 'default:'.
> This is a good idea. I will create another patch that addre
> On Thu, Sep 08, k...@exchange.microsoft.com wrote:
>
> > - default:
> > + case(VERSION_WIN10):
> > util_fw_version = UTIL_FW_VERSION;
> > sd_srv_version = SD_VERSION;
> > ts_srv_version = TS_VERSION;
> > hb_srv_version = HB_VERSION;
> > +
On Thu, Sep 08, k...@exchange.microsoft.com wrote:
> - default:
> + case(VERSION_WIN10):
> util_fw_version = UTIL_FW_VERSION;
> sd_srv_version = SD_VERSION;
> ts_srv_version = TS_VERSION;
> hb_srv_version = HB_VERSION;
> +
From: Alex Ng
This enables support for more accurate TimeSync v4 samples when hosted
under Windows Server 2016 and newer hosts.
The new time samples include a "vmreferencetime" field that represents
the guest's TSC value when the host generated its time sample. This value
lets the guest calculat
