From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org,
Glauber de Oliveira Costa <gcosta@redhat.com>,
Stefan Weil <weil@mail.berlios.de>
Subject: Re: [Qemu-devel][BUG][PATCH] Fix crash in kvm.c
Date: Fri, 05 Dec 2008 16:37:34 -0600 [thread overview]
Message-ID: <4939AD2E.2080904@codemonkey.ws> (raw)
In-Reply-To: <4939A81E.4020301@mail.berlios.de>
Stefan Weil wrote:
> I got a crash (array access out of bounds results in access fault)
> with the current Qemu trunk when kvm is enabled:
>
> qemu -fda fd.img -cdrom cdrom.img -hda hda.img -hdb raw.img -m 256 -boot
> c -enable-kvm
>
> Host is Debian x86_64, the crash occurs before any code is emulated.
>
Is the patch incomplete, perhaps? It seems to just add asserts which
shouldn't fix anything.
I don't think any leaf should return a max leaf greater than 100
elements so I'd be pretty surprised to see this happen. I'd really like
to see the back trace to see which leaf is the problematic one and what
the greatest leaf being reported is.
> With the patch, the emulation (Win 98) boots, but has problems with the
> display of
> icons and the mouse cursor. Qemu displays lots of
> "BUG: kvm_physical_sync_dirty_bitmap: invalid parameters" messages.
>
It looks like Avi and Glauber found some bugs in this code. There are
patches for kvm-userspace right now that need porting to QEMU. I'll
take a look at that this weekend unless Glauber was already planning too.
Regards,
Anthony Liguori
> Stefan
>
>
next prev parent reply other threads:[~2008-12-05 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 22:15 [Qemu-devel][BUG][PATCH] Fix crash in kvm.c Stefan Weil
2008-12-05 22:37 ` Anthony Liguori [this message]
[not found] ` <4939B25F.8030203@mail.berlios.de>
[not found] ` <4939B2F3.5060307@codemonkey.ws>
2008-12-06 10:00 ` Stefan Weil
2008-12-11 21:03 ` Anthony Liguori
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=4939AD2E.2080904@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=gcosta@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).