From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: how to debug unhandled vm exit: 0x11? Date: Tue, 27 Jul 2010 13:04:52 +0300 Message-ID: <4C4EAF44.9040002@redhat.com> References: <4C4DB46F.3070509@redhat.com> <1280167113.15451.15.camel@geektop> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Neo Jia , kvm@vger.kernel.org To: ewheeler Return-path: Received: from mx1.redhat.com ([209.132.183.28]:17091 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755845Ab0G0KE5 (ORCPT ); Tue, 27 Jul 2010 06:04:57 -0400 In-Reply-To: <1280167113.15451.15.camel@geektop> Sender: kvm-owner@vger.kernel.org List-ID: 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 > 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