From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 10/11] VMX: work around lacking VNMI support Date: Wed, 24 Sep 2008 15:44:15 +0300 Message-ID: <48DA361F.7060009@redhat.com> References: <48D74CE6.5060008@siemens.com> <200809231742.03316.sheng.yang@intel.com> <20080923094544.GE3072@minantech.com> <200809231750.49882.sheng.yang@intel.com> <48DA3532.9040306@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Yang, Sheng" , Gleb Natapov , kvm-devel To: Jan Kiszka Return-path: Received: from mx2.redhat.com ([66.187.237.31]:44603 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751517AbYIXMoX (ORCPT ); Wed, 24 Sep 2008 08:44:23 -0400 In-Reply-To: <48DA3532.9040306@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: Jan Kiszka wrote: > After Windows' graphical installation phase I had a hanging guest. At > the same time I got > > kvm_handle_exit: unexpected, valid vectoring info and exit reason is 0x9 > kvm_handle_exit: Breaking out of NMI-blocked state on VCPU 0 after 1 s > timeout > > in the kernel log as well. Something is borken. Will retest the > installation with vanilla KVM. Anyone any ideas on the task switch > thing? Just a false positive or an indication for the real problem in > that domain? > Check the descriptor type for the NMI vector, that should show if it's real or not. -- error compiling committee.c: too many arguments to function