From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=55390 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OJSHa-0006Ch-OW
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 10:17:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <pl@dlh.net>) id 1OJSHY-0002p5-AX
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 10:17:30 -0400
Received: from zion.dlh.net ([91.198.192.1]:59811 helo=mail.dlh.net)
	by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from <pl@dlh.net>)
	id 1OJSHY-0002oW-61
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 10:17:28 -0400
Message-ID: <4C051669.4060209@dlh.net>
Date: Tue, 01 Jun 2010 16:17:13 +0200
From: Peter Lieven <pl@dlh.net>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: disable clocksource=kvm-clock
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>
In-Reply-To: <4C0514C6.3060203@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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.nongnu.org/archive/html/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: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org

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