-
Dr. David Alan Gilbert authored
RAMBlocks that are not a multiple of host pages in length cause problems for postcopy (I've seen an ACPI table on aarch64 be 5k in length - i.e. 5x target-page), so round RAMBlock sizes up to a host-page. This potentially breaks migration compatibility due to changes in RAMBlock sizes; however: 1) x86 and s390 I think always have host=target page size 2) When I've tried on Power the block sizes already seem aligned. 3) I don't think there's anything else that maintains per-version machine-types for compatibility. 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>Dr. David Alan Gilbert authoredRAMBlocks that are not a multiple of host pages in length cause problems for postcopy (I've seen an ACPI table on aarch64 be 5k in length - i.e. 5x target-page), so round RAMBlock sizes up to a host-page. This potentially breaks migration compatibility due to changes in RAMBlock sizes; however: 1) x86 and s390 I think always have host=target page size 2) When I've tried on Power the block sizes already seem aligned. 3) I don't think there's anything else that maintains per-version machine-types for compatibility. 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>
Loading