From: Peter Lieven <pl@kamp.de>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Occasional clockjump in Win2012 after Live Migration
Date: Fri, 13 Dec 2013 12:50:05 +0100 [thread overview]
Message-ID: <52AAF46D.7090402@kamp.de> (raw)
In-Reply-To: <1386929443.27116.2.camel@localhost>
Am 13.12.2013 11:10, schrieb Vadim Rozenfeld:
> On Fri, 2013-12-13 at 09:27 +0100, Peter Lieven wrote:
>> Am 13.12.2013 05:12, schrieb Vadim Rozenfeld:
>>> Does your VM belong to domain or workgroup?
>> We had 2 vServers where this happened. One was a Domain Controller and the second was an independent Workgroup Server.
>>
>> Do you have evidence how the DateTime Clock is driven in Windows 2012?
> Should be CMOS periodic timer.
you mean the RTC?
Ok, so if there is a huge clock jump this one must have got messed up?
Peter
next prev parent reply other threads:[~2013-12-13 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 16:03 [Qemu-devel] Occasional clockjump in Win2012 after Live Migration Peter Lieven
2013-12-13 4:12 ` Vadim Rozenfeld
2013-12-13 8:27 ` Peter Lieven
2013-12-13 10:10 ` Vadim Rozenfeld
2013-12-13 11:50 ` Peter Lieven [this message]
2013-12-13 12:53 ` Vadim Rozenfeld
2013-12-13 12:55 ` Peter Lieven
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=52AAF46D.7090402@kamp.de \
--to=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=vrozenfe@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).