From: Peter Lieven <pl@dlh.net>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, weil@mail.berlios.de,
anthony@codemonkey.ws
Subject: Re: qemu-kvm-1.0 crashes with threaded vnc server?
Date: Tue, 13 Mar 2012 12:29:06 +0100 [thread overview]
Message-ID: <4F5F2F82.3040000@dlh.net> (raw)
In-Reply-To: <CAHR064jArbRzyCC23yejFCvSn_uwkHs50AiAhQCG8UCi2LxhwA@mail.gmail.com>
On 11.02.2012 09:55, Corentin Chary wrote:
> On Thu, Feb 9, 2012 at 7:08 PM, Peter Lieven<pl@dlh.net> wrote:
>> Hi,
>>
>> is anyone aware if there are still problems when enabling the threaded vnc
>> server?
>> I saw some VMs crashing when using a qemu-kvm build with
>> --enable-vnc-thread.
>>
>> qemu-kvm-1.0[22646]: segfault at 0 ip 00007fec1ca7ea0b sp 00007fec19d056d0
>> error 6 in libz.so.1.2.3.3[7fec1ca75000+16000]
>> qemu-kvm-1.0[26056]: segfault at 7f06d8d6e010 ip 00007f06e0a30d71 sp
>> 00007f06df035748 error 6 in libc-2.11.1.so[7f06e09aa000+17a000]
>>
>> I had no time to debug further. It seems to happen shortly after migrating,
>> but thats uncertain. At least the segfault in libz seems to
>> give a hint to VNC since I cannot image of any other part of qemu-kvm using
>> libz except for VNC server.
>>
>> Thanks,
>> Peter
>>
>>
> Hi Peter,
> I found two patches on my git tree that I sent long ago but somehow
> get lost on the mailing list. I rebased the tree but did not have the
> time (yet) to test them.
> http://git.iksaif.net/?p=qemu.git;a=shortlog;h=refs/heads/wip
> Feel free to try them. If QEMU segfault again, please send a full gdb
> backtrace / valgrind trace / way to reproduce :).
> Thanks,
>
I have seen no more crashes with these to patches applied. I would suggest
it would be good to push them to the master repository.
Thank you,
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlh.net>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: anthony@codemonkey.ws, weil@mail.berlios.de,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] qemu-kvm-1.0 crashes with threaded vnc server?
Date: Tue, 13 Mar 2012 12:29:06 +0100 [thread overview]
Message-ID: <4F5F2F82.3040000@dlh.net> (raw)
In-Reply-To: <CAHR064jArbRzyCC23yejFCvSn_uwkHs50AiAhQCG8UCi2LxhwA@mail.gmail.com>
On 11.02.2012 09:55, Corentin Chary wrote:
> On Thu, Feb 9, 2012 at 7:08 PM, Peter Lieven<pl@dlh.net> wrote:
>> Hi,
>>
>> is anyone aware if there are still problems when enabling the threaded vnc
>> server?
>> I saw some VMs crashing when using a qemu-kvm build with
>> --enable-vnc-thread.
>>
>> qemu-kvm-1.0[22646]: segfault at 0 ip 00007fec1ca7ea0b sp 00007fec19d056d0
>> error 6 in libz.so.1.2.3.3[7fec1ca75000+16000]
>> qemu-kvm-1.0[26056]: segfault at 7f06d8d6e010 ip 00007f06e0a30d71 sp
>> 00007f06df035748 error 6 in libc-2.11.1.so[7f06e09aa000+17a000]
>>
>> I had no time to debug further. It seems to happen shortly after migrating,
>> but thats uncertain. At least the segfault in libz seems to
>> give a hint to VNC since I cannot image of any other part of qemu-kvm using
>> libz except for VNC server.
>>
>> Thanks,
>> Peter
>>
>>
> Hi Peter,
> I found two patches on my git tree that I sent long ago but somehow
> get lost on the mailing list. I rebased the tree but did not have the
> time (yet) to test them.
> http://git.iksaif.net/?p=qemu.git;a=shortlog;h=refs/heads/wip
> Feel free to try them. If QEMU segfault again, please send a full gdb
> backtrace / valgrind trace / way to reproduce :).
> Thanks,
>
I have seen no more crashes with these to patches applied. I would suggest
it would be good to push them to the master repository.
Thank you,
Peter
next prev parent reply other threads:[~2012-03-13 11:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 18:08 qemu-kvm-1.0 crashes with threaded vnc server? Peter Lieven
2012-02-09 18:08 ` [Qemu-devel] " Peter Lieven
2012-02-11 8:55 ` Corentin Chary
2012-02-11 8:55 ` [Qemu-devel] " Corentin Chary
2012-02-13 9:24 ` Peter Lieven
2012-02-13 9:24 ` [Qemu-devel] " Peter Lieven
2012-02-28 8:37 ` Corentin Chary
2012-02-28 8:37 ` [Qemu-devel] " Corentin Chary
2012-02-28 11:48 ` Peter Lieven
2012-02-28 11:48 ` [Qemu-devel] " Peter Lieven
2012-03-13 11:29 ` Peter Lieven [this message]
2012-03-13 11:29 ` Peter Lieven
2012-03-13 15:05 ` Corentin Chary
2012-03-13 15:05 ` [Qemu-devel] " Corentin Chary
2012-03-13 15:06 ` Alexander Graf
2012-03-13 15:06 ` [Qemu-devel] " Alexander Graf
2012-06-26 15:02 ` Peter Lieven
2012-06-28 10:18 ` Corentin Chary
2012-06-28 10:21 ` Peter Lieven
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=4F5F2F82.3040000@dlh.net \
--to=pl@dlh.net \
--cc=anthony@codemonkey.ws \
--cc=corentin.chary@gmail.com \
--cc=kvm@vger.kernel.org \
--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 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.