From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weil <weil@mail.berlios.de>
Cc: Peter Lieven <pl@dlh.net>, qemu-devel <qemu-devel@nongnu.org>,
kvm@vger.kernel.org, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] segmentation fault in qemu-kvm-0.14.0
Date: Wed, 09 Mar 2011 10:39:17 +0300 [thread overview]
Message-ID: <4D772EA5.8030809@msgid.tls.msk.ru> (raw)
In-Reply-To: <4D772BBC.4040603@mail.berlios.de>
09.03.2011 10:26, Stefan Weil wrote:
> Am 08.03.2011 23:53, schrieb Peter Lieven:
>> Hi,
>>
>> during testing of qemu-kvm-0.14.0 i can reproduce the following
>> segfault. i have seen similar crash already in 0.13.0, but had no time
>> to debug.
>> my guess is that this segfault is related to the threaded vnc server
>> which was introduced in qemu 0.13.0. the bug is only triggerable if a vnc
>> client is attached. it might also be connected to a resolution change
>> in the guest. i have a backtrace attached. the debugger is still
>> running if someone
>> needs more output
>>
[]
> Hi Peter,
>
> did you apply this patch which fixes one of the known vnc problems
> (but is still missing in qemu git master):
>
> http://lists.nongnu.org/archive/html/qemu-devel/2011-03/msg00256.html
This patch is not suitable for 0.14 since in current qemu/master quite
alot of stuff were changed in this area (bitmaps added), there's no
similar infrastructure in 0.14.
> Then you can read this thread:
>
> http://lists.nongnu.org/archive/html/qemu-devel/2011-03/msg00313.html
>
> And finally the following modifications of ui/vnc.c might help to see
> whether you experience the same kind of crash as I get here in
> my environment. They add assertions for bad memory access
> which occurs sometimes when a vnc client-server connection exists and
> the screen is refreshed after a resolution change.
> The code line with the //~ comment also includes a fix which
> works for me.
The same is true for this patch, but of a less extent: it can be applied
manually (the bitmap_empty context line).
I wonder if something similar actually exists in 0.13/0.14 too and needs
to be backported to -stable.
> Regards,
> Stefan W.
Thanks!
/mjt
next prev parent reply other threads:[~2011-03-09 7:39 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 22:53 segmentation fault in qemu-kvm-0.14.0 Peter Lieven
2011-03-09 7:13 ` [Qemu-devel] " Corentin Chary
2011-03-09 7:26 ` Stefan Weil
2011-03-09 7:39 ` Michael Tokarev [this message]
2011-03-09 9:22 ` Stefan Weil
2011-03-09 10:00 ` Peter Lieven
2011-03-15 12:53 ` Peter Lieven
2011-03-15 18:52 ` Stefan Weil
2011-03-09 7:37 ` Jan Kiszka
2011-03-09 8:50 ` [Qemu-devel] " Corentin Chary
2011-03-09 9:04 ` Jan Kiszka
2011-03-09 9:54 ` Corentin Chary
2011-03-09 9:58 ` Jan Kiszka
2011-03-09 10:02 ` Jan Kiszka
2011-03-09 10:06 ` Corentin Chary
2011-03-09 10:12 ` Jan Kiszka
2011-03-09 10:14 ` Corentin Chary
2011-03-09 10:17 ` Jan Kiszka
2011-03-09 10:41 ` [PATCH] vnc: threaded server depends on io-thread Corentin Chary
2011-03-09 10:50 ` Peter Lieven
2011-03-09 10:57 ` Corentin Chary
2011-03-09 11:05 ` Stefan Hajnoczi
2011-03-09 11:25 ` Jan Kiszka
2011-03-09 11:32 ` Peter Lieven
2011-03-09 11:33 ` Jan Kiszka
2011-03-09 11:42 ` Jan Kiszka
2011-03-09 12:50 ` Peter Lieven
2011-03-09 13:21 ` [PATCH v2] " Corentin Chary
2011-03-09 13:42 ` Corentin Chary
2011-03-09 13:51 ` Paolo Bonzini
2011-03-09 13:59 ` Corentin Chary
2011-03-10 12:59 ` [PATCH 1/2] sockets: add qemu_socketpair() Corentin Chary
2011-03-10 12:59 ` [PATCH 2/2] vnc: don't mess up with iohandlers in the vnc thread Corentin Chary
2011-03-10 13:06 ` Paolo Bonzini
2011-03-10 13:45 ` Anthony Liguori
2011-03-10 13:54 ` Corentin Chary
2011-03-10 13:58 ` Paolo Bonzini
2011-03-10 13:56 ` Paolo Bonzini
2011-03-10 13:47 ` Peter Lieven
2011-03-10 15:13 ` [PATCH v5] " Corentin Chary
2011-03-14 9:19 ` Corentin Chary
2011-03-14 9:55 ` Peter Lieven
2011-03-15 16:55 ` Peter Lieven
2011-03-15 18:07 ` Peter Lieven
2011-03-09 10:02 ` segmentation fault in qemu-kvm-0.14.0 Peter Lieven
2011-03-09 10:16 ` Peter Lieven
2011-03-09 10:20 ` Jan Kiszka
2011-03-09 10:31 ` Peter Lieven
2011-03-09 11:20 ` Paolo Bonzini
2011-03-09 11:44 ` Jan Kiszka
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=4D772EA5.8030809@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--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