From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Glauber Costa <glommer@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qcow2: fix image creation for large, > ~2TB, images
Date: Sun, 05 Apr 2009 12:42:52 -0500 [thread overview]
Message-ID: <49D8ED9C.20304@us.ibm.com> (raw)
In-Reply-To: <20090403212849.GC27148@sequoia.sous-sol.org>
Chris Wright wrote:
> When creating large disk images w/ qcow2 format, qcow2_create is hard
> coded to creating a single refcount block. This is insufficient for
> large images, and will cause qemu-img to segfault as it walks off the
> end of the refcount block. Keep track of the space needed during image
> create and create proper number of refcount blocks accordingly.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=491943
>
> Signed-off-by: Chris Wright <chrisw@redhat.com>
>
Applied. Thanks.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-04-05 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 21:28 [Qemu-devel] [PATCH] qcow2: fix image creation for large, > ~2TB, images Chris Wright
2009-04-05 17:42 ` Anthony Liguori [this message]
2009-04-05 18:18 ` Anthony Liguori
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=49D8ED9C.20304@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=glommer@redhat.com \
--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).