diff options
| author | Leonardo Bras <leobras@redhat.com> | 2023-04-25 00:33:08 -0300 |
|---|---|---|
| committer | Juan Quintela <quintela@redhat.com> | 2023-04-27 10:18:25 +0200 |
| commit | b405dfff1ea3cf0530b628895b5a7a50dc8c6996 (patch) | |
| tree | bd50d2ce01714d628935a1ebe1d098c5e872b155 /migration/qemu-file.c | |
| parent | c3f9aa8e488db330197c9217e38555f6772e8f07 (diff) | |
| download | qemu-b405dfff1ea3cf0530b628895b5a7a50dc8c6996.zip qemu-b405dfff1ea3cf0530b628895b5a7a50dc8c6996.tar.gz qemu-b405dfff1ea3cf0530b628895b5a7a50dc8c6996.tar.bz2 | |
migration: Disable postcopy + multifd migration
Since the introduction of multifd, it's possible to perform a multifd
migration and finish it using postcopy.
A bug introduced by yank (fixed on cfc3bcf373) was previously preventing
a successful use of this migration scenario, and now thing should be
working on most scenarios.
But since there is not enough testing/support nor any reported users for
this scenario, we should disable this combination before it may cause any
problems for users.
Suggested-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Leonardo Bras <leobras@redhat.com>
Acked-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'migration/qemu-file.c')
0 files changed, 0 insertions, 0 deletions