From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JqACn-0007Kr-2A
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 12:58:25 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JqACl-0007Kb-GK
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 12:58:24 -0400
Received: from [199.232.76.173] (port=34153 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JqACl-0007KY-Ak
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 12:58:23 -0400
Received: from wr-out-0506.google.com ([64.233.184.227])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1JqACk-0003d3-Vn
	for qemu-devel@nongnu.org; Sun, 27 Apr 2008 12:58:23 -0400
Received: by wr-out-0506.google.com with SMTP id c49so2478906wra.19
	for <qemu-devel@nongnu.org>; Sun, 27 Apr 2008 09:58:20 -0700 (PDT)
Message-ID: <4814B0A9.7090601@codemonkey.ws>
Date: Sun, 27 Apr 2008 11:58:17 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [Patch] [kinda-resend] persistent real-time-clock
References: <20080427154501.GA20547@karma.qumranet.com>
In-Reply-To: <20080427154501.GA20547@karma.qumranet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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:
> Real PC lets its user set the real-time-clock and store it on CMOS,
> which advances the clock even when the PC is offline.
>
> 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.
>
> Please tell me what do you think of it.
>   

I think a more general mechanism that stored nvram in a file would be 
interesting.  Something like like -nvram file.ram.  This also allows a 
guest to determine it's initial boot device and for that setting to persist.

Regards,

Anthony Liguori

> Dan.
>