For VMWare, the command vmware-toolbox-cmd timesync status returns 'Disabled'. I can submit a patch for /etc/init.d/cloud-early-config to enable it
On 5/15/13 12:23 PM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> wrote: >I am not sure why it is missing, but I will refer to >Citrix XenServer 6.0 Virtual Machine Installation Guide > >http://s.apache.org/YGn > >And quote >"Time Handling in Linux VMs >By default, the clocks in a Linux VM are synchronized to the clock running >on the control domain, and cannot be >independently changed. This mode is a convenient default, since only the >control domain needs to be running the >NTP service to keep accurate time across all VMs. Upon installation of a >new Linux VM, make sure you change the >time-zone from the default UTC to your local value (see the section called >³Release Notes² for specific distribution >instructions). >To set individual Linux VMs to maintain independent times >1. From a root prompt on the VM, run the command: echo 1 > >/proc/sys/xen/independent_wallclock >2. This can be persisted across reboots by changing the /etc/sysctl.conf >configuration file and adding: ># Set independent wall clock time >xen.independent_wallclock=1 >3. As a third alternative, independent_wallclock=1 may also be passed as a >boot parameter to the VM. >" > > >On 5/15/13 12:09 PM, "Chip Childers" <chip.child...@sungard.com> wrote: > >>On Wed, May 15, 2013 at 12:02:41PM -0700, Chiradeep Vittal wrote: >>> /proc/sys is not a regular filesystem and cannot be added to from the >>> shell. >>> Drivers need to add nodes into this filesystem. >> >>Backing up a bit... >> >>This is the current system VM image that the 4.1 software should be >>using on Xen: >> >>http://download.cloud.com/templates/acton/acton- >>systemvm-02062012.vhd.bz2 >> >>Does this system VM have the correct drives installed to set >>/proc/sys/xen to use the Dom0 time for sync? >> >>If so, then is this a devcloud only issue for Xen? If that's the case, >>then we shouldn't block a release to simply improve things. >> >>We do know that a patch for kvm was needed. >> >>We still don't have any >>answer or comments about the VMware system VM (specifically this >>template: http://download.cloud.com/templates/burbank/burbank- >>systemvm-08012012.ova >> >
