On Mon, Jul 10, 2017 at 03:24:02PM +0200, Peter Lieven wrote: > Am 10.07.2017 um 15:10 schrieb Kevin Wolf: > > Am 29.06.2017 um 12:57 hat Peter Lieven geschrieben: > > > Signed-off-by: Peter Lieven <p...@kamp.de> > > > --- > > > qapi/block-core.json | 44 +++++++++++++++++++++++++++++++++++++++++++- > > > 1 file changed, 43 insertions(+), 1 deletion(-) > > How does this make sense as a runtime option? What would happen if the > > image contains one compression format and I specify another one on the > > command line or in blockdev-add? > > > > Shouldn't it just be a create-time option and when you run qemu, it uses > > whatever format that image has? > > I was asked to add it here. It is indeed only a create option and has no > other effect.
I think there was some mis-understanding. I suggested adding QAPI schema to define the options needed during create, and then use QAPI functions when processing the create. In patch 4 you've just used the traditional qemu opts functions to query the parameters, so there's no validation that what's being processed actually matches the QAPI schema. The QAPI schema additions for create would need to be defined indepenantly of the runtime options too. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
