Sasha Levin <[email protected]> writes: > On Thu, Nov 10, 2011 at 10:57 AM, Markus Armbruster <[email protected]> wrote: >> Sasha Levin <[email protected]> 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. [...] -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
