On Tue, Jul 8, 2008 at 3:52 AM, Mohammed Gamal <[EMAIL PROTECTED]> wrote: > On Mon, Jul 7, 2008 at 6:29 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote: >> Avi Kivity wrote: >>> >>> Mohammed Gamal wrote: >>> >>> I think they're fine. Can you check the vmentry patch now, with Anthony's >>> testcase? >> >> The following patch makes the problem almost 100% reproducible on my system. >> This strongly suggests a timing issue. >> >> Regards, >> >> Anthony Liguori >> >> > It's true indeed, the patch did increase the likelihood of the > problem with me (although it occurs every few runs). I modified > invalid_guest_state() to call kvm_report_emulation_failure() in all > cases and I noticed that whenever the crash happens it happens here: > > rip 6e10 66 b8 20 00 > > It's too late at night here, so I'll not lookup the opcode map now :) > . I'll further look into it later. >
Another thing, I tried -no-kvm-pit switch and it tremendously increase the likelihood of the crash to almost a 100%. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
