A user asked me about setting max downtime prior to migration, which I thought
could be done similar to MigrateSetMaxSpeed. I was surprised to find that it
can only be set when migration is in progress
# virsh migrate-setmaxdowntime test 1000
error: Requested operation is not valid: domain is not being migrated
Is there any reason this cannot be set prior to migration? Max speed can even
be set on a persistent domain that is not running. I'd be happy to work on a
patch if the only reason is no one has needed this itch scratched.
Regards,
Jim
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list