aboutsummaryrefslogtreecommitdiff
path: root/migration/ram.c
diff options
context:
space:
mode:
authorPeter Xu <peterx@redhat.com>2018-07-10 17:18:54 +0800
committerDr. David Alan Gilbert <dgilbert@redhat.com>2018-07-10 12:56:07 +0100
commitfd037a656aca23dc3c47aa8c9de261bec6b8aad0 (patch)
tree89bb2c422334e3e1262e68f9cbf562ecfcd80429 /migration/ram.c
parent1aa8367861645c3c0917f585fe14b1b6b23b0f66 (diff)
migration: loosen recovery check when load vm
We were checking against -EIO, assuming that it will cover all IO failures. But actually it is not. One example is that in qemu_loadvm_section_start_full() we can have tons of places that will return -EINVAL even if the error is caused by IO failures on the network. Let's loosen the recovery check logic here to cover all the error cases happened by removing the explicit check against -EIO. After all we won't lose anything here if any other failure happened. Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Reviewed-by: Juan Quintela <quintela@redhat.com> Signed-off-by: Peter Xu <peterx@redhat.com> Message-Id: <20180710091902.28780-3-peterx@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'migration/ram.c')
0 files changed, 0 insertions, 0 deletions