[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <516FBBF7.1080400@redhat.com>
Date: Thu, 18 Apr 2013 11:25:11 +0200
From: Gerd Hoffmann <kraxel@...hat.com>
To: Stefan Hajnoczi <stefanha@...il.com>
CC: "Zhanghaoyu (A)" <haoyu.zhang@...wei.com>,
"Huangweidong (C)" <weidong.huang@...wei.com>,
kvm list <kvm@...r.kernel.org>,
Marcelo Tosatti <mtosatti@...hat.com>,
Luonengjun <luonengjun@...wei.com>,
qemu-devel <qemu-devel@...gnu.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Zanghongyong <zanghongyong@...wei.com>,
Zhanghuanzhong <zhanghuanzhong@...wei.com>,
corentin.chary@...il.com
Subject: Re: [Qemu-devel] reply: reply: qemu crashed when starting vm(kvm)
with vnc connect
On 04/11/13 11:29, Stefan Hajnoczi wrote:
> On Mon, Apr 08, 2013 at 12:27:06PM +0000, Zhanghaoyu (A) wrote:
>> On Sun, Apr 07, 2013 at 04:58:07AM +0000, Zhanghaoyu (A) wrote:
>>>>>> I start a kvm VM with vnc(using the zrle protocol) connect, sometimes qemu program crashed during starting period, received signal SIGABRT.
>>>>>> Trying about 20 times, this crash may be reproduced.
>>>>>> I guess the cause memory corruption or double free.
>>>>>
>>>>> Which version of QEMU are you running?
>>>>>
>>>>> Please try qemu.git/master.
Please try again with latest master, might be fixed meanwhile.
If it still happens pleas provide full qemu and vnc client command lines.
>> backtrace from core file is shown as below:
>>
>> Program received signal SIGABRT, Aborted.
>> #8 0x00007f32efd26d07 in vnc_disconnect_finish (vs=0x7f32f0c762d0)
>> at ui/vnc.c:1050
Do you have a vnc client connected? Do you close it?
Any errors reported by the vnc client (maybe it disconnects due to an
error in the data stream)?
cheers,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists