Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-06-08 Thread Amit Shah
On (Sat) 07 Jun 2014 [02:48:14], Alexey Kardashevskiy wrote: > On 06/06/2014 10:50 PM, Amit Shah wrote: > > On (Thu) 27 Mar 2014 [14:57:26], Alexey Kardashevskiy wrote: > >> 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

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-06-06 Thread Alexey Kardashevskiy
On 06/06/2014 10:50 PM, Amit Shah wrote: > On (Thu) 27 Mar 2014 [14:57:26], Alexey Kardashevskiy wrote: >> 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 n

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-06-06 Thread Amit Shah
On (Thu) 27 Mar 2014 [14:57:26], Alexey Kardashevskiy wrote: > 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 m

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-06-04 Thread Paolo Bonzini
Il 04/06/2014 12:25, Juan Quintela ha scritto: > > Who else needs to be ok to get this in upstream? :) Thanks! Peter? David? Paolo? (I think to remember that they are ok with it) Certainly okay by me. Paolo

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-06-04 Thread Juan Quintela
Alexey Kardashevskiy wrote: > On 05/05/2014 09:20 PM, Juan Quintela wrote: >> Alexey Kardashevskiy wrote: >>> On 04/13/2014 12:38 AM, Alexey Kardashevskiy wrote: On 03/27/2014 08:01 PM, Markus Armbruster wrote: > Adding Juan. Ping? >> >> Patch is OK for me. > > > > Who el

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-06-04 Thread Alexey Kardashevskiy
On 05/05/2014 09:20 PM, Juan Quintela wrote: > Alexey Kardashevskiy wrote: >> On 04/13/2014 12:38 AM, Alexey Kardashevskiy wrote: >>> On 03/27/2014 08:01 PM, Markus Armbruster wrote: Adding Juan. >>> >>> >>> Ping? > > Patch is OK for me. Who else needs to be ok to get this in upstream? :)

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-05-05 Thread Juan Quintela
Alexey Kardashevskiy wrote: > On 04/13/2014 12:38 AM, Alexey Kardashevskiy wrote: >> On 03/27/2014 08:01 PM, Markus Armbruster wrote: >>> Adding Juan. >> >> >> Ping? Patch is OK for me. As sender says, with guests doing anything/bigger than 1GB RAM is basically implosible to get into the 30ms

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-05-05 Thread Alexey Kardashevskiy
On 04/30/2014 11:10 AM, Alexey Kardashevskiy wrote: > On 04/13/2014 12:38 AM, Alexey Kardashevskiy wrote: >> On 03/27/2014 08:01 PM, Markus Armbruster wrote: >>> Adding Juan. >> >> >> Ping? > > > Ping? > > Ping? >> >>> >>> Alexey Kardashevskiy writes: >>> The existing timeout is 30ms w

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-04-29 Thread Alexey Kardashevskiy
On 04/13/2014 12:38 AM, Alexey Kardashevskiy wrote: > On 03/27/2014 08:01 PM, Markus Armbruster wrote: >> Adding Juan. > > > Ping? Ping? > >> >> Alexey Kardashevskiy writes: >> >>> The existing timeout is 30ms which on 100MB/s (1Gbit) gives us >>> 3MB/s rate maximum. If we put some load on

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-04-12 Thread Alexey Kardashevskiy
On 03/27/2014 08:01 PM, Markus Armbruster wrote: > Adding Juan. Ping? > > Alexey Kardashevskiy writes: > >> 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 migratio

Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-03-27 Thread Markus Armbruster
Adding Juan. Alexey Kardashevskiy writes: > 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 gu

[Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms

2014-03-26 Thread Alexey Kardashevskiy
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