[pve-devel] [PATCH V2] - fix setting migration parameters
Alexandre DERUMIER
aderumier at odiso.com
Thu Dec 27 07:31:29 CET 2012
> Cleaner code. Nobody expects that those values were set at vm start.
>>We set that since version 1.0 - so 'everybody' expect that this value is set at startup.
I agree with stefan, this value should be set before migration.
currently, we can't change the migrate_downtime without restart the vm.
(example:
I have a migration which take to much time because of too low migrate_downtime value,
I stop the migration,
I increase the migrate_downtime,
I restart the migration)
----- Mail original -----
De: "Dietmar Maurer" <dietmar at proxmox.com>
À: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag>
Cc: pve-devel at pve.proxmox.com
Envoyé: Jeudi 27 Décembre 2012 07:27:29
Objet: Re: [pve-devel] [PATCH V2] - fix setting migration parameters
> Cleaner code. Nobody expects that those values were set at vm start.
We set that since version 1.0 - so 'everybody' expect that this value is set at startup.
> >> - lower default migration downtime value to 0
> >
> > We do not want that, because this is known to cause long wait times on
> busy VMs.
>
> A value of 1 does not work for me. Whole vm stalls immediately and socket
> is unavailable. Migration than takes 5-10 minutes of an idle vm.
So this is a qemu bug - we should try to fix that.
Else any VM which use migrate_downtime is broken!
_______________________________________________
pve-devel mailing list
pve-devel at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
More information about the pve-devel
mailing list