migration: Modify ram_init_bitmaps() to report dirty tracking errors
commit030b56b280375242cd8591b06e806978b8564be1
authorCédric Le Goater <clg@redhat.com>
Wed, 20 Mar 2024 06:49:10 +0000 (20 07:49 +0100)
committerPeter Xu <peterx@redhat.com>
Tue, 23 Apr 2024 22:36:01 +0000 (23 18:36 -0400)
tree2eb13b0bec5ebfc1f5c4b016c3ab85206df32f36
parent7bee8ba8bbcef27cc98bc85747258e942f8d9717
migration: Modify ram_init_bitmaps() to report dirty tracking errors

The .save_setup() handler has now an Error** argument that we can use
to propagate errors reported by the .log_global_start() handler. Do
that for the RAM. The caller qemu_savevm_state_setup() will store the
error under the migration stream for later detection in the migration
sequence.

Signed-off-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
Link: https://lore.kernel.org/r/20240320064911.545001-15-clg@redhat.com
Signed-off-by: Peter Xu <peterx@redhat.com>
migration/ram.c