On 12/04/2014 11:57 AM, Peter Krempa wrote:
On 12/04/14 17:53, Jim Fehlig wrote:
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. qemu driver allows this already since: commit fe808d95bf353647bb39b3bc468f5a841b5588dd Author: Chris St. Pierre <chris.a.st.pierre@gmail.com> Date: Mon Sep 29 13:45:28 2014 +0000
Hmm, since quite some time in fact. Sorry for not looking a bit closer before making this noise. Regards, Jim