On Wed, Apr 15, 2009 at 03:53:40PM +0400, Dmitry Eremin-Solenikov wrote: > Jan Kiszka пишет: >> 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 runs >>>> 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: e3dbe3f408a46a045012f1882e9f62b27b8a616c >>> from Avi's tree (KVM: x86 emulator: fix call near emulation) + these >>> patches. I have to boot the kernels (both this kernel and 2.6.26 from >>> 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 using > the image from the debian's bochsbios package. I asked qemu to use the > bios from 0.10.2 release and got slightly different messages. Attached > 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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
