> The user basically can specify two things: > > - a transport protocol. Normally this is just the filesystem > interface, but it can also be nbd, http or for really sick people > vvfat. This is a setting which can't be guessed, btw - it needs > to be explicitly set in some way, with file used as a reasonable > fallback. > > - an image format. This one interprets the content the transport > protocol delivers to us. This can either be raw for not interpreting > it all, or things like qcow2 / vmdk to add more functionality to it.
Makes sense to me. In theory we should be able to stack image formats. In practice it's probably not very useful with the current set of formats, so may not be worth the hassle. The best way to implement it may be to add a "blockdev" transport. Paul
