qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Virtbie <virtbie@shiftmail.org>
To: qemu-devel@nongnu.org,
	"'KVM-ML (kvm@vger.kernel.org)'" <kvm@vger.kernel.org>
Subject: [Qemu-devel] Clock skew after pausing guests
Date: Thu, 17 Mar 2011 15:24:31 +0100	[thread overview]
Message-ID: <4D82199F.6030703@shiftmail.org> (raw)

Hello all
I am seeing, perhaps unsurprisingly, a skewed system clock after pausing
and then resuming a qemu-kvm guest. The guest continues with its earlier
time.
Since I'd like to use the pause technique for backups, which can take 1
hour, this is significant.

This is with windows guests, and it doesn't seem to recover by itself
just by waiting.

Linux guests instead seem to adjust their clock correctly after the resume.

Is there any way to tell the windows guests to resynchronize its clock
with the host?
I am using virsh / libvirt.

Thank you

             reply	other threads:[~2011-03-17 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 14:24 Virtbie [this message]
2011-03-17 14:34 ` [Qemu-devel] Re: Clock skew after pausing guests Timur Safin

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=4D82199F.6030703@shiftmail.org \
    --to=virtbie@shiftmail.org \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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).