I thought I have tested everything "obvious" - also uninstalled latest Windows 10 CU - but the problem persisted, also reverted tools to the previous version, but no change.. I assume the time on the VM is not being synchronized independently, as otherwise it'll just take on the time of the host in which it's running. The other option is to of course set it up to independently sync to preferably the same NTP source as the XenServer host. In any case, that behavior you experienced seems odd.
I've not seen this with any Windows or Linux VMs. The XenServers are all configured for the same NTP servers, the time is correct on all of them, yet only the guests boot to wildly off times more than 2 hours in some instances. And as such, all group policy processing fails and the box is virtually useless. Your HostTime registry key is the only thing that seems to work in my limited testing.
I vaguely remember some hardware that has issues, but a server on the domain should follow the. A local time source or syncing out. No unfortunately not, I haven't found the root cause for this as of now.
Very strange indeed. In the mean time I have deployed the registry "fix" on all my VMs - and I haven't had a single problem with time sync since then Usually I also want to find the root cause - but there are limits on how much time you put on an issue - especially if you have a pretty simple workaround Our XA admin was ready to bang her head through a wall over this issue, because it's been killing us. Before I stumbled across your post, she had written a script to force a lot of stuff at startup just to get through testing, but since making this change everything has been good.
I'm going to just roll with it, as well, but I do believe that she submitted a ticket with Citrix last week. If that goes anywhere, I'll absolutely post the findings here. Same problem.
I discovered it after updating XenTools to 7. XenServer 7. Removing the parameter value of the HostTime in the registry or set to "Local", or disable service solved it problem. Xen is a platform that allows multiple operating systems running in virtual systems on one physical box of hardware. At a customer site before deploying the product in a production environment he may want to test the product or component. To test or demo the product, multiple systems with different servers and clients might be required which might be cumbersome to have.
There might be various scenarios or deployments where time synchronization across the servers and setups is needed. This document helps to resolve the time synchronization issues to have successful setups on guest virtual systems.
In one of the cases, while attaching a eDirectory server to an exiting Tree, time synchronization plays a major role. The eDirectory configuration fails if the servers are not in timesync which is a major failure for the component. This article describes how time synchronization issues can be resolved.
Restarting NTP service frequently to get the time regularly will solve the problem, for which crontab can be used. Do the following:. A crontab file has five fields for specifying day , date and time. This contab entry in the above command will restart NTP service for every minute by which the system get the time from NTP server for every minute. Website optional. Save my name, email, and website in this browser for the next time I comment. Currently you have JavaScript disabled.
In order to post comments, please make sure JavaScript and Cookies are enabled, and reload the page. Click here for instructions on how to enable JavaScript in your browser. Skip to content. Skip to Archives. Skip to Search. From Microsoft Technet regarding time Windows components and services depend on time synchronization.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.
0コメント