VMware场景下：将多台VM与指定VM（非ESX）同步时间

Hey there, let's work through this time sync problem together—no need to stress if you're still getting up to speed on VM configs, I'll focus on practical, doable steps given your limited control over the VMs.

First, a quick prerequisite: the target VM you want to sync to needs to be set up to act as a time source. That means it should have its time service running (NTP for Linux, W32Time for Windows) and its firewall should allow incoming UDP port 123 traffic (the standard port for time sync). If you don't manage that target VM, you might need to loop in whoever does to confirm these settings are in place.

For Linux VMs (Jenkins master/slave, test VMs, database) #

Most modern Linux distros use either systemd-timesyncd or ntpd for time sync. Here's what you can try, depending on your permissions:

If you have sudo access #

• Using systemd-timesyncd (common on Ubuntu 18.04+, CentOS 7+):

  1. Edit the timesync config to point to your target VM:

     sudo sed -i 's/^#NTP=/NTP=your-target-vm-ip-or-hostname/' /etc/systemd/timesyncd.conf
     

  2. Restart the service to apply changes:

     sudo systemctl restart systemd-timesyncd
     

  3. Verify the sync is working:

     sudo timedatectl status
     

     Look for "System clock synchronized: yes" and check the "NTP service" line shows it's using your target VM.

• Using ntpd (older distros):

  1. Update the NTP config to replace existing servers with your target VM:

     sudo sed -i 's/^server.*/server your-target-vm-ip-or-hostname iburst/' /etc/ntp.conf
     

  2. Restart the NTP service:

     sudo systemctl restart ntpd
     

  3. Check the sync status:

     ntpq -p
     

     You should see your target VM listed as a peer.

If you don't have sudo access #

You can still run a one-time manual sync (though this won't persist after a reboot):

ntpdate your-target-vm-ip-or-hostname

For permanent sync, you'll need to ask your VM admin to apply the above config changes for you.

For Windows VMs #

Windows uses the W32Time service for time sync. Again, steps depend on your permissions:

If you have admin access #

1. Open Command Prompt as Administrator, then stop the time service:

   net stop w32time
   

2. Configure the VM to sync from your target VM:

   w32tm /config /syncfromflags:manual /manualpeerlist:"your-target-vm-ip-or-hostname"
   

3. Re-register the time service to apply the config:

   w32tm /register
   

4. Start the service back up:

   net start w32time
   

5. Force an immediate sync:

   w32tm /resync /force
   

6. Verify the sync:

   w32tm /query /status
   

   Look for "Source" showing your target VM and "Leap Indicator" set to "0 (no warning)".

If you don't have admin access #

You can manually adjust the time via the system clock settings, but this won't stay synced long-term. For permanent sync, reach out to your VM admin to set up the W32Time config for you—they can also use Group Policy to push this setting to multiple Windows VMs at once if needed.

Quick Note for Jenkins Nodes #

Since Jenkins relies heavily on accurate time for build logs, scheduled jobs, and pipeline timing, make sure to double-check the time in Jenkins after syncing: go to Manage Jenkins > System Information and look for the "System Time" field to confirm it matches your target VM.

内容的提问来源于stack exchange，提问作者Adam Cohen