From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Ravi Kumar Kulkarni <ravilinux4u@gmail.com>
Cc: 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: Sun, 06 Feb 2011 19:20:32 +0200 [thread overview]
Message-ID: <4D4ED860.2060109@redhat.com> (raw)
In-Reply-To: <4D4C0613.9050309@siemens.com>
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.
> Start with capturing the activity of you guest via ftrace, enabling all
> kvm:* events. You may also try to attach gdb to qemu and analyze the
> different code path in both versions (specifically if you have debugging
> symbols for your guest).
The easy way to do that is trace-cmd (http://lwn.net/Articles/341902/):
$ trace-cmd record -e kvm -b 20000
...
^C
$ trace-cmd report
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-06 17:20 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 ` Avi Kivity [this message]
2011-02-07 8:33 ` [Qemu-devel] Re: [SeaBIOS] " Ravi Kumar Kulkarni
2011-02-07 8:49 ` Avi Kivity
2011-02-07 9:24 ` Ravi Kumar Kulkarni
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=4D4ED860.2060109@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=ravilinux4u@gmail.com \
--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).