From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Eremin-Solenikov Subject: Re: [PATCH 05/15] Coalesce userspace/kernel irqchip interrupt injection logic. Date: Wed, 15 Apr 2009 16:02:40 +0400 Message-ID: <49E5CCE0.1000904@siemens.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> <20090415120141.GG27675@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jan Kiszka , kvm@vger.kernel.org To: Gleb Natapov Return-path: Received: from david.siemens.de ([192.35.17.14]:24687 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753100AbZDOMDE (ORCPT ); Wed, 15 Apr 2009 08:03:04 -0400 In-Reply-To: <20090415120141.GG27675@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Gleb Natapov =D0=C9=DB=C5=D4: > On Wed, Apr 15, 2009 at 03:53:40PM +0400, Dmitry Eremin-Solenikov wro= te: >> 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' kerne= l >>>>>> with 'noapic'. >>>>> Do you mean boot 'guest' kernel with noapic? The guest is what ru= ns >>>>> 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: e3dbe3f408a46a045012f1882e9f62b27b8a61= 6c >>>> from Avi's tree (KVM: x86 emulator: fix call near emulation) + the= se >>>> patches. I have to boot the kernels (both this kernel and 2.6.26 f= rom >>>> debian) with noapic to w/around APIC problems (I dunno if it's qem= u or >>>> bochsbios problem). >>> And the bios you are using with 0.10.2 is from 0.10.2 (when in doub= t, >>> 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 usi= ng >> the image from the debian's bochsbios package. I asked qemu to use t= he =20 >> bios from 0.10.2 release and got slightly different messages. Attach= ed >> 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. I was talking about qemu-system_x86-64, not about KVM. --=20 With best wishes Dmitry