XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Windows Time Sync

    Scheduled Pinned Locked Moved Compute
    3 Posts 3 Posters 1.5k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      gofm
      last edited by gofm

      We have 2019 servers on XCP 7.6. They are running about 2 minutes behind what the XCP host is showing. XCP is syncing with NTP and is correct. When I check what server windows is using to sync, it says LOCAL CMOS. I have the Xen Agent Running. What can I do to correct this?

      1 Reply Last reply Reply Quote 0
      • ForzaF Offline
        Forza
        last edited by

        @gofm said in Windows Time Sync:

        We have 2019 servers on XCP 7.6. They are running about 2 minutes behind what the XCP host is showing. XCP is syncing with NTP and is correct. When I check what server windows is using to sync, it says LOCAL CMOS. I have the Xen Agent Running. What can I do to correct this?

        I usually use NTP time source on the VMs too. We use a dedicated NTP server that all clients sync too.

        https://support.microsoft.com/en-us/help/816042/how-to-configure-an-authoritative-time-server-in-windows-server

        1 Reply Last reply Reply Quote 0
        • N Offline
          nackstein
          last edited by

          @gofm not sure on windows but on linux the walltime is written in UTC to the CMOS when you shutdown or when you explicitly call hwclock command. the time written in the virtualized CMOS should contain an offset to the host clock so when the VM start it read the host time plus the offset. I suppose that if you disable the time sync in windows, set the time and reboot you will come up with a correct clock.
          I have no link to point you at, this is just a sum of things I remember but may be dated and/or wrong still if you can reboot your Windows VM could be worth testing.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post