Il 26/11/2013 13:24, Jiri Denemark ha scritto:
Hmm, I know you are just following what I did with
VIR_MIGRATE_COMPRESSED, but setting auto-converge on destination doesn't
make any sense. And it doesn't even make a lot of sense to set
compression on destination (other than checking the destination supports
compression) so I'm wondering why I did so.
FWIW, when new capabilities pop up, I'm trying to enforce that they only
need to be set in the source and that (if they affect the destination at
all) the destination should automatically discover them through the
migration stream.
"query-migrate-capabilities" can be used to find out if the destination
knows about the capability.
Paolo