From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:44905) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ROPzc-00013a-QO for qemu-devel@nongnu.org; Thu, 10 Nov 2011 03:28:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ROPzb-0001l8-9D for qemu-devel@nongnu.org; Thu, 10 Nov 2011 03:28:16 -0500 Received: from mx1.redhat.com ([209.132.183.28]:50819) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ROPza-0001kY-RL for qemu-devel@nongnu.org; Thu, 10 Nov 2011 03:28:15 -0500 Message-ID: <4EBB8B16.40903@redhat.com> Date: Thu, 10 Nov 2011 09:28:06 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <4EB351E6.3090807@cn.fujitsu.com> <4EB965CE.7000407@codemonkey.ws> <20111109162231.GH29718@otherpad.lan.raisama.net> In-Reply-To: <20111109162231.GH29718@otherpad.lan.raisama.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] reenable vm_clock when resuming all vcpus List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori , Wen Congyang , qemu-devel , Lucas Meneghel Rodrigues On 11/09/2011 05:22 PM, Eduardo Habkost wrote: > The bug was 100% reproducible on the machine I was testing, previously, > and after this commit it didn't happen anymore. I double-checked by > re-testing this commit (47113ab6), and the previous one (f67ab77a) > twice, after bisecting. > > (If anybody has some possible explanation on how this patch could have > any impact on the above symptoms, or want to investigate further, please > let me know. I think I will stop debugging this, move on, and finally > stress-test my qemu_fclose() series, now.) I'm not sure about how the patch could fix this, but I'm not surprised that Linux shows the bug in more mysterious ways than Windows. That's because Windows uses the (in-QEMU) HPET for timing and Linux by default uses the (in-kernel) kvmclock. Paolo