qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
	Vinzenz Feenstra <vfeenstr@redhat.com>
Subject: Re: [Qemu-devel] [PULL 8/8] qga: Add `guest-get-timezone` command
Date: Wed, 26 Apr 2017 12:02:02 +0100	[thread overview]
Message-ID: <20170426110202.GF18933@redhat.com> (raw)
In-Reply-To: <1493161481-29595-9-git-send-email-mdroth@linux.vnet.ibm.com>

On Tue, Apr 25, 2017 at 06:04:41PM -0500, Michael Roth wrote:
> From: Vinzenz Feenstra <vfeenstr@redhat.com>
> 
> Adds a new command `guest-get-timezone` reporting the currently
> configured timezone on the system. The information on what timezone is
> currently is configured is useful in case of Windows VMs where the
> offset of the hardware clock is required to have the same offset. This
> can be used for management systems like `oVirt` to detect the timezone
> difference and warn administrators of the misconfiguration.

> +GuestTimezone *qmp_guest_get_timezone(Error **errp)
> +{

> +    name = g_time_zone_get_abbreviation(tz, intv);

[snip]

> +##
> +# @GuestTimezone:
> +#
> +# @zone:    Timezone name

This isn't clearly documented in glib, but it looks like the time zone
names are *different* when glib is run on POSIX vs Win32 platforms.

Do we really want to expose something in QAPI that is going to have
different semantics depending on the guest OS the agent runs in ?

> +# @offset:  Offset to UTC in seconds, negative numbers for time zones west of
> +#           GMT, positive numbers for east
> +#
> +# Since: 2.10
> +##
> +{ 'struct': 'GuestTimezone',
> +  'data':   { '*zone': 'str', 'offset': 'int' } }

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-04-26 11:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 23:04 [Qemu-devel] [PULL 0/8] qemu-ga patch queue Michael Roth
2017-04-25 23:04 ` [Qemu-devel] [PULL 1/8] qemu-ga: Make QGA VSS provider service run only when needed Michael Roth
2017-04-25 23:04 ` [Qemu-devel] [PULL 2/8] qga-win: Enable 'can-offline' field in 'guest-get-vcpus' reply Michael Roth
2017-04-25 23:04 ` [Qemu-devel] [PULL 3/8] qga-win: Fix a bug where qemu-ga service is stuck during stop operation Michael Roth
2017-04-25 23:04 ` [Qemu-devel] [PULL 4/8] qga-win: Fix Event Viewer errors caused by qemu-ga Michael Roth
2017-04-25 23:04 ` [Qemu-devel] [PULL 5/8] qga: Add 'guest-get-host-name' command Michael Roth
2017-04-25 23:04 ` [Qemu-devel] [PULL 6/8] qga: improve fsfreeze documentations Michael Roth
2017-04-25 23:04 ` [Qemu-devel] [PULL 7/8] qga: Add 'guest-get-users' command Michael Roth
2017-04-25 23:04 ` [Qemu-devel] [PULL 8/8] qga: Add `guest-get-timezone` command Michael Roth
2017-04-26 11:02   ` Daniel P. Berrange [this message]
2017-04-26 13:08     ` Eric Blake
2017-04-26 13:10       ` Daniel P. Berrange
2017-04-26 10:51 ` [Qemu-devel] [PULL 0/8] qemu-ga patch queue Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170426110202.GF18933@redhat.com \
    --to=berrange@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vfeenstr@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).