summaryrefslogtreecommitdiff
path: root/bt-vhci.c
diff options
context:
space:
mode:
authorMichal Privoznik <mprivozn@redhat.com>2014-01-31 11:29:51 +0100
committerMichael Roth <mdroth@linux.vnet.ibm.com>2014-02-23 13:11:56 -0600
commit2c958923bc09b1faf2505a988b4b1c458580e9ac (patch)
tree5f93ba27390077b8eccf71af5465ef69371c9aa2 /bt-vhci.c
parentd9e1f574cb6eac0a3a2f97b67d2e7a3ad9c1dc95 (diff)
downloadqemu-2c958923bc09b1faf2505a988b4b1c458580e9ac.tar.gz
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 'bt-vhci.c')
0 files changed, 0 insertions, 0 deletions