migration: Fix non-multiple of page size migration
commit1eb3fc0a0b61b5d22adee2a9add3162a6c03a47e
authorDr. David Alan Gilbert <dgilbert@redhat.com>
Wed, 17 May 2017 16:58:09 +0000 (17 17:58 +0100)
committerJuan Quintela <quintela@redhat.com>
Thu, 18 May 2017 16:04:53 +0000 (18 18:04 +0200)
treef52c213e3456aa91214d9ee05db39a02213810ff
parent56821559f0ba682fe6b367815572e6f974d329ab
migration: Fix non-multiple of page size migration

Unfortunately it's legal to create a VM with a RAM size that's
not a multiple of the underlying host page or huge page size.
Recently I'd changed things to always send host sized pages,
and that breaks if we have say a 1025MB guest on 2MB hugepages.

Unfortunately we can't just make that illegal since it would break
migration from/to existing oddly configured VMs.

Symptom: qemu-system-x86_64: Illegal RAM offset 40100000
     as it transmits the fraction of the hugepage after the end
     of the RAMBlock (may also cause a crash on the source
     - possibly due to clearing bits after the bitmap)

Reported-by: Yumei Huang <yuhuang@redhat.com>
Red Hat bug: https://bugzilla.redhat.com/show_bug.cgi?id=1449037

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