Postcopy vs xbzrle: Don't send xbzrle pages once in postcopy [for 2.8]
authorDr. David Alan Gilbert <dgilbert@redhat.com>
Wed, 24 Aug 2016 17:15:46 +0000 (18:15 +0100)
committerJuan Quintela <quintela@trasno.org>
Thu, 13 Oct 2016 15:23:53 +0000 (17:23 +0200)
commit2ebeaec012b4e5695612774c44f14c61ab46c72c
treed7a492d4699a7240ad7ff7c5bd41bc11928a082e
parent091ecc8b69bd735383e171828d4e8ed5e34c2a3b
Postcopy vs xbzrle: Don't send xbzrle pages once in postcopy [for 2.8]

xbzrle relies on reading pages that have already been sent
to the destination and then applying the modifications; we can't
do that in postcopy because the destination may well have
modified the page already or the page has been discarded.

I already didn't allow reception of xbzrle pages, but I
forgot to add the test to stop them being sent.

Enabling both xbzrle and postcopy can make some sense;
if you think that your migration might finish if you
have xbzrle, then when it doesn't complete you flick
over to postcopy and stop xbzrle'ing.

This corresponds to RH bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1368422

Symptom is:

Unknown combination of migration flags: 0x60 (postcopy mode)
(either 0x60 or 0x40)

Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
migration/ram.c