On 06/21/2010 09:01 AM, Kevin Wolf wrote:
No, what I'm saying is that even in your model
-blockdev format=qcow2,file=image.qcow2,id=blk1
becomes qcow2 -> file automatically, whereas
-blockdev format=vvfat,file=/tmp/dir/,id=blk1
doesn't become vvfat -> file, but stays just vvfat.
I should say, that -blockdev format= vs. -blockdev transport= is
definitely at a place where I don't care that much.
The things that I think are most important are:
1) That we have structured options that map well to config file without
trickery to do nesting
2) That we don't automagically pass options through from the first layer
down to subsequent layers
I think we're pretty much agreed here so while I think it's worth
discussing whether format or transport should be exposed to the user, it
shouldn't stop someone from coding something up and submitting it.
Either way would be a vast improvement over what we have now.
Regards,
Anthony Liguori
