From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbjER-0005pI-4v for qemu-devel@nongnu.org; Thu, 13 Aug 2009 18:57:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbjEM-0005mj-Ea for qemu-devel@nongnu.org; Thu, 13 Aug 2009 18:57:14 -0400 Received: from [199.232.76.173] (port=50826 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbjEM-0005mf-6c for qemu-devel@nongnu.org; Thu, 13 Aug 2009 18:57:10 -0400 Received: from mx20.gnu.org ([199.232.41.8]:6310) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MbjEL-00080b-85 for qemu-devel@nongnu.org; Thu, 13 Aug 2009 18:57:09 -0400 Received: from mail-qy0-f174.google.com ([209.85.221.174]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbjEK-0006Ts-Fd for qemu-devel@nongnu.org; Thu, 13 Aug 2009 18:57:08 -0400 Received: by qyk4 with SMTP id 4so876502qyk.4 for ; Thu, 13 Aug 2009 15:57:07 -0700 (PDT) Message-ID: <4A849A40.3080205@codemonkey.ws> Date: Thu, 13 Aug 2009 17:57:04 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Add tar container format References: <1249486402-10824-1-git-send-email-agraf@suse.de> In-Reply-To: <1249486402-10824-1-git-send-email-agraf@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Kevin Wolf , qemu-devel@nongnu.org, Christoph Hellwig Alexander Graf wrote: > For that we still need to enable the qemu blockery to support stacking though. > > Signed-off-by: Alexander Graf > This feels like a bit too much of a one-off to me. I'm concerned that it's something we'd have to support long term that wouldn't have very many users beyond your particular use-case. So far, we only support image formats that are dedicated to virtual machines. We support http and nbd but those are generic protocols, not necessarily special formats. tar and dzip seem arbitrary. Why not zip, rar, bzip2, or any other format? You could do all of this by making use of a fuse filesystem. I'd almost rather see something like gio integration so that this sort of generic filesystem stuff could live somewhere else. I'm curious what others think though. Does it seem reasonable to include this type of functionality?