summaryrefslogtreecommitdiffstats
path: root/tests/test-io-channel-socket.c
diff options
context:
space:
mode:
authorPeter Xu2018-07-23 14:33:03 +0200
committerDr. David Alan Gilbert2018-07-24 18:10:59 +0200
commit97ca211c6216ccfcb64c46f739a0ce36042d9ea8 (patch)
treee9866bb7fc0ee13f02d7c5d986dc8be2ca66cd70 /tests/test-io-channel-socket.c
parentmigration: update recv bitmap only on dest vm (diff)
downloadqemu-97ca211c6216ccfcb64c46f739a0ce36042d9ea8.tar.gz
qemu-97ca211c6216ccfcb64c46f739a0ce36042d9ea8.tar.xz
qemu-97ca211c6216ccfcb64c46f739a0ce36042d9ea8.zip
migration: disallow recovery for release-ram
Postcopy recovery won't work well with release-ram capability since release-ram will drop the page buffer as long as the page is put into the send buffer. So if there is a network failure happened, any page buffers that have not yet reached the destination VM but have already been sent from the source VM will be lost forever. Let's refuse the client from resuming such a postcopy migration. Luckily release-ram was designed to only be used when src and destination VMs are on the same host, so it should be fine. Signed-off-by: Peter Xu <peterx@redhat.com> Message-Id: <20180723123305.24792-3-peterx@redhat.com> Reviewed-by: Juan Quintela <quintela@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'tests/test-io-channel-socket.c')
0 files changed, 0 insertions, 0 deletions