On Tue, Feb 28, 2023 at 07:59:54PM +0200, Anton Kuchin wrote: > We can't rely here entirely on > destination to block this because if VM is migrated to file and then > can't be loaded by destination there is no way to fallback and resume > the source so we need to have some kind of blocker on source by default.
So I commented about a fallback. IMO it's just orchestrator being silly: don't kill source qemu until you have made sure destination loaded the file, or re-load it, and all will be well. But a bigger issue that this highlights is simply that if migrating to file you have no idea at all where will the file be loaded. Maybe some orchestrators know but I don't see how we can be sure all of them know. The only time where we know whether the file is loaded on the same host where it was saved is when we actually load it. -- MST
