On 11/09/2009 09:35 PM, Jamie Lokier wrote:
What I'd like to know is, if all of QEMU's state is appropriately recreated in the child instance, and KVM's device is reopened with a copy of the kvm state (by using the recently introduced ioctls to get and set it), will it fork the _guest RAM_ mapped into KVM in the way that fork does?
Guest RAM is just ordinary userspace memory. If you told Linux to COW it, it will COW it. If you told Linux not to COW it, it will not COW it. kvm has nothing to say in the matter (at least with kernels 2.6.27 and up).
-- error compiling committee.c: too many arguments to function
