>> 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%. >
I updated to the latest kvm-userspace git tree, and now the failure is happening at completely random instructions whether or not we are using -no-kvm-pit. -- 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
