From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Why QCOW1? Date: Fri, 15 Apr 2011 07:12:22 -0500 Message-ID: <4DA83626.4040907@codemonkey.ws> References: <1302722762-30517-1-git-send-email-prasadjoshi124@gmail.com> <4DA6AA2F.2020306@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Stefan Hajnoczi , Markus Armbruster , Kevin Wolf , Prasad Joshi , mingo@elte.hu, kvm@vger.kernel.org, asias.hejun@gmail.com, gorcunov@gmail.com, levinsasha928@gmail.com, stefanha@linux.vnet.ibm.com To: Pekka Enberg Return-path: Received: from mail-gy0-f174.google.com ([209.85.160.174]:60009 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720Ab1DOMM0 (ORCPT ); Fri, 15 Apr 2011 08:12:26 -0400 Received: by gyd10 with SMTP id 10so792113gyd.19 for ; Fri, 15 Apr 2011 05:12:25 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 04/15/2011 06:17 AM, Pekka Enberg wrote: > On Fri, Apr 15, 2011 at 1:14 PM, Stefan Hajnoczi wrote: >> Why even use a non-raw image format? The current implementation only >> does sparse files, but POSIX sparse raw files gives you the same >> feature. > Because people have existing images they want to boot to? Since this project is trying to be so integrated into the kernel, why not add support for image files directly to the kernel? Add a qcow1/qcow2/qed block device type such that you can use normal tools (like mount) to work with the image files. Regards, Anthony Liguori > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html