diff options
| author | Peter Xu <peterx@redhat.com> | 2018-07-23 20:33:03 +0800 |
|---|---|---|
| committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | 2018-07-24 17:10:59 +0100 |
| commit | 97ca211c6216ccfcb64c46f739a0ce36042d9ea8 (patch) | |
| tree | e9866bb7fc0ee13f02d7c5d986dc8be2ca66cd70 /hw/core/qdev-properties-system.c | |
| parent | 814bb08f177af8dc67e155f0ad622fb6366c3b85 (diff) | |
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 'hw/core/qdev-properties-system.c')
0 files changed, 0 insertions, 0 deletions