On 30/12/2015 01:26, Peter Crosthwaite wrote:
> On Tue, Nov 10, 2015 at 6:25 AM, Juan Quintela wrote:
>> From: "Dr. David Alan Gilbert"
>>
>> 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
* Peter Crosthwaite (crosthwaitepe...@gmail.com) wrote:
> On Tue, Nov 10, 2015 at 6:25 AM, Juan Quintela wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > 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 len
On Tue, Nov 10, 2015 at 6:25 AM, Juan Quintela wrote:
> From: "Dr. David Alan Gilbert"
>
> 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-p
From: "Dr. David Alan Gilbert"
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 chang
From: "Dr. David Alan Gilbert"
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 chang
