Uri Lublin wrote:
That is true, but in the case I mentioned above it would take the management tool some time (guest down time) to realize what happens, and to send "cont" to the SRC. With end-of-migration messages SRC discovers DST fails and immediately continues. I agree those messages add some complexity, and slow things a bit for the good/average case.
It's the classic general's dilemma. If SRC waits for DST to send an ACK, DST still doesn't know whether SRC received the ACK so it doesn't know whether it's truly safe to continue.
This is why migration doesn't quit SRC immediately, and leaves SRC in the stopped state. It's because the only safe way to handle this is with a third party that is reliable.
Regards, Anthony Liguori -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
