On Tue, Oct 14, 2014 at 03:14:21PM +0100, Mike Surcouf wrote: > Even with networking I think there are other senarios where this would > be useful such as no access to an NTP server due to firewall rules or > no internal NTP or simply an admin without much knowledge of NTP. Perhaps, but ... > HyperV host very likely has good time from AD and it would be good if > the Linux VM just synced its time from the host after a vanilla > install (just like windows VMs). Just cause windows does it, doesn't make it a good idea. > That would require no configuration and probably save a ton of support traffic. > However this patch requires a module parameter which really negates > the zero configuration argument. > Also please don't make this the default until the timesync component > is more comprehensive and provides a stable time of similar quality to > NTP. We really don't want to go there. > VMware has put a lot of effort into host -> guest timesync so I think > there is a case for some form of host based time sync on HyperV. Again, that is fine for VMware, but it might not be the best way. IMHO, you should let the guest steer its own clock. That gives the end user the most flexibility. Just provide the offset information, and let a dedicated service (like ntpd or linuxptp's phc2sys) do the rest. Thanks, Richard _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
