From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Lieven Subject: Re: [Qemu-devel] Re: disable clocksource=kvm-clock Date: Tue, 01 Jun 2010 16:17:13 +0200 Message-ID: <4C051669.4060209@dlh.net> References: <4C050743.3030603@dlh.net> <4C05087A.9090803@redhat.com> <4C0511BC.7080803@dlh.net> <4C0512AA.6060906@redhat.com> <4C0513DB.1080108@dlh.net> <4C0514C6.3060203@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from zion.dlh.net ([91.198.192.1]:58204 "EHLO mail.dlh.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756258Ab0FAOR3 (ORCPT ); Tue, 1 Jun 2010 10:17:29 -0400 In-Reply-To: <4C0514C6.3060203@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > On 06/01/2010 05:06 PM, Peter Lieven wrote: >> >> avi, i do not know whats going on. but if i supply -cpu xxx,-kvmclock >> the guest >> still uses kvm-clock, but it seems bug #584516 is not triggered... >> thats weird... > > I guess that bug was resolved in qemu-kvm.git. Likely 1a03675db1, but > it appears to be part of 0.12 too, so not sure. > > What qemu-kvm were you using previously? > i'm using qemu-kvm git from today (aa22e82). bug #585113 seems to be fixed (this was the irq nobody cared error with virtio_blk or e1000) bug #584516 is still there, but if I set - cpu xxx,-kvmclock it is not triggered. the guest shows current_clocksource = kvm_clock, but migration seems to succeed (at least the ~20 times i tested it since you told me about the flag) do you have a clue what fixed bug #585113. i would like to backport it to 0.12.4