| commit | 70fedd76d9fe4900651f3360725fb511a19d03d5 | |
| author | Alex Williamson <alex.williamson@redhat.com> | |
| Wed, 14 Jul 2010 19:36:49 +0000 (14 13:36 -0600) | ||
| committer | Marcelo Tosatti <mtosatti@redhat.com> | |
| Thu, 5 Aug 2010 12:57:35 +0000 (5 09:57 -0300) | ||
| tree | ebb65f8332f627b230451f61c6eefda7a0a71939 | treesnapshot (tar.gz zip) |
| parent | 748a4ee311b8353292e85851034cb917906aac14 | commitdiff |
kvm: Don't walk memory_size == 0 slots in kvm_client_migration_log
If we've unregistered a memory area, we should avoid calling
qemu_get_ram_ptr() on the left over phys_offset cruft in the
slot array. Now that we support removing ramblocks, the
phys_offset ram_addr_t can go away and cause a lookup fault
and abort.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
If we've unregistered a memory area, we should avoid calling
qemu_get_ram_ptr() on the left over phys_offset cruft in the
slot array. Now that we support removing ramblocks, the
phys_offset ram_addr_t can go away and cause a lookup fault
and abort.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
| kvm-all.c | diffblobblamehistory |