On Tue, Apr 14, 2009 at 11:29:49PM +0400, Dmitry Eremin-Solenikov wrote: > 2009/4/14 Gleb Natapov <gleb@xxxxxxxxxx>: > > On Tue, Apr 14, 2009 at 06:32:29PM +0400, Dmitry Eremin-Solenikov wrote: > >> 2009/4/14 Gleb Natapov <gleb@xxxxxxxxxx>: > >> > On Tue, Apr 14, 2009 at 02:14:04PM +0000, Dmitry Eremin-Solenikov wrote: > >> >> Gleb Natapov wrote: > >> >> > >> >> > Start to use interrupt/exception queues like VMX does. This also fix the > >> >> > bug that if exit was caused by a guest internal exception access to IDT > >> >> > the exception was not reinjected. > >> >> > >> >> This patch broke KVM for me: after it is applied (to the tip of avi's git tree), > >> >> linux inside KVM (version 84 from Debian) stops booting, moaning about lost > >> >> interrupts from ide. The KVM is executed inside qemu-system-x86_64, > >> >> version 0.10.2. > >> >> > >> > Please apply next patch in the series too. This one will not work > >> > without it. But better yet can you please test entire series. > >> > >> After applying the next patch (or the whole serie), I get the following messages > >> during initramfs drivers probe: > >> > >> Clocksource tsc unstable (delta...) > >> no cont in shutdown! > >> floppy0: FDC access conflict! > >> > >> Then kernel boot stalls. I'll try gdbing into kernel but this may > >> require lots of efforts. > >> I don't quite understand how do these two patches influence FDC emulation, but > >> they do. Tell me if you need any additional info. > >> > > What guest is this? What kernel? Does the whole series works? > > Guest: Debian lenny. Linux 2.6.26, Debian version (I can provide > config or bzImage + initrd). Yes please provide. Debian lenny (x86_64) is my default guest :) And I just booted it fine on AMD barcelona CPU. What is you host cpu? "cat /proc/cpuinfo" I just noticed that my kernel is different. Will install 2.6.26 and retest, but provide me yours anyway. > The whole serie doesn't work too (that's why I started bisecting). > > And BTW, I got the same results with -no-kvm-irqchip > -- 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
