Liran Schour wrote:
qemu_savevm_state will call all registered components with 3 phases: START,
PART, END. Only the PART phase is iterative.
In case of storage live migration we have lot more data to copy then memory
and usually the dirty rate is much less then memory dirty rate. I thought
about
qemu_savevm_state will call all registered components with 3 phases: START,
PART, END. Only the PART phase is iterative.
In case of storage live migration we have lot more data to copy then memory
and usually the dirty rate is much less then memory dirty rate. I thought
about adding an iterative p
