On 04/08/2015 06:46 PM, Paolo Bonzini wrote:
On 08/04/2015 08:34, Xiao Guangrong wrote:
We noticed that KVM keeps tracking dirty for the memslots when
live migration failed which causes bad performance due to huge
page mapping disallowed for this kind of memslot
It is caused by slot flags d
We noticed that KVM keeps tracking dirty for the memslots when
live migration failed which causes bad performance due to huge
page mapping disallowed for this kind of memslot
It is caused by slot flags does not properly sync-ed between Qemu
and KVM. Current code doing slot update depends on slot-
On 04/08/2015 02:34 PM, Xiao Guangrong wrote:
We noticed that KVM keeps tracking dirty for the memslots when
live migration failed which causes bad performance due to huge
page mapping disallowed for this kind of memslot
It is caused by slot flags does not properly sync-ed between Qemu
and KVM
On 08/04/2015 08:34, Xiao Guangrong wrote:
> We noticed that KVM keeps tracking dirty for the memslots when
> live migration failed which causes bad performance due to huge
> page mapping disallowed for this kind of memslot
>
> It is caused by slot flags does not properly sync-ed between Qemu
>
