Re: [libvirt] [PATCH 6/6] Expand docs about clock modes
According to Daniel P. Berrange on 2/18/2010 10:54 AM: > * formatdomain.html.in: Document new clock options > --- > + > + The guest clock will have an arbitrary offset applied > + relative to UTC. The delta relative to UTC is specified > + in seconds, using the adjustment attribute. > + The guest is free to adjust the RTC over time an expect s/an/and/ > + that it will be honoured at next reboot. This is in Regarding "honoured": Is there a policy on American vs. British English in the documentation? -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 6/6] Expand docs about clock modes
On Thu, Feb 18, 2010 at 05:54:32PM +, Daniel P. Berrange wrote: > * formatdomain.html.in: Document new clock options > --- > docs/formatdomain.html.in | 38 +++--- > 1 files changed, 35 insertions(+), 3 deletions(-) > > diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in > index 083a80a..55038e2 100644 > --- a/docs/formatdomain.html.in > +++ b/docs/formatdomain.html.in > @@ -393,9 +393,41 @@ > > >clock > - The offset attribute takes either "utc" or > -"localtime" to specify how the guest clock is initialized > -in relation to the host OS. > + > + The offset attribute takes three possible > + values, allowing fine grained control over how the guest > + clock is synchronized to the host. NB, not all hypervisors > + support all modes. > + > + utc > + > + The guest clock will always be synchronized to UTC when > + booted > + localtime > + > + The guest clock will be synchronized to the host's configured > + timezone when booted, if any. > + > + timezone > + > + The guest clock will be synchronized to the requested timezone > + using the timezone attribute. > + > + variable > + > + The guest clock will have an arbitrary offset applied > + relative to UTC. The delta relative to UTC is specified > + in seconds, using the adjustment attribute. > + The guest is free to adjust the RTC over time an expect > + that it will be honoured at next reboot. This is in > + contrast to 'utc' mode, where the RTC adjustments are > + lost at each reboot. > + > + > + > + NB, at time of writing, only QEMU supports the variable > + clock mode, or custom timezones. > + > > > ACK, too, ACK for the serie a a whole, just a few checks and improvement possible. Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ dan...@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/ -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] [PATCH 6/6] Expand docs about clock modes
* formatdomain.html.in: Document new clock options --- docs/formatdomain.html.in | 38 +++--- 1 files changed, 35 insertions(+), 3 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 083a80a..55038e2 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -393,9 +393,41 @@ clock - The offset attribute takes either "utc" or -"localtime" to specify how the guest clock is initialized -in relation to the host OS. + + The offset attribute takes three possible + values, allowing fine grained control over how the guest + clock is synchronized to the host. NB, not all hypervisors + support all modes. + + utc + + The guest clock will always be synchronized to UTC when + booted + localtime + + The guest clock will be synchronized to the host's configured + timezone when booted, if any. + + timezone + + The guest clock will be synchronized to the requested timezone + using the timezone attribute. + + variable + + The guest clock will have an arbitrary offset applied + relative to UTC. The delta relative to UTC is specified + in seconds, using the adjustment attribute. + The guest is free to adjust the RTC over time an expect + that it will be honoured at next reboot. This is in + contrast to 'utc' mode, where the RTC adjustments are + lost at each reboot. + + + + NB, at time of writing, only QEMU supports the variable + clock mode, or custom timezones. + -- 1.6.6 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] [PATCH 6/6] Expand docs about clock modes
* formatdomain.html.in: Document new clock options --- docs/formatdomain.html.in | 34 +++--- 1 files changed, 31 insertions(+), 3 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index ce49f7d..e47a6b7 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -393,9 +393,37 @@ clock - The offset attribute takes either "utc" or -"localtime" to specify how the guest clock is initialized -in relation to the host OS. + + The offset attribute takes three possible + values, allowing fine grained control over how the guest + clock is synchronized to the host. NB, not all hypervisors + support all modes. + + utc + + The guest clock will always be synchronized to UTC when + booted + localtime + + The guest clock will be synchronized to the host's configured + timezone when booted. It is possible to override the timezone + by using the timezone attribute. + + variable + + The guest clock will have an arbitrary offset applied + relative to UTC. The delta relative to UTC is specified + in seconds, using the adjustment attribute. + The guest is free to adjust the RTC over time an expect + that it will be honoured at next reboot. This is in + contrast to 'utc' mode, where the RTC adjustments are + lost at each reboot. + + + + NB, at time of writing, only QEMU supports the variable + clock mode, or custom timezones. + -- 1.6.6 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
