aboutsummaryrefslogtreecommitdiff
path: root/rust/qemu-api
diff options
context:
space:
mode:
authorFabiano Rosas <farosas@suse.de>2025-02-05 13:23:55 -0300
committerFabiano Rosas <farosas@suse.de>2025-02-14 15:19:04 -0300
commite0ad300fe1a0e0b12b90994bab6e4df77dd1ee8a (patch)
treec3671a94999710d69473a4c671949438fe0d9a9f /rust/qemu-api
parent9b3b192f65b1cf635719a2981dd2d4b70892d2ec (diff)
downloadqemu-e0ad300fe1a0e0b12b90994bab6e4df77dd1ee8a.zip
qemu-e0ad300fe1a0e0b12b90994bab6e4df77dd1ee8a.tar.gz
qemu-e0ad300fe1a0e0b12b90994bab6e4df77dd1ee8a.tar.bz2
migration: Check migration error after loadvm
We're currently only checking the QEMUFile error after qemu_loadvm_state(). This was causing a TLS termination error from multifd recv threads to be ignored. Start checking the migration error as well to avoid missing further errors. Regarding compatibility concerning the TLS termination error that was being ignored, for QEMUs <= 9.2 - if the old QEMU is being used as migration source - the recently added migration property multifd-tls-clean-termination needs to be set to OFF in the *destination* machine. Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de>
Diffstat (limited to 'rust/qemu-api')
0 files changed, 0 insertions, 0 deletions