From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pekka Enberg <penberg@kernel.org>
Subject: Re: Why QCOW1? (was: [PATCH v2] kvm tool: add QCOW verions 1
 read/write support)
Date: Fri, 15 Apr 2011 15:10:46 +0300
Message-ID: <BANLkTin9OrhtbAk+A0=eu=qxog4nmwLksA@mail.gmail.com>
References: <1302722762-30517-1-git-send-email-prasadjoshi124@gmail.com>
	<4DA6AA2F.2020306@redhat.com>
	<m3wriwdnjb.fsf_-_@blackfin.pond.sub.org>
	<BANLkTiknr7=1_xstQiTJeQnObO426sFcwg@mail.gmail.com>
	<BANLkTinU+JM_ac9bLwQjF94Wek0VTqa3+Q@mail.gmail.com>
	<BANLkTimLAzuyYJd8NvZ3jGcPGN7C60J8iA@mail.gmail.com>
	<BANLkTinoSm4oHe+7UHE=DkOm1FpM+YMyDA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: Markus Armbruster <armbru@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>,
	Prasad Joshi <prasadjoshi124@gmail.com>, mingo@elte.hu,
	kvm@vger.kernel.org, asias.hejun@gmail.com, gorcunov@gmail.com,
	levinsasha928@gmail.com, stefanha@linux.vnet.ibm.com
To: Stefan Hajnoczi <stefanha@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-vx0-f174.google.com ([209.85.220.174]:52819 "EHLO
	mail-vx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750877Ab1DOMKr convert rfc822-to-8bit (ORCPT
	<rfc822;kvm@vger.kernel.org>); Fri, 15 Apr 2011 08:10:47 -0400
Received: by vxi39 with SMTP id 39so2009559vxi.19
        for <kvm@vger.kernel.org>; Fri, 15 Apr 2011 05:10:46 -0700 (PDT)
In-Reply-To: <BANLkTinoSm4oHe+7UHE=DkOm1FpM+YMyDA@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Fri, Apr 15, 2011 at 3:05 PM, Stefan Hajnoczi <stefanha@gmail.com> w=
rote:
> People don't have existing QCOW1 images they want to boot from :).
>
> They have vmdk, vhd, vdi, or qcow2. =A0You can use qemu-img to conver=
t
> them to raw. =A0You can use qemu-nbd if you are desperate to boot fro=
m
> or inspect them in-place.
>
> But I think the natural path for a native Linux KVM tool is to fully
> exploit file systems and block layer features in Linux instead of
> implementing a userspace block layer.

=46or optimum performance, sure, but we want to support non-native
images for usability reasons.