From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 78331] New: Qemu crash in x86
Date: Thu, 19 Jun 2014 07:14:18 +0000
Message-ID: <bug-78331-28872@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.kernel.org ([198.145.19.201]:55798 "EHLO mail.kernel.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753794AbaFSHOV (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 19 Jun 2014 03:14:21 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
	by mail.kernel.org (Postfix) with ESMTP id CFE3920398
	for <kvm@vger.kernel.org>; Thu, 19 Jun 2014 07:14:19 +0000 (UTC)
Received: from bugzilla2.web.kernel.org (bugzilla2.web.kernel.org [172.20.200.52])
	by mail.kernel.org (Postfix) with ESMTP id 62ABE2038E
	for <kvm@vger.kernel.org>; Thu, 19 Jun 2014 07:14:18 +0000 (UTC)
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

https://bugzilla.kernel.org/show_bug.cgi?id=78331

            Bug ID: 78331
           Summary: Qemu crash in x86
           Product: Virtualization
           Version: unspecified
    Kernel Version: 2.6.32
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: janakiram.sistla@gmail.com
        Regression: No

Hi all,



I am running qemu on an x86 host and when the host reloaded we do see a core on
Qemu and the gdb dump shows as follows. 

Can any one please let me know if any one has come across such failures.

rning: Can't read pathname for load map: Input/output error.

Core was generated by `/usr/bin/qemu-system-x86_64 -name default-sdr--2 -S -M
pc_q35 -enable-kvm -m 61'.

Program terminated with signal 11, Segmentation fault.

#0  0x000000000049c976 in qemu_bh_delete (bh=0x31) at
/auto/thirdparty-sdk/release/235/thirdparty/opensource/qemu-kvm/contents/async.c:193

193         bh->scheduled = 0;

(gdb) bt

#0  0x000000000049c976 in qemu_bh_delete (bh=0x31)

    at
/auto/thirdparty-sdk/release/235/thirdparty/opensource/qemu-kvm/contents/async.c:193

#1  0x00000000004c50a3 in qemu_chr_generic_open_bh (opaque=0xdc1f670)

    at
/auto/thirdparty-sdk/release/235/thirdparty/opensource/qemu-kvm/contents/qemu-char.c:130

#2  0x000000000049c7e4 in qemu_bh_poll ()

    at
/auto/thirdparty-sdk/release/235/thirdparty/opensource/qemu-kvm/contents/async.c:150

#3  0x000000000042017d in main_loop_wait (nonblocking=0)

    at
/auto/thirdparty-sdk/release/235/thirdparty/opensource/qemu-kvm/contents/vl.c:1384

#4  0x000000000043bae5 in kvm_main_loop ()

    at
/auto/thirdparty-sdk/release/235/thirdparty/opensource/qemu-kvm/contents/qemu-kvm.c:1710

#5  0x0000000000420237 in main_loop ()

    at
/auto/thirdparty-sdk/release/235/thirdparty/opensource/qemu-kvm/contents/vl.c:1408

#6  0x0000000000423bf4 in main (argc=67, argv=0x7fffc1ec48a8,
envp=0x7fffc1ec4ac8)

    at
/auto/thirdparty-sdk/release/235/thirdparty/opensource/qemu-kvm/contents/vl.c:3159





Regards,

sistla.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.