From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: kvm-88: KVM_APIC_READ: read reserved register b0 Date: Sun, 30 Aug 2009 13:01:59 +0300 Message-ID: <20090830100159.GT30093@redhat.com> References: <4A97AB92.9090509@l-mx.de> <20090829212036.GA3014@defiant.freesoftware.org> <4A9A4D7F.3010904@l-mx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dbareiro@gmx.net, kvm@vger.kernel.org To: Christoph Lechner Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49154 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554AbZH3KCD (ORCPT ); Sun, 30 Aug 2009 06:02:03 -0400 Content-Disposition: inline In-Reply-To: <4A9A4D7F.3010904@l-mx.de> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, Aug 30, 2009 at 11:59:27AM +0200, Christoph Lechner wrote: > Daniel Bareiro wrote: > > On Friday, 28 August 2009 12:04:02 +0200, > > Christoph Lechner wrote: > > > >> Hi all, > > > > Hi Christoph. > Hi. > > > >> running kvm-88 on a 2.6.26-1-amd64 kernel (stock Debian 5.0 kernel), I > >> get the syslog on the host system flooded with the message: > >> > >> Aug 28 11:49:40 reactor kernel: [124035.611782] KVM_APIC_READ: read > >> reserved register b0 > >> > >> [...] > > > > Also I am observing this behavior in one of my hosts with KVM-88 and > > Linux 2.6.30 compiled both by myself on Ubuntu GNU/Linux Hardy Heron > > server amd64, as I've mentioned in a previous [1] mail. Guests has > > Debian GNU/Linux Lenny with stock kernel 2.6.26. > > > > I was trying if with model=virtio the problem were solved, but was not > > successful. It would seem that the cause is due to something related to > > hardware of the host (is it possible?), since I have other hosts in > > which I use both the same version of KVM and kernel, also both compiled > > by myself, and I'm not having this problem. > > don't know if this is caused by the host hardware. But what I forgot to > mention: I commented out the printk call in lapic.c. This stopped the > flooding, but I know it's only a work around. > This printk no longer exists in upstream kvm. -- Gleb.