diff options
author | Michal Privoznik <mprivozn@redhat.com> | 2014-01-31 11:29:51 +0100 |
---|---|---|
committer | Michael Roth <mdroth@linux.vnet.ibm.com> | 2014-02-23 13:11:56 -0600 |
commit | 2c958923bc09b1faf2505a988b4b1c458580e9ac (patch) | |
tree | 5f93ba27390077b8eccf71af5465ef69371c9aa2 /qga/qapi-schema.json | |
parent | d9e1f574cb6eac0a3a2f97b67d2e7a3ad9c1dc95 (diff) | |
download | qemu-2c958923bc09b1faf2505a988b4b1c458580e9ac.zip qemu-2c958923bc09b1faf2505a988b4b1c458580e9ac.tar.gz qemu-2c958923bc09b1faf2505a988b4b1c458580e9ac.tar.bz2 |
qga: Don't require 'time' argument in guest-set-time command
As the description to the guest-set-time states, the command is
there to ease time synchronization after resume. If guest was
suspended for longer period of time, its system time can go off
so badly, that even NTP refuses to set it. That's why the command
was invented: to give users chance to set the time (not
necessarily 100% correct). However, there's is no real need for
us to require users to pass an arbitrary time. Especially if we
can read the correct value from RTC (boiling down to reading
host's time). Hence this commit enables logic:
guest-set-time() == guest-set-time($now_from_rtc)
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'qga/qapi-schema.json')
-rw-r--r-- | qga/qapi-schema.json | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/qga/qapi-schema.json b/qga/qapi-schema.json index 245f968..80edca1 100644 --- a/qga/qapi-schema.json +++ b/qga/qapi-schema.json @@ -120,17 +120,18 @@ # This command tries to set guest time to the given value, # then sets the Hardware Clock to the current System Time. # This will make it easier for a guest to resynchronize -# without waiting for NTP. +# without waiting for NTP. If no @time is specified, then +# the time to set is read from RTC. # -# @time: time of nanoseconds, relative to the Epoch of -# 1970-01-01 in UTC. +# @time: #optional time of nanoseconds, relative to the Epoch +# of 1970-01-01 in UTC. # # Returns: Nothing on success. # # Since: 1.5 ## { 'command': 'guest-set-time', - 'data': { 'time': 'int' } } + 'data': { '*time': 'int' } } ## # @GuestAgentCommandInfo: |