Glauber Costa wrote:
> On Fri, May 22, 2009 at 11:51:45PM +0200, Jan Kiszka wrote:
>> As Avi correctly noted, last_ram_offset does not mark the last physical
>> RAM address the guest may see (due to non-continuous memory regions).
>> Ensure that we catch them all by marking the full possible address range
>> dirty.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> Indeed, we already do something in that lines in qemu-kvm tree, 
> in a place that does not apply for  It makes a lot of sense. Just
> maybe you could just -1UL instead of defining a new constant, but I don't
> really care.

I intentionally made this verbose.

> 
> As soon as this is applied to master, I'll pick it for stable too.

Migration for KVM would be a new feature for stable. It requires a new
CPU save/restore format (V9). Do think that qualifies it for stable.

Jan