qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/5] Add qemu-img check subcommand
Date: Mon, 20 Apr 2009 13:30:30 +0300	[thread overview]
Message-ID: <20090420103030.GV10126@redhat.com> (raw)
In-Reply-To: <1239969879-5611-1-git-send-email-kwolf@redhat.com>

On Fri, Apr 17, 2009 at 02:04:34PM +0200, Kevin Wolf wrote:
> Current qcow2 code already includes some functions to do some consistency
> checks (e.g. compare refcounts to real usage). Allowing the user (or developer
> debugging qcow2 code) to check his images only involves actually building this
> code and exposing it to the user by qemu-img.
> 
> This patch series implements a check subcommand for qemu-img. I think it will
> be useful especially in combination with qemu-io for test suites.
> 
Qumranet's product had this functionality and I found it to be so useful
that I still have qemu-img binary that has this "check" verb. For
instance if windows starts to BSOD to often the first thing I do is to
check that image is not corrupted.

> Kevin
> 
> Kevin Wolf (5):
>   qcow2: Fix warnings in check_refcount()
>   Introduce bdrv_check
>   Introduce qemu-img check subcommand
>   qcow2: Refcount checking code cleanup
>   qcow2: Add plausibility check for L1/L2 entries
> 
>  block-qcow2.c |  239 +++++++++++++++++++++++++++++++++++++++++---------------
>  block.c       |   14 ++++
>  block.h       |    1 +
>  block_int.h   |    3 +
>  qemu-img.c    |   62 +++++++++++++++
>  5 files changed, 255 insertions(+), 64 deletions(-)
> 
> 

--
			Gleb.

      parent reply	other threads:[~2009-04-20 10:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 12:04 [Qemu-devel] [PATCH 0/5] Add qemu-img check subcommand Kevin Wolf
2009-04-17 12:40 ` [Qemu-devel] [PATCH 1/5] qcow2: Fix warnings in check_refcount() Kevin Wolf
2009-04-17 14:01 ` kwolf
2009-04-17 20:39   ` Anthony Liguori
2009-04-17 21:00     ` Kevin Wolf
2009-04-17 21:03       ` Anthony Liguori
2009-04-17 21:19         ` Kevin Wolf
2009-04-17 22:07           ` Anthony Liguori
2009-04-17 22:29             ` Kevin Wolf
2009-04-17 22:31               ` Anthony Liguori
2009-04-18  0:11                 ` Ryan Harper
2009-04-20 13:48                 ` Christoph Hellwig
2009-04-21 16:19         ` Kevin Wolf
2009-04-20 13:46     ` Christoph Hellwig
2009-04-21 23:12   ` Anthony Liguori
2009-04-17 14:01 ` [Qemu-devel] [PATCH 2/5] Introduce bdrv_check kwolf
2009-04-17 14:01 ` [Qemu-devel] [PATCH 3/5] Introduce qemu-img check subcommand kwolf
2009-04-17 14:01 ` [Qemu-devel] [PATCH 4/5] qcow2: Refcount checking code cleanup kwolf
2009-04-21  8:32   ` [Qemu-devel] [PATCH v2 " Kevin Wolf
2009-04-17 14:02 ` [Qemu-devel] [PATCH 5/5] qcow2: Add plausibility check for L1/L2 entries kwolf
2009-04-20 10:30 ` Gleb Natapov [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=20090420103030.GV10126@redhat.com \
    --to=gleb@redhat.com \
    --cc=kwolf@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).