Am 14.09.2011 17:45, schrieb Anthony Liguori:
On 09/14/2011 08:18 AM, Thomas Treutner wrote:
Currently, it is possible that a live migration never finishes, when
the dirty page rate is high compared to the scan/transfer rate. The
exact values for MAX_MEMORY_ITERATIONS and
Currently, it is possible that a live migration never finishes, when the dirty
page rate is high compared to the scan/transfer rate. The exact values for
MAX_MEMORY_ITERATIONS and MAX_TOTAL_MEMORY_TRANSFER_FACTOR are arguable, but
there should be *some* limit to force the final iteration of a li
Am 09.02.2011 21:02, schrieb Anthony Liguori:
The reason it's still this today is mainly historic. I've thought about
making the default limit unlimited. I'm not sure if anyone has strong
opinions.
Personally, I'd appreciate that. TCP's congestion control when using
100MBit Ethernet seems to w
Hi,
I was reading qemu's (qemu-kvm-0.13.0's, to be specific) live migration
code to unterstand how the iterative dirty page transfer is implemented.
During this I noticed that ram_save_live in arch_init.c is called quite
often, more often than I expected (approx. 200 times for an idle 500MiB
On Tuesday 29 December 2009 13:24:36 Luiz Capitulino wrote:
> > > Is the "-balloon virtio" parameter passed on the command-line?
> >
> > # grep balloon /usr/local/var/log/libvirt/qemu/* | wc -l
> > 0
> >
> > These logs include some history - so the parameter isn't used by libvirt
> > even when bal
On Tuesday 29 December 2009 12:48:39 Luiz Capitulino wrote:
> On Tue, 29 Dec 2009 13:10:36 +0200 Avi Kivity wrote:
> > Hm, I get "The balloon device has not been activated by the guest" in
> > the qemu monitor.
>
> Is the "-balloon virtio" parameter passed on the command-line?
# grep balloon /us
