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: Mon, 23 Mar 2009 16:08:54 +0200 [thread overview]
Message-ID: <49C797F6.8070308@redhat.com> (raw)
In-Reply-To: <200903231439.34107.andreas.tanz@kvt.de>
Andreas Tanz wrote:
> Mar 23 14:27:35 [kernel] [ 5252.775939] vmx->handle_exception 10 : handle_rmode_exception(vcpu, intr_info & INTR_INFO_VECTOR_MASK, error_code) returned 0x1
> Mar 23 14:27:35 [kernel] [ 5252.775955] vmx->vmx_vcpu_run() 00 : vmcs_read32(VM_ENTRY_INTR_INFO_FIELD) returned 0x8000040d
> Mar 23 14:27:35 [kernel] [ 5252.775967] vmx->handle_exception 00 : giving some infos
> Mar 23 14:27:35 [kernel] [ 5252.775972] vmx->handle_exception 01 : vect_info: 0x0
> Mar 23 14:27:35 [kernel] [ 5252.775978] vmx->handle_exception 02 : intr_info: 0x80000b0d, is_page_fault()==0
> Mar 23 14:27:35 [kernel] [ 5252.775984] vmx->handle_exception 03 : irq_chip_in_kernel()==1
> Mar 23 14:27:35 [kernel] [ 5252.775989] vmx->handle_exception 04 : is_external_interrupt()==0
> Mar 23 14:27:35 [kernel] [ 5252.775995] vmx->handle_exception 0a : kvm_rip_read(vcpu) returned 0x3154
> Mar 23 14:27:35 [kernel] [ 5252.776000] vmx->handle_exception 0f : vcpu->arch.rmode.active: 0x1
> Mar 23 14:27:35 [kernel] [ 5252.776015] vmx->handle_exception 10 : handle_rmode_exception(vcpu, intr_info & INTR_INFO_VECTOR_MASK, error_code) returned 0x1
>
>
Okay, the data is already poisoned at this point. We need something
from earlier in time.
Try adding at the beginning of kvm_handle_exit() (after the three lines
of declarations):
{
static int counter;
if (kvm_rip_read(vcpu) == 0x3154 && counter++ >= 2) {
kvm_run->exit_reason = KVM_EXIT_UNKNOWN;
kvm_run->hw.hardware_exit_reason = exit_reason;
return 0;
}
}
This time, qemu should exit instead of looping. Please post the last
few screenfulls of dmesg.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-23 14:09 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
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 [this message]
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=49C797F6.8070308@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.