Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

What about every 15seconds if no progress has happened? How would you define progress? I would then start at 0.15s downtime as default or at custom conf value if defined. If no progress happens I would double the value. Stefan Am 30.12.2012 um 06:55 schrieb Dietmar Maurer diet...@proxmox.com:

Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

Décembre 2012 09:33:09 Objet: Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0 What about every 15seconds if no progress has happened? How would you define progress? I would then start at 0.15s downtime as default or at custom conf

Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

: Alexandre Derumier aderum...@odiso.com, pve-devel@pve.proxmox.com Envoyé: Dimanche 30 Décembre 2012 09:33:09 Objet: Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0 What about every 15seconds if no progress has happened? How would you

Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Dimanche 30 Décembre 2012 13:25:40 Objet: Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0 Hi, attached a patch

Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

Hi, Am 30.12.2012 16:31, schrieb Alexandre DERUMIER: I'm testing your patch. remaning memory can also stay at 0 at the end (with last qemu git migration patch), so we need to also check that. OK - will wait for your patch. Still missing part1. also in your patch, what is +

Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

attached a patch. I think a fast round should clear the counter? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

Am 31.12.2012 um 06:00 schrieb Dietmar Maurer diet...@proxmox.com: attached a patch. I think a fast round should clear the counter? But this would raise the chance to have a constant up and down. I could imagine lowering the counter by just 0.5 could prevent that. Stefan

Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

Hi, i really like that idea instead of having a fixed downtime of 1s. What is about starting at 0.5s and then add 0.5s every 15 runs? Dietmar what's your opinion? Greets, Stefan Am 27.12.2012 11:14, schrieb Alexandre Derumier: Signed-off-by: Alexandre Derumier aderum...@odiso.com ---

Re: [pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

i really like that idea instead of having a fixed downtime of 1s. What is about starting at 0.5s and then add 0.5s every 15 runs? Yes, we can do that, but may Every 15 runs if we make no progress? ___ pve-devel mailing list

[pve-devel] [PATCH] increase migrate_set_downtime only if expected downtime is more than 30 iterations 0

Signed-off-by: Alexandre Derumier aderum...@odiso.com --- PVE/QemuMigrate.pm | 24 ++-- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm index dbbeb69..aeb6deb 100644 --- a/PVE/QemuMigrate.pm +++ b/PVE/QemuMigrate.pm @@