On 05/16/2010 11:04 PM, Juan Quintela wrote:
So, to make the story short: I know what is happening, and I know how to
fix it, just that fix is not trivial. I just need time.
Meanwhile, we have a broken 0.12.4. Is there a quick'n'dirty
workaround that will be forward compatible with the real fix that we
can push out?
revert the patch. It almost never happen (being in the middle of one
IO) while migrating.
If the guest does any work, it will always happen.
We've regressed from failing some migrations to failing all migrations.
Humm, 0.12.4 -> 0.12.4 should work. My advise is just revert the patch
and live with it for another week, what do you think?
A week is fine. I'm not going to release 0.12.4.1 for the week until
you fix it, and just changing things in git doesn't help users.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
