From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757610Ab1KJJsv (ORCPT ); Thu, 10 Nov 2011 04:48:51 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49856 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755406Ab1KJJss (ORCPT ); Thu, 10 Nov 2011 04:48:48 -0500 From: Markus Armbruster To: Sasha Levin Cc: Pekka Enberg , Anthony Liguori , Pekka Enberg , Linus Torvalds , Avi Kivity , Andrew Morton , Ingo Molnar , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Christoph Hellwig Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2 References: <4EBB4A21.20707@codemonkey.ws> Date: Thu, 10 Nov 2011 10:48:07 +0100 In-Reply-To: (Sasha Levin's message of "Thu, 10 Nov 2011 11:04:46 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sasha Levin writes: > On Thu, Nov 10, 2011 at 10:57 AM, Markus Armbruster wrote: >> Sasha Levin writes: [...] >>> I'm actually not sure why KVM tool got QCOW support in the first >>> place. You can have anything QCOW provides if you use btrfs (among >>> several other FSs). >> >> Maybe it's just me, but isn't it weird to have a filesystem (QCOW2) >> sitting in the kernel sources that you can't mount(2)? >> > > It's not really a filesystem, it's a disk image :) Sloppy language on my part, sorry about that. It's a transport for blocks. We have a few of those in the kernel already: block devices. Including loop devices and DRBD. You use a filesystem to interpret their contents. The resulting stack is what gets mounted. Adding another transport for blocks to the kernel that cannot be used that way strikes me as weird. [...]