From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:37619)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1TBssp-0003fG-TD
	for qemu-devel@nongnu.org; Wed, 12 Sep 2012 15:46:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1TBssh-00067c-Ge
	for qemu-devel@nongnu.org; Wed, 12 Sep 2012 15:45:59 -0400
Received: from v220110690675601.yourvserver.net ([78.47.199.172]:35302)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1TBssh-00067T-AZ
	for qemu-devel@nongnu.org; Wed, 12 Sep 2012 15:45:51 -0400
Message-ID: <5050E66D.4090900@weilnetz.de>
Date: Wed, 12 Sep 2012 21:45:49 +0200
From: Stefan Weil <sw@weilnetz.de>
MIME-Version: 1.0
References: <87pq5r5otp.fsf@codemonkey.ws> <5050B7E2.3070803@weilnetz.de>
	<20120912164518.GD25041@redhat.com> <5050C6A0.8050800@weilnetz.de>
	<20120912181312.GE25041@redhat.com>
In-Reply-To: <20120912181312.GE25041@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Rethinking missed tick catchup
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gleb Natapov <gleb@redhat.com>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>, Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>, Avi Kivity <avi@redhat.com>, Anthony Liguori <anthony@codemonkey.ws>, Paolo Bonzini <pbonzini@redhat.com>, Eric Blake <eblake@redhat.com>

Am 12.09.2012 20:13, schrieb Gleb Natapov:
> On Wed, Sep 12, 2012 at 07:30:08PM +0200, Stefan Weil wrote:
>> I also meant host hibernation.
> Than I don't see how guest can handle the situation since it has
> no idea that it was stopped. Qemu has not idea about host hibernation
> either.

The guest can compare its internal timers (which stop
when the host hibernates) with external time references
(NTP, hw clock or any other clock reference).