On 06/16/2009 12:10 PM, Avi Kivity wrote:
Does anyone have a clever idea how to fix this without just waiting
for all IO requests to complete?
What's wrong with waiting for requests to complete? It should take a
few tens of milliseconds.
We could start throttling requests late in the live stage, but I don't
really see the point.
Well, we can introduce a new live stage, where we migrate RAM and
complete block requests, but the vm is otherwise stopped. This allows
the flush to overlap with sending memory dirtied by the flush, reducing
some downtime. Since block requests can dirty large amounts of memory,
this may be significant.
We can even keep the vcpu alive, only blocking new block requests, but
that may cause dirty RAM divergence.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
