public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Lechner <cl0059@l-mx.de>
To: dbareiro@gmx.net, kvm@vger.kernel.org
Subject: Re: kvm-88: KVM_APIC_READ: read reserved register b0
Date: Sun, 30 Aug 2009 11:59:27 +0200	[thread overview]
Message-ID: <4A9A4D7F.3010904@l-mx.de> (raw)
In-Reply-To: <20090829212036.GA3014@defiant.freesoftware.org>

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.

- cl


  reply	other threads:[~2009-08-30  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28 10:04 kvm-88: KVM_APIC_READ: read reserved register b0 Christoph Lechner
2009-08-29 16:37 ` Christoph Lechner
2009-08-29 21:20 ` Daniel Bareiro
2009-08-30  9:59   ` Christoph Lechner [this message]
2009-08-30 10:01     ` Gleb Natapov
2009-08-30 11:42       ` Christoph Lechner
2009-08-30 11:49         ` Gleb Natapov
2009-08-30 15:28           ` Daniel Bareiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A9A4D7F.3010904@l-mx.de \
    --to=cl0059@l-mx.de \
    --cc=dbareiro@gmx.net \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox