
This invalidation only happens after the point where In any case, this doesn't seem to be related to (re)opening image because theyĪre opened much earlier, and in RHEL 7 we don't reopen images any more, but only VMState handler has a different message, too, though I might be wrong on that. We might restart requests, but we would return successsīefore that request has even completed. I don't think we require a succeeding I/O request Next thing is that the error message that is seen on the destination refers toĪ qemu_loadvm_state() failure. This might be a hint that it's not exactly the :-)įirst thing I notice is that on the source host we have -ENOSPC, whereas on theĭestination it seems to be -EIO. I guess that depends on the rest of the sentence.

> finds that it has a non finished operation and retries it. > error, or if while we are trying to reopen the disk image on destination, it > It is not completely clear to me (yet) if we are failing for the previous (In reply to Juan Quintela from comment #4)
