Hello List, I am trying to understand kvm memory management code related to VM migration. From the code, it looks like during guest VM migration, all the memory of the guest is transferred from source to destination, but does it copy the source page tables to destination ?
A certain GFN(guest frame/physical number) X can be mapped to to PFN Y in source but it is not necessary to map that GFN to PFN Y at destination. Thus it should not make sense to copy page tables. But then, KVM should build page tables when entire memory is copied(because current implementation is precopy). I added prinks in code and looks like at destination it fault, there are no page tables created. But the memory is. Is this understanding correct ? Can anyone explain which part of code is doing this page table building ? -- Sunil -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
