From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [PATCH 05/15] Coalesce userspace/kernel irqchip interrupt injection logic. Date: Wed, 15 Apr 2009 15:01:41 +0300 Message-ID: <20090415120141.GG27675@redhat.com> References: <20090414142403.GC20739@redhat.com> <20090414145536.GD20739@redhat.com> <20090414194103.GK20739@redhat.com> <20090415094430.GB27675@redhat.com> <49E5C0F9.6050200@siemens.com> <49E5C46F.3010805@siemens.com> <49E5CAC4.3030002@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jan Kiszka , kvm@vger.kernel.org To: Dmitry Eremin-Solenikov Return-path: Received: from mx2.redhat.com ([66.187.237.31]:59554 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758169AbZDOMBp convert rfc822-to-8bit (ORCPT ); Wed, 15 Apr 2009 08:01:45 -0400 Content-Disposition: inline In-Reply-To: <49E5CAC4.3030002@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Apr 15, 2009 at 03:53:40PM +0400, Dmitry Eremin-Solenikov wrote= : > Jan Kiszka =D0=C9=DB=C5=D4: >> Dmitry Eremin-Solenikov wrote: >>> Gleb Natapov wrote: >>>> On Wed, Apr 15, 2009 at 01:30:29PM +0400, Dmitry Eremin-Solenikov = wrote: >>>>> qemu-x86_64 version 0.10.2 running on i386 >>>>> Due to problems with qemu-x86_64 I have to boot the 'host' kernel >>>>> with 'noapic'. >>>> Do you mean boot 'guest' kernel with noapic? The guest is what run= s >>>> inside qemu. So you are able to boot guest with 'noapic'? >>>> >>>> What is the command line you are using. >>> Well, since this caused lot's of questions, here is my setup: >>> >>> Main host: Debian squeeze, kernel 2.6.28 or .29 (doesn't matter), >>> qemu-system-x86_64 version 0.10.2 >>> >>> KVM kernel run inside qemu: e3dbe3f408a46a045012f1882e9f62b27b8a616= c >>> from Avi's tree (KVM: x86 emulator: fix call near emulation) + thes= e >>> patches. I have to boot the kernels (both this kernel and 2.6.26 fr= om >>> debian) with noapic to w/around APIC problems (I dunno if it's qemu= or >>> bochsbios problem). >> >> And the bios you are using with 0.10.2 is from 0.10.2 (when in doubt= , >> specify explicitly with -bios and/or -L)? Then this would be a QEMU >> upstream bug. > > Indeed, there seem to be problems with upstream qemu bios. I was usin= g > the image from the debian's bochsbios package. I asked qemu to use th= e =20 > bios from 0.10.2 release and got slightly different messages. Attache= d > the kernel log > Now it seems to be a problem with KVM bios. KVM will not work with upstream bochs or qemu bios only with its own version. -- Gleb.