From: Aurelien Jarno <aurel32@debian.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 592056] Re: qemu segmentation fault when create qcow2 image with qemu-img command
Date: Sun, 20 Feb 2011 17:16:36 -0000 [thread overview]
Message-ID: <20110220171636.30233.53286.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 20100610074137.20134.96759.malonedeb@palladium.canonical.com
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/592056
Title:
qemu segmentation fault when create qcow2 image with qemu-img command
Status in QEMU:
Fix Released
Bug description:
Host OS: ia32e
kvm.git Commit:cf18597a046413e9f0dd8df3ad6715a88766be51
qemu-kvm Commit:3f505ec990599aeb960ed7031a2bb7b233ea4927
Host Kernel Version:2.6.35-rc2+
Hardware:Westmere-HEDT
Bug detailed description:
--------------------------
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.
Reproduce steps:
----------------
1.boot up into KVM ia32e host
2.use command: qemu-img create -b /path/to/file.img -f qcow2 /path/to/qcow.img
3.it displays: segmentation fault
prev parent reply other threads:[~2011-02-20 17:26 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
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 [this message]
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=20110220171636.30233.53286.launchpad@wampee.canonical.com \
--to=aurel32@debian.org \
--cc=592056@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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).