On Tue, May 29, 2018 at 12:14:28PM +0200, Kevin Wolf wrote: > Am 29.05.2018 um 11:23 hat Max Reitz geschrieben: > > On 2018-05-28 21:09, Kevin Wolf wrote: > > > Am 28.05.2018 um 20:44 hat Max Reitz geschrieben: > > >> On 2018-05-28 20:38, Kevin Wolf wrote: > > >>> Am 28.05.2018 um 20:30 hat Richard W.M. Jones geschrieben: > > >>>> On Mon, May 28, 2018 at 08:10:32PM +0200, Max Reitz wrote: > > >>>>> As someone who is just naive and doesn't see the big picture, I don't > > >>>>> see what's wrong with using a tar file that contains the image and > > >>>>> additional data. > > >>>> > > >>>> FWIW an OVA file is exactly this: an uncompressed tar file containing > > >>>> disk image(s) and metadata. > > >>> > > >>> If we combine VM configuration and the disk image this way, I would > > >>> still want to directly use that combined thing without having to extract > > >>> its components first. > > >>> > > >>> Just accessing the image file within a tar archive is possible and we > > >>> could write a block driver for that (I actually think we should do > > >>> this), but it restricts you because certain operations like resizing > > >>> aren't really possible in tar. Unfortunately, resizing is a really > > >>> common operation for non-raw image formats. > > >>> > > >>> And if I think of a file format that can contain several different > > >>> things that can be individually resized etc., I end up with qcow2 in the > > >>> simple case or a full file system in the more complex case. > > >> > > >> Well, you end up with VMDK. > > > > > > I don't think VMDK can save several different objects? It can have some > > > metadata in the descriptor, and it can spread the contents of a single > > > object across multiple files (with extents), but I don't think it has > > > something comparable to e.g. qcow2 snapshots, which are separate objects > > > with an individual size that can dynamically change. > > > > Right, I tried to be funny and was over-simplifying in the process. > > > > What I meant is: You end up with an image format that is spread on a > > filesystem, like VMDK is (usually). Then you have some metadata > > descriptor file that describes the rest and multiple data object files. > > > > (For completeness's sake: And you can use an external or an internal > > filesystem, that is, use multiple files (like VMDK) or have an internal > > filesystem (like tar, except tar doesn't allow fragmentation).) > > Let's call the libvirt XML the image file and the qcow2 files its > data object files and we're done?
libvirt XML doesn't seems to be a solution for the problem, but a separate VM specification file could work anyway. > > I'm afraid spreading things across multiple files doesn't meet the > requirements for the problem at hand, though... Yeah, I wanted to make this an extension of qcow2, so people don't have Yet Another file format to choose from. We could also let libvirt automatically write hints to disk images so things would Just Work if you copied a disk image from an existing VM. But I'm not the one working on management layers or guest image tools, so I will just trust Richard's and Daniel's opinions on this. -- Eduardo
