From: Ravi Kumar Kulkarni <ravilinux4u@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] Re: [SeaBIOS] IO APIC emulation failure with qemu-kvm
Date: Mon, 7 Feb 2011 14:54:04 +0530 [thread overview]
Message-ID: <AANLkTik_vm3anS7V6uPr-+9Duz2SUDvoJT=MPsuA-Rv2@mail.gmail.com> (raw)
In-Reply-To: <4D4FB231.1050107@redhat.com>
On Mon, Feb 7, 2011 at 2:19 PM, Avi Kivity <avi@redhat.com> wrote:
> On 02/07/2011 10:33 AM, Ravi Kumar Kulkarni wrote:
>>
>> On Sun, Feb 6, 2011 at 10:50 PM, Avi Kivity<avi@redhat.com> wrote:
>>>
>>> > On 02/04/2011 03:58 PM, Jan Kiszka wrote:
>>>>
>>>> >>
>>>>>
>>>>> >> > when i run my kernel image with qemu-kvm it gives emulation
>>>>> >> error
>>>>> >> > failure
>>>>> >> > trying to execute the code outside ROM or RAM at fec00000(IO
>>>>> >> APIC base
>>>>> >> > address)
>>>>> >> > but the same code runs fine with qemu. can anyone please point
>>>>> >> me
>>>>> >> > where might be the problem or how to find out this one?
>>>
>>> >
>>> > Please post the error message.
>>
>> Im attachin the error message in kvm.txt file with above mail.
>> KVM internal error. Suberror: 1
>> rax
>> 000000000000000d rbx 000000001e2db2a6 rcx 00000000fa4bec19 rdx
>> 0000000000000088
>> rsi 000000001f4de1ea rdi 0000000000000000 rsp
>> 00000000000c0004 rbp 000000001f464fbb
>>
>> r8 0000000000000000 r9 0000000000000000
>> r10 0000000000000000 r11 0000000000000000
>> r12
>> 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
>> 0000000000000000
>> rip 000000001e2f3f7b rflags 00010097
>> cs 0008
>> (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g
>
> What's the guest code at rip 0x1e2f3f7b ?
please find the code below.
(qemu) xp /20iw 0x1e2f3f83
0x000000001e2f3f83: pop %ds
0x000000001e2f3f84: jae
0x1e2f3f66
0x000000001e2f3f86: dec %ebp
0x000000001e2f3f87: pop %ds
0x000000001e2f3f88: pushf
0x000000001e2f3f89: aas
0x000000001e2f3f8a: das
0x000000001e2f3f8b: push
%ds
0x000000001e2f3f8c: iret
0x000000001e2f3f8d: test
$0x1e2e,%eax
0x000000001e2f3f92: add
%al,(%eax)
0x000000001e2f3f94: add %al,(%eax)
0x000000001e2f3f96: add
%al,(%eax)
0x000000001e2f3f98: or
$0x0,%eax
0x000000001e2f3f9d: add
%al,(%eax)
0x000000001e2f3f9f: add %cl,0x81e2f4c(%esi)
0x000000001e2f3fa5: add
%al,(%eax)
0x000000001e2f3fa7: add
%al,(%edx)
0x000000001e2f3fa9: add %al,(%ecx)
0x000000001e2f3fab: add
%cl,-0x1f(%edx)
Thanks,
Ravi Kulkarni.
>
> --
>
>
next prev parent reply other threads:[~2011-02-07 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 13:35 [Qemu-devel] IO APIC emulation failure with qemu-kvm Ravi Kumar Kulkarni
2011-02-04 13:58 ` [Qemu-devel] " Jan Kiszka
2011-02-06 17:20 ` [Qemu-devel] Re: [SeaBIOS] " Avi Kivity
2011-02-07 8:33 ` Ravi Kumar Kulkarni
2011-02-07 8:49 ` Avi Kivity
2011-02-07 9:24 ` Ravi Kumar Kulkarni [this message]
2011-02-07 9:29 ` Avi Kivity
2011-02-07 9:47 ` Ravi Kumar Kulkarni
2011-02-07 9:54 ` Avi Kivity
2011-02-07 10:28 ` Ravi Kumar Kulkarni
2011-02-07 13:17 ` 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='AANLkTik_vm3anS7V6uPr-+9Duz2SUDvoJT=MPsuA-Rv2@mail.gmail.com' \
--to=ravilinux4u@gmail.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).