From: "Richard W.M. Jones" <rjones@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-1.5 0/3] qcow2: Catch some L1 table index overflows
Date: Mon, 13 May 2013 15:39:35 +0100 [thread overview]
Message-ID: <20130513143935.GH4515@redhat.com> (raw)
In-Reply-To: <1368452576-32262-1-git-send-email-kwolf@redhat.com>
On Mon, May 13, 2013 at 03:42:53PM +0200, Kevin Wolf wrote:
[...]
I tested the first patch (didn't try the tests) with qemu-img
and libguestfs and it works.
New qemu-img fails with:
qemu-img: The image size is too large for file format 'qcow2'
If you use the old qemu-img to create the file, and then try
to add it with the new qemu, you get:
-drive file=/tmp/huge.qcow2,cache=none,id=hd0,if=none: could not open disk image /tmp/huge.qcow2: File too large
(instead of a segfault).
So:
ACK.
Tested-by: Richard W.M. Jones <rjones@redhat.com>
My only gripe is it would be nice if the qemu-img error message
mentioned that you can use the -o cluster_size=XXX option.
> Suggestions for a better test case are welcome. But now that creating a large
> image file fails, and if you somehow manage to create it anyway (qcow2.py)
> opening it fails, it's hard to test the actual read/write cases.
It'd be nice if the test included a test of the huge case using -o
cluster_size=2M and a few reads and writes at the end of the disk,
just to make sure this doesn't break in future.
Also nice to have would be to be able to specify disk sizes using 'P'
and 'E' :-)
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
prev parent reply other threads:[~2013-05-13 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 13:42 [Qemu-devel] [PATCH for-1.5 0/3] qcow2: Catch some L1 table index overflows Kevin Wolf
2013-05-13 13:42 ` [Qemu-devel] [PATCH for-1.5 1/3] " Kevin Wolf
2013-05-13 13:42 ` [Qemu-devel] [PATCH 2/3] qcow2.py: Subcommand for changing header fields Kevin Wolf
2013-05-13 14:59 ` Stefan Hajnoczi
2013-05-13 13:42 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: Try creating huge qcow2 image Kevin Wolf
2013-05-13 14:39 ` Richard W.M. Jones [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=20130513143935.GH4515@redhat.com \
--to=rjones@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).