From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JqEPq-0006XT-On
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 17:28:10 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JqEPo-0006Wl-K6
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 17:28:09 -0400
Received: from [199.232.76.173] (port=55694 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JqEPo-0006Wi-FB
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 17:28:08 -0400
Received: from mail2.shareable.org ([80.68.89.115])
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1JqEPo-0004XB-2Q
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 17:28:08 -0400
Received: from jamie by mail2.shareable.org with local (Exim 4.63)
	(envelope-from <jamie@shareable.org>) id 1JqEPj-0007hv-Hn
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 22:28:03 +0100
Date: Sun, 27 Apr 2008 22:28:03 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] [Patch] [kinda-resend] persistent real-time-clock
Message-ID: <20080427212803.GA29507@shareable.org>
References: <20080427154501.GA20547@karma.qumranet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080427154501.GA20547@karma.qumranet.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Dan Kenigsberg wrote:
> These patches will allow doing the same with VM:
> - Before shutting a VM down, use the monitor's info timeoffset to see
>   how much (in seconds) does the rtc differ from the host clock.
> - Store this offset somewhere.
> - Use it next time with -startdate now+offset.

Another useful one would be store the actual time, and use the same
time when starting next time - without including any advance in host's
clock in the interval.

That's useful when running some time-limited software in a VM.  Then
you can only run the VM when you're using the software, and get more
use out of it before the time runs out.

-- Jamie