| commit | f7cd55a023b71ff9583dad9135413b7cc5821dfe | |
| author | Alexey Kardashevskiy <aik@ozlabs.ru> | |
| Thu, 27 Mar 2014 03:57:26 +0000 (27 14:57 +1100) | ||
| committer | Juan Quintela <quintela@redhat.com> | |
| Mon, 16 Jun 2014 02:55:27 +0000 (16 04:55 +0200) | ||
| tree | 7f75137f512e391b8d3e736d5c680806ca347d5a | treesnapshot (tar.gz zip) |
| parent | c6f6646c60a2450e437ee89582295d5fde8e8a72 | commitdiff |
migration: Increase default max_downtime from 30ms to 300ms
The existing timeout is 30ms which on 100MB/s (1Gbit) gives us
3MB/s rate maximum. If we put some load on the guest, it is easy to
get page dirtying rate too big so live migration will never complete.
In the case of libvirt that means that the guest will be stopped
anyway after a timeout specified in the "virsh migrate" command and
this normally generates even bigger delay.
This changes max_downtime to 300ms which seems to be more
reasonable value.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Juan Quintela <quintela@redhat.com>
The existing timeout is 30ms which on 100MB/s (1Gbit) gives us
3MB/s rate maximum. If we put some load on the guest, it is easy to
get page dirtying rate too big so live migration will never complete.
In the case of libvirt that means that the guest will be stopped
anyway after a timeout specified in the "virsh migrate" command and
this normally generates even bigger delay.
This changes max_downtime to 300ms which seems to be more
reasonable value.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Juan Quintela <quintela@redhat.com>
| migration.c | diffblobblamehistory |