From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MveQz-00073g-3e for qemu-devel@nongnu.org; Wed, 07 Oct 2009 17:52:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MveQu-0006zi-Kf for qemu-devel@nongnu.org; Wed, 07 Oct 2009 17:52:32 -0400 Received: from [199.232.76.173] (port=48577 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MveQu-0006zb-DC for qemu-devel@nongnu.org; Wed, 07 Oct 2009 17:52:28 -0400 Received: from mx1.redhat.com ([209.132.183.28]:8897) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MveQt-0004Zb-Pl for qemu-devel@nongnu.org; Wed, 07 Oct 2009 17:52:28 -0400 From: Juan Quintela Date: Wed, 07 Oct 2009 23:52:07 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Qemu-devel] Host clock broke loadvm List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka , qemu-devel@nongnu.org Hi Jan Today I found that I am not able to load anymore old saved images (old means more than 2 days old). Problem is with host clock. I need to run qemu with -rtc clock=vm, and then things cames to work again. My suspicion is that the saved timers are based from cpu_clock_offset, and when we run now with host_clock, that value don't exist. If I don't use -rtc clock=vm, machines will come eventually to life, but it will take several minutes. Anthony asked to change pc-11 definition to use vm clock. What do you think? Any other good idea to make a machine saved with clock=vm to load with clock=host. I tried the trial: if (cpu_clock_offset != 0) rtc_clock = vm_clock; after loading an image, but that didn't fixed the problem (I didn't investigate more). Do you have a plan to go from here? Later, Juan.