From: Avi Kivity <avi@redhat.com>
To: andreas.tanz@kvt.de
Cc: kvm@vger.kernel.org
Subject: Re: KVM on Via Nano (Isaiah) CPUs? <Virus checked>
Date: Thu, 19 Mar 2009 14:25:20 +0200 [thread overview]
Message-ID: <49C239B0.8060005@redhat.com> (raw)
In-Reply-To: <200903191155.06122.andreas.tanz@kvt.de>
Andreas Tanz wrote:
> Hi!
>
>
>>> The guest starts up showing the Bochs BIOS POST and stucks giving thousands of lines :
>>> [15013.656923] returning from kvm_handle_exit, cause 3, retval = 1
>>>
>>>
>>>
>> What was the value of exit_reason?
>>
>>
> kernel/x86/vmx.c:
> 3211 static int kvm_handle_exit(struct kvm_run *kvm_run, struct kvm_vcpu *vcpu)
> 3212 {
> ...
> 3273 if (exit_reason < kvm_vmx_max_exit_handlers
> 3274 && kvm_vmx_exit_handlers[exit_reason]){
> 3275 int retval = kvm_vmx_exit_handlers[exit_reason](vcpu, kvm_run);
> 3276 printk(KERN_WARNING "returning from kvm_handle_exit, cause 3, retval = %i"
> 3277 ", exit_reason = %i\n"
> 3278 ,retval, exit_reason);
> 3279 // return kvm_vmx_exit_handlers[exit_reason](vcpu, kvm_run);
> 3280 return retval;
> 3281 }
> 3282 else {
> 3283 kvm_run->exit_reason = KVM_EXIT_UNKNOWN;
> 3284 kvm_run->hw.hardware_exit_reason = exit_reason;
> 3285 }
> 3286 printk(KERN_WARNING "returning from kvm_handle_exit\n
> 3287 return 0;
> 3288 }
> ...
>
> --> 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.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-19 12:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903180902.29139.andreas.tanz@kvt.de>
[not found] ` <200903181810.48603.andreas.tanz@kvt.de>
[not found] ` <49C20DEE.9040302@redhat.com>
2009-03-19 10:55 ` KVM on Via Nano (Isaiah) CPUs? <Virus checked> Andreas Tanz
2009-03-19 12:25 ` Avi Kivity [this message]
2009-03-19 15:10 ` Andreas Tanz
2009-03-19 15:19 ` Avi Kivity
2009-03-19 15:34 ` Andreas Tanz
2009-03-19 15:48 ` Avi Kivity
2009-03-19 17:05 ` Andreas Tanz
2009-03-19 17:20 ` Avi Kivity
2009-03-20 12:37 ` Andreas Tanz
2009-03-22 8:53 ` Avi Kivity
2009-03-22 9:03 ` Avi Kivity
2009-03-23 13:39 ` Andreas Tanz
2009-03-23 14:08 ` Avi Kivity
2009-03-23 17:33 ` Andreas Tanz
2009-03-23 18:41 ` Avi Kivity
2009-03-23 20:36 ` Avi Kivity
2009-03-25 9:45 ` Andreas Tanz
2009-03-23 18:50 ` [PATCH] mm/memory.c:unmap_vmas(): fix NULL * deref john cooper
2009-05-08 19:16 KVM on Via Nano (Isaiah) CPUs? Craig Metz
2009-05-09 9:32 ` Avi Kivity
2009-05-12 6:48 ` KVM on Via Nano (Isaiah) CPUs? <Virus checked> Andreas Tanz
2009-05-12 6:50 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C239B0.8060005@redhat.com \
--to=avi@redhat.com \
--cc=andreas.tanz@kvt.de \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.