From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LvtrP-0000wm-Kb
	for qemu-devel@nongnu.org; Mon, 20 Apr 2009 09:48:35 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LvtrK-0000qV-QD
	for qemu-devel@nongnu.org; Mon, 20 Apr 2009 09:48:35 -0400
Received: from [199.232.76.173] (port=36119 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LvtrK-0000qI-Jh
	for qemu-devel@nongnu.org; Mon, 20 Apr 2009 09:48:30 -0400
Received: from verein.lst.de ([213.95.11.210]:57602)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60)
	(envelope-from <hch@lst.de>) id 1LvtrK-00020F-05
	for qemu-devel@nongnu.org; Mon, 20 Apr 2009 09:48:30 -0400
Date: Mon, 20 Apr 2009 15:48:19 +0200
From: Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH 1/5] qcow2: Fix warnings in check_refcount()
Message-ID: <20090420134819.GB8480@lst.de>
References: <1239969879-5611-1-git-send-email-kwolf@redhat.com>
	<200904172319.55735@kevin-wolf.de> <49E8FDA1.2030505@us.ibm.com>
	<200904180029.06432@kevin-wolf.de> <49E90356.1090305@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49E90356.1090305@us.ibm.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Christoph Hellwig <hch@infradead.org>, Kevin Wolf <mail@kevin-wolf.de>

On Fri, Apr 17, 2009 at 05:31:50PM -0500, Anthony Liguori wrote:
> Yeah, I've been wanting to do everything via kvm-autotest but so far, 
> it's not quite up to what I want to use it for.  I'll see about cleaning 
> up some of my scripts and posting them.  The problem is they rely on 
> custom images.

Having a repository of "problem" or just interesting images that we can
use qemu-io or just plain guests on would be extremty helpful for
extending test coverage.