On Tue, Aug 27, 2013 at 09:18:00AM +0200, Paolo Bonzini wrote: > > I've captured 20,000 lines of kvm trace output. This can be found > > https://gist.github.com/devicenull/fa8f49d4366060029ee4/raw/fb89720d34b43920be22e3e9a1d88962bf305da8/trace > > The guest is doing quite a lot of exits per second, mostly to (a) access > the ACPI timer I see a lot of PM timer access not ACPI timer. The solution for that is the patchset Brian linked. > (b) service NMIs. In fact, every NMI is reading the > timer too and causing an exit to QEMU. > Do you mean "kvm_exit: reason EXCEPTION_NMI rip 0xfffff800016dcf84 info 0 80000307"? Those are not NMIs, single NMI will kill Windows, they are #NM exceptions. Brian, is your workload uses floating point calculation? > So it is also possible that you have to debug this inside the guest, to > see if these exits are expected or not. > > Paolo > -- > 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 -- 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
