From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: kvm problems on new hardware Date: Thu, 29 Oct 2009 17:07:40 -0500 Message-ID: <20091029220740.GI13808@us.ibm.com> References: <20091026100651.GA15566@dth.net> <4AE6C126.5030803@redhat.com> <1256639276.3889.29.camel@thinkpaddth> <4AE6CCA1.9000307@redhat.com> <1256841444.4117.16.camel@thinkpaddth> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , kvm@vger.kernel.org To: Danny ter Haar Return-path: Received: from e2.ny.us.ibm.com ([32.97.182.142]:37265 "EHLO e2.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753028AbZJ2WHl (ORCPT ); Thu, 29 Oct 2009 18:07:41 -0400 Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by e2.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id n9TM0Csb020492 for ; Thu, 29 Oct 2009 18:00:12 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n9TM7j0d1347786 for ; Thu, 29 Oct 2009 18:07:45 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id n9TC7ver003675 for ; Thu, 29 Oct 2009 08:07:57 -0400 Content-Disposition: inline In-Reply-To: <1256841444.4117.16.camel@thinkpaddth> Sender: kvm-owner@vger.kernel.org List-ID: * Danny ter Haar [2009-10-29 13:38]: > Update: > I compiled/installed 2.6.32-rc5-git3 on this machine > > I manually start kvm: > > vhost1:~# kvm -m 512 -cdrom /vz/template/iso/debian-503-amd64-netinst.iso > > The bootscreen comes up, i hit enter to install and i get these messages > (copied from dmesg) > > handle_exception: unexpected, vectoring info 0x80000010 intr info 0x80000b0d > handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d > [this line is repeated many times: > dmesg |grep 0x80000b0d | wc -l > 570 ] > and finally before ending the kvm session i get: > vmx_handle_exit: unexpected, valid vectoring info (0x8000000d) and exit reason is 0x80000021 I've seen that in a couple places. I don't think we have root cause, but in at least one situation (running win2k3 with > 4G of ram) the work around was to use: -cpu pentium3 This relates to what cpu features are exported in the virtual processor, so if this helps it's masking the real issue, but hopefully can help narrow down what we have to look at. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ryanh@us.ibm.com