From: Kevin Wolf <kwolf@redhat.com>
To: Bug 592056 <592056@bugs.launchpad.net>
Cc: xudong <xudong.hao@intel.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 592056] [NEW] qemu segmentation fault when create qcow2 image with qemu-img command
Date: Thu, 10 Jun 2010 10:59:29 +0200 [thread overview]
Message-ID: <4C10A971.8020705@redhat.com> (raw)
In-Reply-To: <20100610074137.20134.96759.malonedeb@palladium.canonical.com>
Am 10.06.2010 09:41, schrieb xudong:
> when use "qemu-img" command to create qcow image, segmentation fault will
> happen.
> dmesg: qemu-img[1883] general protection ip:32f0477d20 sp:7fff9c89b308
> error:0 in libc-2.5.so[32f0400000+14a000]
>
> Bisected commit ea25559830a1a025e534dea634158c0141c71894 in qemu-kvm tree bring up this
> issue.
Can you please provide a backtrace? I couldn't reproduce this in a quick
attempt, so I can't get it myself.
next prev parent reply other threads:[~2010-06-10 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 7:41 [Qemu-devel] [Bug 592056] [NEW] qemu segmentation fault when create qcow2 image with qemu-img command xudong
2010-06-10 8:59 ` Kevin Wolf [this message]
2010-06-10 9:30 ` Hao, Xudong
2010-06-11 7:20 ` Hao, Xudong
2010-06-23 8:38 ` [Qemu-devel] [Bug 592056] " xudong
2010-06-24 2:15 ` xudong
2011-02-20 17:16 ` Aurelien Jarno
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=4C10A971.8020705@redhat.com \
--to=kwolf@redhat.com \
--cc=592056@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
--cc=xudong.hao@intel.com \
/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).