| commit | 2ab033fca211b213418a7d9ac3c33b4cc7ef056d | |
| author | Glauber de Oliveira Costa <glommer@redhat.com> | |
| Tue, 12 May 2009 23:24:14 +0000 (12 20:24 -0300) | ||
| committer | Avi Kivity <avi@redhat.com> | |
| Wed, 13 May 2009 06:59:32 +0000 (13 09:59 +0300) | ||
| tree | 14886871059c48c8e3ea62cb21377a79a931448c | treesnapshot (tar.gz zip) |
| parent | 20c94ef953b8cebf5039a418c0f5a2f151420cbc | commitdiff |
Enable dirty logging for all regions during migration
In current calculations, we are not activating dirty logging
for all regions, leading migration to fail. This problem was
already raised by Yaniv Kamay a while ago. The proposed
solution at the time (not merged), was a calculation to convert
from target_phys_addr_t to ram_addr_t, which the dirty logging code
expects.
Avi noticed that enabling dirty logging for the region 0 -> -1ULL
would do the trick. As I hit the problem, I can confirm it does.
This patch, therefore, goes with this simpler approach. Before
this patch, migration fails. With this patch, simple migration
tests succeds.
Signed-off-by: Glauber de Oliveira Costa <glommer@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
In current calculations, we are not activating dirty logging
for all regions, leading migration to fail. This problem was
already raised by Yaniv Kamay a while ago. The proposed
solution at the time (not merged), was a calculation to convert
from target_phys_addr_t to ram_addr_t, which the dirty logging code
expects.
Avi noticed that enabling dirty logging for the region 0 -> -1ULL
would do the trick. As I hit the problem, I can confirm it does.
This patch, therefore, goes with this simpler approach. Before
this patch, migration fails. With this patch, simple migration
tests succeds.
Signed-off-by: Glauber de Oliveira Costa <glommer@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
| qemu-kvm.c | diffblobblamehistory |