From: Max Reitz <mreitz@redhat.com>
To: Jeff Cody <jcody@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, sw@weilnetz.de, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 5/5] block: iotest - update 084 to test static VDI image creation
Date: Tue, 22 Jul 2014 22:21:48 +0200 [thread overview]
Message-ID: <53CEC7DC.6020407@redhat.com> (raw)
In-Reply-To: <b0f1625f9f62e2017cbd9090a7f25812fc7934b4.1405962961.git.jcody@redhat.com>
On 21.07.2014 21:52, Jeff Cody wrote:
> This updates the VDI corruption test to also test static VDI image
> creation, as well as the default dynamic image creation.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> tests/qemu-iotests/084 | 16 ++++++++++++++--
> tests/qemu-iotests/084.out | 15 +++++++++++++++
> 2 files changed, 29 insertions(+), 2 deletions(-)
>
> diff --git a/tests/qemu-iotests/084 b/tests/qemu-iotests/084
> index cb4d7b7..ae33c2c 100755
> --- a/tests/qemu-iotests/084
> +++ b/tests/qemu-iotests/084
> @@ -1,6 +1,7 @@
> #!/bin/bash
> #
> -# Test case for VDI header corruption; image too large, and too many blocks
> +# Test case for VDI header corruption; image too large, and too many blocks.
> +# Also simple test for creating dynamic and static VDI images.
> #
> # Copyright (C) 2013 Red Hat, Inc.
> #
> @@ -43,14 +44,25 @@ _supported_fmt vdi
> _supported_proto generic
> _supported_os Linux
>
> +size=64M
> ds_offset=368 # disk image size field offset
> bs_offset=376 # block size field offset
> bii_offset=384 # block in image field offset
>
> echo
> +echo "=== Statically allocated image creation ==="
> +echo
> +_make_test_img $size -o static
> +_img_info
> +stat -c"disk image file size in bytes: %s" "${TEST_IMG}"
> +_cleanup_test_img
> +
> +echo
> echo "=== Testing image size bounds ==="
> echo
> -_make_test_img 64M
> +_make_test_img $size
> +_img_info
> +stat -c"disk image file size in bytes: %s" "${TEST_IMG}"
>
> # check for image size too large
> # poke max image size, and appropriate blocks_in_image value
> diff --git a/tests/qemu-iotests/084.out b/tests/qemu-iotests/084.out
> index c7120d9..2dfafb7 100644
> --- a/tests/qemu-iotests/084.out
> +++ b/tests/qemu-iotests/084.out
> @@ -1,8 +1,23 @@
> QA output created by 084
>
> +=== Statically allocated image creation ===
> +
> +Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
> +statically allocating 67109888 bytes
This seems like left-over debug output to me (at least it doesn't show
up for me and I don't find it in block/vdi.c).
With this line removed:
Reviewed-by: Max Reitz <mreitz@redhat.com>
> +image: TEST_DIR/t.IMGFMT
> +file format: IMGFMT
> +virtual size: 64M (67108864 bytes)
> +cluster_size: 1048576
> +disk image file size in bytes: 67109888
> +
> === Testing image size bounds ===
>
> Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
> +image: TEST_DIR/t.IMGFMT
> +file format: IMGFMT
> +virtual size: 64M (67108864 bytes)
> +cluster_size: 1048576
> +disk image file size in bytes: 1024
> Test 1: Maximum size (1024 TB):
> qemu-img: Could not open 'TEST_DIR/t.IMGFMT': Could not open 'TEST_DIR/t.IMGFMT': Invalid argument
>
next prev parent reply other threads:[~2014-07-22 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 19:52 [Qemu-devel] [PATCH v2 0/5] Allow VPC and VDI to be created over protocols Jeff Cody
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 1/5] block: allow bdrv_unref() to be passed NULL pointers Jeff Cody
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 2/5] block: vdi - use block layer ops in vdi_create, instead of posix calls Jeff Cody
2014-07-22 20:14 ` Max Reitz
2014-07-22 20:19 ` Jeff Cody
2014-07-22 20:20 ` Max Reitz
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 3/5] block: use the standard 'ret' instead of 'result' Jeff Cody
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 4/5] block: vpc - use block layer ops in vpc_create, instead of posix calls Jeff Cody
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 5/5] block: iotest - update 084 to test static VDI image creation Jeff Cody
2014-07-22 20:21 ` Max Reitz [this message]
2014-07-22 20:24 ` Jeff Cody
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=53CEC7DC.6020407@redhat.com \
--to=mreitz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.