From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM on Via Nano (Isaiah) CPUs? Date: Thu, 19 Mar 2009 17:19:28 +0200 Message-ID: <49C26280.1080007@redhat.com> References: <200903180902.29139.andreas.tanz@kvt.de> <200903191155.06122.andreas.tanz@kvt.de> <49C239B0.8060005@redhat.com> <200903191610.48032.andreas.tanz@kvt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: andreas.tanz@kvt.de Return-path: Received: from mx2.redhat.com ([66.187.237.31]:48772 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752722AbZCSPTe (ORCPT ); Thu, 19 Mar 2009 11:19:34 -0400 In-Reply-To: <200903191610.48032.andreas.tanz@kvt.de> Sender: kvm-owner@vger.kernel.org List-ID: Andreas Tanz wrote: >>> --> dmesg : >>> [79116.175571] returning from kvm_handle_exit, cause 3, retval = 1, exit_reason = 0 >>> >> That's an exception or nmi. Next step is to instrument >> handle_exception() and see what happens there. Please print out >> vect_info, intr_info, and kvm_rip_read(vcpu) (all as hex). >> >> The more you instrument, of course, the better. >> >> > > for testing i killed the kvm guest 0.4s after starting it - got this: > > thousands of lines : > returning from kvm_handle_exit, cause 3, retval = 0, exit_reason = 30 > mixed with single line (every ca. 40th-100th line) : > returning from kvm_handle_exit, cause 3, retval = 1, exit_reason = 1 > ... > This is normal operation. 30 is IO_INSTRUCTION, the guest is probably reading its boot disk. 1 is EXTERNAL_INTERRUPT, normal host interrupts. So the guest hands a little later. Let it reach steady state and see where it hangs. -- error compiling committee.c: too many arguments to function