On Tue, Jul 27, 2010 at 3:04 AM, Avi Kivity <avi@xxxxxxxxxx> wrote: > On 07/26/2010 08:58 PM, ewheeler wrote: >>> >>> O >>> n 07/26/2010 07:01 PM, Neo Jia wrote: >>>> >>>> hi, >>>> >>>> I am seeing an unhandled vm exit: 0x11 on Win7 with KVM-88 release and >>>> wondering if I am still able to dump the code from guest OS when this >>>> happens. But it looks that all instructions are 0s after adding one >>>> more print code after dumping the guest registers. >>>> >>>> And it is very likely that this problem is fixed in the latest qemu >>>> code base but I still would like to know how to debug and investigate >>>> this kind of problem. BTW, I am using 32-bit qemu + 64-bit KVM kernel >>>> module. >>>> >>>> unhandled vm exit: 0x11 Avi, I found the instruction that caused this problem: emulation failed (failure) rip 71f14651 66 0f 7f 07 And according to Intel, this is a MOVDQA. So, do we already have this instruction emulated as I am using a pretty old version of KVM (release 88)? If yes, could you point me to the file I need to look at for that specific patch? Currently, I am trying to use coalesced_mmio as you suggested in another thread: http://www.mail-archive.com/kvm@xxxxxxxxxxxxxxx/msg25695.html Thanks, Neo >> >> I happened to be in the intel docs today: >> 0x11 (17) RSM. Guest software attempted to execute RSM in SMM. > > As it happens, the 0x11 should be looked up as a KVM_EXIT_REASON (kvm.h), > not in the manuals as I said. It's a kvm internal error. > >> What is RSM and SMM? > > These are documented in the manuals. > > -- > error compiling committee.c: too many arguments to function > > -- I would remember that if researchers were not ambitious probably today we haven't the technology we are using! -- 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
